Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS FORTH TECHNICAL COMMITTEE
Message-ID: <2359.UUL1.3#5129@willett.pgh.pa.us>
Date: 18 Feb 91 02:00:30 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 32

Category 10,  Topic 2
Message 322       Sat Feb 16, 1991
B.RODRIGUEZ2 [Brad]          at 16:23 EST
 
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.

To Mitch Bradley, in reply to my && and || query:

My thanks, you are quite correct, and I sit corrected!  They're not difficult
to implement, just inefficient in space.  (Normally I do them in machine code,
anyway.)

And thanks to Ulrich for catching your (minor) code error.  Either way, it
illustrates the technique.

Brad Rodriguez        | brad%candice@maccs.uucp      (God willing)
 B.RODRIGUEZ2 on GEnie | brad%candice@maccs.dcss.mcmaster.ca
 "Shoes for industry!" | bradford@maccs.dcss.mcmaster.ca  (archaic)

-----
This message came from GEnie via willett.  You cannot Reply to the author
using email.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, whatever).
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp