Re: General bug - No out of bounds checking on 3D coordinates

[Hans-Bernhard B. <br...@ph...>]

On Mon, 5 Jul 2004, Ethan Merritt wrote:

> On Monday 05 July 2004 10:38 am, Daniel J Sebald wrote:
> > I don't understand why negative coordinates is an error.
> 
> The error is not the fact that it's negative.  The error is that after 
> stuffing it into an (unsigned int) it looks like a huge positive number
> instead.

Not quite, IMHO.  The fact that casting a negative will result in
ridiculously large positive coordinates passed to terminal functions is a
*second* error, which is a consequence of the original one: that stuff was
output outside the page boundary.

> That would be a big change, though. 

I'm aware of that.  If it weren't, I would have insisted on getting that
fixed before considering the thing fit for the 4.0 release.  But if now
isn't the time for big changes, when is?

> The problem I've run into is that the PDF library doesn't clip in
> these cases, it just causes the program to exit.  

So our PDF driver *must* do its own "emergency" clipping, no matter
what we do in the core routines.

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.