Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!aplcen!haven!umd5!zben
From: zben@umd5.umd.edu (Ben Cranston)
Newsgroups: comp.lang.postscript
Subject: Re: PostScript vs TrueType?
Summary: I think the skipping code itself is broken
Message-ID: <7214@umd5.umd.edu>
Date: 29 Aug 90 20:03:56 GMT
References: <9724@goofy.Apple.COM> <438@three.mv.com> <9931@goofy.Apple.COM> <258@heaven.woodside.ca.us> <1513@chinacat.Unicom.COM>
Reply-To: zben@umd5.umd.edu (Ben Cranston)
Organization: University of Maryland, College Park
Lines: 41

In article <1513@chinacat.Unicom.COM> woody@chinacat.Unicom.COM
(Woody Baker @ Eagle Signal) writes:

> ...  This is not a complete font, most of the guts have been
> cut out, but there should be enough here to demonstrate the problem.

>	/Casa1 known		% if the preamble was known
>		{
>			{
>			currentfile(   )readstring
>				{
>				(%%%)eq		%look for separator
>					{
>					exit
>					}if
>				}
>				{
>				pop		%hangs, looking forever
>				}ifelse
>			}loop
>		}if

I think this is broken.  Seems to me this will read 3-character chunks from
the input and compare them against %%%, but if the stuff being skipped is
not EXACTLY a multiple of 3 characters long you could get a test against
<newline> % %  or % % <somethingelse> and fail to find the target.
Remember that (according to red book) readstring does NOT stop on line bdry!

Perhaps if you used readline, gave it a fairly longish string to read into,
                        ====
and used an anchorsearch to match the three first characters on the line,
            ============
this could be made to work...

Am I off base?

-- 
Ben Cranston <zben@umd2.umd.edu>
A determined iconoclast, it would be better to assume the opinion expressed
above is the diametric OPPOSITE to that of the Warm and Fuzzy Network Group
of Egregious State University...