Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!ucbvax!MITCH.ENG.SUN.COM!wmb
From: wmb@MITCH.ENG.SUN.COM (Mitch Bradley)
Newsgroups: comp.lang.forth
Subject: ANS Forth
Message-ID: <9006051819.AA27558@ucbvax.Berkeley.EDU>
Date: 5 Jun 90 18:14:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Mitch Bradley <wmb%MITCH.ENG.SUN.COM@SCFVM.GSFC.NASA.GOV>
Organization: The Internet
Lines: 32

> By making multi-line comments part of the standard, you prevent the use of
> a simple get-a-line-and-feed-it-to-interpret style of file loader.

Not true.  The file loader semantics IS specified as "get-a-line-and-feed-
it-to-interpret".  "(" is responsible for refilling the input buffer as
needed until the closing ")" is encountered.  That is why the QUERY function
(which refills the input buffer) has been extended to apply to text files
in addition to the keyboard.

> If you can't get the semantics of divide right

The semantics of divide, in all its flavors, ARE right.  It is just the
spelling that is in question.


> What's wrong with:
>
>       foo()
>       {
>               jmp_buf bar;
>               ...
>       }

It is useless because the name scope of "bar" is the definition "foo",
so any setjmp()/longjmp() pair using "bar" would have to be entirely
contained inside "foo".  It is nearly always the case that setjmp() and
longjmp() are called from different procedures.  There is little reason
to use a setjmp()/longjmp() pair inside a single procedure, because
other control structures like "while" or "goto" work better within a
procedure.

Mitch Bradley