Message from discussion
Creating a PrintWriter: No matching ctor found
MIME-Version: 1.0
Message-ID: <95c1692d-f613-4983-b11a-aa1a62dea8a2@i29g2000prf.googlegroups.com>
Date: Sat, 5 Jan 2008 13:31:57 -0800 (PST)
Received: by 10.151.6.2 with SMTP id j2mr326325ybi.20.1199568717457; Sat, 05
Jan 2008 13:31:57 -0800 (PST)
In-Reply-To: <a0aa389d0801051301o3f66cb6fsd6233125d3a55e34@mail.gmail.com>
X-IP: 67.86.170.109
References: <01c793a1-adf8-4a40-a145-247935a85ef0@q77g2000hsh.googlegroups.com>
<892229d1-4d3e-4457-98a9-4cbd367365d2@1g2000hsl.googlegroups.com>
<bb9eccdb-35fd-49ad-a13e-9d96f667902f@v4g2000hsf.googlegroups.com>
<1199462382.6103.24.camel@laptop-wittner> <256abf67-b545-4fab-b73d-c1eefea4d64f@d21g2000prf.googlegroups.com>
<1199541325.6131.26.camel@laptop-wittner> <c4ba2c0f-0b40-4116-8640-187be0407830@d21g2000prf.googlegroups.com>
<1199558272.6131.101.camel@laptop-wittner> <c32098f6-bd78-400d-83a7-eeed853a3cc1@f47g2000hsd.googlegroups.com>
<6ec9aa1f-0599-4035-8292-43bebd451333@y5g2000hsf.googlegroups.com>
<a0aa389d0801051301o3f66cb6fsd6233125d3a55e34@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.4)
Gecko/20070509 Camino/1.5,gzip(gfe),gzip(gfe)
Subject: Re: Creating a PrintWriter: No matching ctor found
From: Rich Hickey <richhic...@gmail.com>
To: Clojure <clojure@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On Jan 5, 4:01 pm, "John Cowan" <johnwco...@gmail.com> wrote:
> On Jan 5, 2008 2:36 PM, Rich Hickey <richhic...@gmail.com> wrote:
>
> > - They will represent Boolean.TRUE and Boolean.FALSE, and will have
> > type Boolean
>
> > - only Booleans will implicitly convert to match boolean arguments in
> > calls to Java, as now
>
> > - Conditionals will test for nil/non-nil, as now
>
> > - boolean returns from Java will be converted into nil/:t, as now
>
> > - the boolean coercion operator will still be available to transform
> > Clojure logical values to Java logical values, as now
>
> Then I suggest "javatrue" and "javafalse", or any shortening or
> punctuating of that (jtrue, java-true, whatever) that suits you.
>
> I would also suggest a convenience function "javatruth" that maps
> nil/non-nil to javafalse and javatrue, so you can say things like
> (java-function (javatruth (another-java-function)))
> where java-function expects a Boolean and another-java-function returns one.
That's what the boolean coercion op does now. Note that this won't be
needed unless the calls are reflective.