I've closed STR 1949 since, with Albrecht and Fabien's patches in
place, it now seems to do the Right Thing in tests on OSX, Linux,
WinXP and Vista. (WinXP and Vista builds tested with mingw and cygwin.)
Now... given that the fix works, do we want to back-port it into
fltk-1.1.x, since the
Whilst investigating STR 2080, I tripped over a feature in WinXP
(and possibly also in Vista) described in STR 2086.
Can I ask others that have access to WinXP and Vista test systems to
try the failure recipe I describe and report whether the fault is
reproducible or not?
Thanks,
--
Ian
imacarthur wrote:
Whilst investigating STR 2080, I tripped over a feature in WinXP
(and possibly also in Vista) described in STR 2086.
Can I ask others that have access to WinXP and Vista test systems to
try the failure recipe I describe and report whether the fault is
reproducible or
On 11 Nov 2008, at 22:03, Greg Ercolano wrote:
Can I ask others that have access to WinXP and Vista test systems to
try the failure recipe I describe and report whether the fault is
reproducible or not?
Reproduced on Vista.
I don't have the latest checkout, but have a somewhat
No, it's just there compiler being stupid. That's a useful *warning* but
it should not be an error!
The workaround everybody uses is to replace int(ptr) with
int(long(ptr)). I changed it to this and checked it in.
Changing the values to size_t will just make warnings appear somewhere else.
imacarthur wrote:
Whilst investigating STR 2080, I tripped over a feature in WinXP (and
possibly also in Vista) described in STR 2086.
Can I ask others that have access to WinXP and Vista test systems to try
the failure recipe I describe and report whether the fault is
reproducible or not?
FLTK mostly uses xyz(value) to set, and xyz() to get.
And I just _love_ that approach!
___
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
Furthermore, Bill, I am just talking on IRC with a guy who contributed
few important patches to FLTK2, and here is what he says (interesting):
traeak taking a 64bit pointer value
traeak then tossing the upper 32bits
traeak and using that as a hash value
traeak or index value
traeak
Dejan Lekic wrote:
FLTK mostly uses xyz(value) to set, and xyz() to get.
And I just _love_ that approach!
Seems fine to me.
The only way it might get confusing is if xyz is an action verb,
like explode, in which case a programmer might accidentally code:
//
Greg, I can only agree.
IMHO there was a paragraph in our code standards document about what I
said previously, however, some people did not follow strictly that
standard...
___
fltk-dev mailing list
fltk-dev@easysw.com
The workaround everybody uses is to replace int(ptr) with
int(long(ptr)). I changed it to this and checked it in.
I do not see this change Bill, will you _please_ check if you perhaps
did not check it in? :)
___
fltk-dev mailing list
[STR Closed w/Resolution]
Link: http://www.fltk.org/str.php?L1935
Version: Web Site
Fix Version: Current
Link: http://www.fltk.org/str.php?L1935
Version: Web Site
Fix Version: Current
___
fltk-dev mailing list
fltk-dev@easysw.com
12 matches
Mail list logo
