🚀 go-pugleaf

In article <1990Oct19.160619@bendenweyr.Eng.Sun.COM> flar@bendenweyr.Eng.Sun.COM (Jim Graham) writes:
>In article <1990Oct18.204534.9186@julius.cs.uiuc.edu>,
>nelson@melodian.cs.uiuc.edu (Taed Nelson) writes:
>
>> [Some PS code involving rlineto]
>
>What am I missing here?  In the first repeat loop, a lot of moveto
>rlineto's get generated but the result is never stroked or filled,
>it is just thrown away with a newpath.  What's the point (only side
>effect that I can see is the execution of 20 rand's, so it essentially
>just throws out 20 random numbers and takes a long time to do it.

But it *does* move the Current Point. There is *no* gsave ... grestore,
so this has the effect of going through the IFS transformations,
and eventually places ink at the appropriate places..

--
Daniel Carosone,
System Administrator,
TeXworks (Australia) Pty. Ltd.
From postnews Sun Oct 21 19:17:08 1990
In article <1990Oct19.160619@bendenweyr.Eng.Sun.COM> flar@bendenweyr.Eng.Sun.COM (Jim Graham) writes:
>In article <1990Oct18.204534.9186@julius.cs.uiuc.edu>,
>nelson@melodian.cs.uiuc.edu (Taed Nelson) writes:
>
>> [Some PS code involving rlineto]
>
>What am I missing here?  In the first repeat loop, a lot of moveto
>rlineto's get generated but the result is never stroked or filled,
>it is just thrown away with a newpath.  What's the point (only side
>effect that I can see is the execution of 20 rand's, so it essentially
>just throws out 20 random numbers and takes a long time to do it.

But it *does* move the Current Point. There is *no* gsave ... grestore,
so this has the effect of going through the IFS transformations,
and eventually places ink at the appropriate places..

--
Daniel Carosone,
System Administrator,
TeXworks (Australia) Pty. Ltd.