Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!texbell!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.lang.forth
Subject: Re: multi-line comments
Message-ID: <U.X3NGC@xds13.ferranti.com>
Date: 5 Jun 90 15:57:44 GMT
References: <9006041403.AA15819@ucbvax.Berkeley.EDU>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 25

In article <9006041403.AA15819@ucbvax.Berkeley.EDU> Mitch Bradley <wmb%MITCH.ENG.SUN.COM@SCFVM.GSFC.NASA.GOV> writes:
> The tools to create whatever comment style you prefer are now present,
> with the recent extensions to QUERY, the new word PARSE, and the precision
> with which the semantics of text file loading is now specified.

Well, my concern is that the semantics are too precise. 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. If you can't get the
semantics of divide right, why overspecify here?

> > What makes you think [ Setjmp and longjmp require the allocation of
> > global memory ] ?

> As Henk Lengeveld has also pointed out, the variable of type "jmp_buf"
> which allows longjmp() to rendezvous with setjmp() is a global variable
> in the sense that its storage must be allocated statically.

Why? What's wrong with:

	foo()
	{
		jmp_buf bar;

		...
	}
-- 
`-_-' Peter da Silva. +1 713 274 5180.  <peter@ficc.ferranti.com>
 'U`  Have you hugged your wolf today?  <peter@sugar.hackercorp.com>
@FIN  Dirty words: Zhghnyyl erphefvir vayvar shapgvbaf.