On Tue, 2 Nov 2004 03:29:06 +0900, Mohammad Khan <mkhan / lextranet.com> wrote:
> On Sat, 2004-10-30 at 01:47, "Pe?a, Botp" wrote:
> > //I still don't see a reason for #true? and #false?.
> >
> > it's a language problem. ruby caters english and sometimes the language does
> > not fall immediately into ones (non-english) ears... Thus the op was asking
> > if he could be more explicit+...
> >
> > consider:
> >
> > a = (1 > 0)
> 
> this will return a boolean, so it doesn't fit in my example.
> try, a = Foo.new and consider your examples.
> You will know, what I mean.

No, I'm sorry, I *don't* know what you mean. Foo.new is a true value.

I'm not seeing the purpose of this. Really.

-austin
-- 
Austin Ziegler * halostatue / gmail.com
               * Alternate: austin / halostatue.ca
: as of this email, I have [ 5 ] Gmail invitations