[Gtkradiant] [Bug 1109] Wrong calculation ofBEZIERCURVETREE_MAX_INDEX

Joseph, William WJoseph at europe.ea.com
Tue Sep 12 08:22:41 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 =).


-----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


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.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Gtkradiant mailing list
Gtkradiant at zerowing.idsoftware.com

More information about the Gtkradiant mailing list