Re: hard-coding MAX_WIDTH and MAX_HEIGHT (was: patch-fu)

[email protected] wrote:
> Agreed. howabout in my next set of patches, i apply something that creates
> a MAX_WIDTH and MAX_HEIGHT define, that we use for spots that "need" a 
> hard coded value at compile time, and continue to use width and height
> for things that dont require hard coding?
>
>   
That would be a whole lot nicer than using 65536 :). Then you can do 
your static compile time memory allocation, but still pass width and 
height parameters into the routines to determine how much of this buffer 
gets used.

Cheers,

David


-- 
Dr David McG. Squire, Senior Lecturer, on sabbatical in 2006
Caulfield School of Information Technology, Monash University, Australia
CRICOS Provider No. 00008C        http://www.csse.monash.edu.au/~davids/