[Gtkradiant] [Bug 1109] Wrong calculation ofBEZIERCURVETREE_MAX_INDEX

[Ondrej Svetlik]

Joseph, William wrote:
> The calculation uses size_t because BEZIERCURVETREE_MAX_INDEX is
> supposed to be the largest integer representable with a native type on
> whatever architecture you're compiling for - if it was supposed to be
> the same on all architectures then it would just be:
> 
> const std::size_t BEZIERCURVETREE_MAX_INDEX = 2147483648;
> 
> Though it never really needs to be that big anyway =).
> 
> -SPoG
> 
> 
> -----Original Message-----
> From: gtkradiant-bounces at zerowing.idsoftware.com
> [mailto:gtkradiant-bounces at zerowing.idsoftware.com] On Behalf Of
> bugzilla-daemon at zerowing.idsoftware.com
> Sent: 12 September 2006 14:13
> To: gtkradiant at zerowing.idsoftware.com
> Subject: [Gtkradiant] [Bug 1109] Wrong calculation
> ofBEZIERCURVETREE_MAX_INDEX
> 
> http://zerowing.idsoftware.com/bugzilla/show_bug.cgi?id=1109
> 
> 
> spam at codecreator.net changed:
> 
>            What    |Removed                     |Added
> ------------------------------------------------------------------------
> ----
>              Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> 
> ------- Additional Comments From spam at codecreator.net  2006-09-12 08:13
> -------
> Yes 2147483648 is correct.
> 
> The bitshift code is not from me, please don't ask me why it uses size_t
> ;)
> Added the fix to trunk.
> 

We still can use size_t, that's up to you, I'm glad it's no more a 0. ;-)

How can I actually test it? It compiles without a warning, but what 
should I do in the editor to prove it works?

Regards,

Ondrej