Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!dwp
From: dwp@willett.pgh.pa.us (Doug Philips)
Newsgroups: comp.lang.forth
Subject: Re: ANS FORTH TECHNICAL COMMITTEE
Message-ID: <2381.UUL1.3#5129@willett.pgh.pa.us>
Date: 21 Feb 91 01:11:14 GMT
References: <2359.UUL1.3#5129@willett.pgh.pa.us>
Organization: (n.) to be organized.  But that's not important right now.
Lines: 20

In <2359.UUL1.3#5129@willett.pgh.pa.us>,
	B.RODRIGUEZ2 [Brad] writes:
> Doug Philips writes:
> 
> > ...what I really really want is a way to write Forth code that will
>  > run on more than one Forth and more than one processor....
>  > Portability is my main interest in this ANSI process.
> 
> Interesting.  I've had relatively little trouble porting applications from
> processor to processor.  It's moving from "standard" to "standard" that gives
> me headaches.

Ok, perhaps I should be a bit more explicit.  I was thinking of PC versus
Unix (Sun, Apollo, etc).  PC-Forths versus C-Unix Forths.  Since there is
no wide spread defacto standard, switching from processors implies (or so
I tried to assume) switching between standards.

-Doug
---
Preferred:  dwp@willett.pgh.pa.us	Ok:  {pitt,sei,uunet}!willett!dwp