[Gtkradiant] [Bug 1109] Wrong calculation ofBEZIERCURVETREE_MAX_INDEX

namespace spam at codecreator.net
Tue Sep 12 10:42:48 CDT 2006

> 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

So it just needs to be the numeric max of size_t, ok I didn't knew that.
Are there any special reasons why it was done with bitshift magic?
The STL way looks clearer to me.


Home: www.codecreator.net |
GPG: http://www.codecreator.net/gpg-public.asc | 0xD4BD516D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://zerowing.idsoftware.com/pipermail/gtkradiant/attachments/20060912/6351980e/attachment.pgp

More information about the Gtkradiant mailing list