Fox::TRUE and Fox::FALSE conflict with Ruby TRUE and Ruby FALSE
Reported by lyle (at lylejohnson) | November 11th, 2009 @ 10:38 PM | in 1.8.0
After "require 'fox16'" we have:
Fox::TRUE -> 1
Fox::FALSE -> 0
Fox::MAYBE -> 2
Meanwhile, Ruby has built-in constants:
TRUE -> true
FALSE -> false
So after "include Fox", we have:
TRUE -> true
FALSE -> false
MAYBE -> 2
To avoid confusion, perhaps in FXRuby, Fox::TRUE and Fox::FALSE could be renamed or even abolished entirely?
Comments and changes to this ticket
-
lyle (at lylejohnson) November 11th, 2009 @ 10:39 PM
- Milestone set to “1.8.0”
I didn't even realize that Ruby defined those constants. Ugh. Yes, we ought to see if we can get rid of those in FXRuby 1.8. I don't want to make that kind of API change in FXRuby 1.6 since it breaks compatibility with those folks who may already be using Fox::TRUE and Fox::FALSE.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
FXRuby is a library for developing powerful and sophisticated cross-platform graphical user interfaces (GUIs) for your Ruby applications. It’s based on the FOX Toolkit, a popular open source C++ library developed by Jeroen van der Zijp. What that means for you as an application developer is that you’re able to write code in the Ruby programming language that you already know and love, while at the same time taking advantage of the performance and functionality of a featureful, highly optimized C++ toolkit.
lyle (at lylejohnson)