Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!comp.vuw.ac.nz!windy!srwmcln
From: srwmcln@windy.dsir.govt.nz
Newsgroups: comp.lang.postscript
Subject: Re: Behaviour of pathbbox in Level 2
Message-ID: <18802.278fb9b8@windy.dsir.govt.nz>
Date: 13 Jan 91 01:36:56 GMT
References: <5706@exodus.Eng.Sun.COM> <9924@adobe.UUCP>
Organization: DSIR, Wellington, New Zealand
Lines: 26

In article <9924@adobe.UUCP>, taft@adobe.com (Ed Taft) writes:
> This situation cannot arise. When multiple consecutive movetos are executed,
> each causes the preceding one to be discarded. See the moveto operator
> description. Thus, it's possible to have at most a single isolated moveto at
> the end of a path.
> 
Well that may have been what the Red book said, but on our IINT with V38
PostScript I found the following:

0 0 moveto
1 1 moveto
2 2 lineto
3 3 lineto
pathbbox


gave 0 0 3 3  rather than 1 1 3 3.

I can only assume that in the IINT inplementation either (i) That all moveto's
are kept in the path and that it is upto path operators to discard useless
moveto's, which pathbbox seems not to or (ii) The path keeps track of the bbox
at all times and just forgets what it says in the Red book about moveto's.

But, I'm glad the 2rd edition clears up the trailing moveto problem.

Clive.