Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Creating a PrintWriter: No matching ctor found
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Stuart Sierra  
View profile  
 More options Jan 5 2008, 11:34 pm
From: "Stuart Sierra" <the.stuart.sie...@gmail.com>
Date: Sat, 5 Jan 2008 23:34:49 -0500
Local: Sat, Jan 5 2008 11:34 pm
Subject: Re: Creating a PrintWriter: No matching ctor found

On Sat, 2008-01-05 at 11:36 -0800, Rich Hickey wrote:
> I am considering
> supplying constants that correspond to the values Boolean.TRUE and
> Boolean.FALSE for use in _calling_ Java, but I won't change the nature
> of conditional tests to also test for FALSE - it's a performance issue
> I decided long ago.

Just my 2 cents: I like Ruby's "true", "false", and "nil" keywords.
Ruby treats both "false" and "nil" as false in boolean expressions;
anything else is considered true.  It's very clear when you're
returning a boolean value, but you still get the convenience of using
nil in boolean expressions.

Having true/false/nil map exactly to Java true/false/null (boxed if
necessary) would avoid confusion over the type conversions.

-Stuart


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.