Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!apple!sun-barr!decwrl!adobe!greid
From: greid@adobe.com (Glenn Reid)
Newsgroups: comp.lang.postscript
Subject: Re: commenting out blocks of code
Message-ID: <1121@adobe.UUCP>
Date: 27 Aug 89 09:08:30 GMT
References: <4300@imagen.UUCP>
Sender: news@adobe.COM
Reply-To: greid@adobe.COM (Glenn Reid)
Organization: Adobe Systems Incorporated, Mountain View
Lines: 31

In article <4300@imagen.UUCP> geof@apolling (Geof Cooper) writes:
>In article <1100@adobe.UUCP> greid@adobe.COM () writes:
>>{ %%%%%%%%%%%
>>
>>} pop %%%%%%%
>
>The only problem you might encounter is the limit described in the
>green book on the length of arrays that can be generated by the parser
>so you might get a limitcheck on processing a very long "comment".
>Since you wrote the green book, I guess you know about that one.
>
>- Geof

Yeah, I vaguely remember that part of the green book :-)

You're right about that (except that it raises a stackoverflow on
our implementations, not a limitcheck, I think).

Luckily this is a limit you don't run into very often, but if you
were commenting out a big block of stuff that was machine-generated
(and hence had no { } arrays inside it) you would have problems,
it's true.  That's where a technique that just reads and discards
a bunch of data up through some %%Flag comes in handy, although it
is enough more work that I think just deleting with a text editor
probably starts to look more appealing.

Heck, none of us on this newsgroup ever needs to comment anything
out anyway, do we?  Doesn't it usually work the first time?

Thought so,
 Glenn