Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Fox::TRUE and Fox::FALSE conflict with Ruby TRUE and Ruby FALSE

#30

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?

Reported by lyle (at lylejohnson) · November 11th, 2009 @ 10:38 PM

State: new
Milestone: 1.8.0
Assigned to: lyle (at lylejohnson) lyle (at lylejohnson)

Activity

  1. lyle (at lylejohnson)
    lyle (at lylejohnson)
    • 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.

    November 11th, 2009 @ 10:39 PM

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.