[armedbear-devel] jcall and t/nil boolean arguments

Alessio Stalla alessiostalla at gmail.com
Fri Jan 29 21:16:08 UTC 2010

On Fri, Jan 29, 2010 at 10:07 PM, Erik Huelsmann <ehuels at gmail.com> wrote:
> Hi Alan,
> On Fri, Jan 1, 2010 at 9:37 PM, Alan Ruttenberg
> <alanruttenberg at gmail.com> wrote:
>> Can it be made so that within jcall, t or nil is understood as a java
>> boolean argument?
> Thanks for the idea. I've filed a ticket for it in order to prevent it
> from getting lost.

Ok for T, but NIL currently means null and I'd like it to stay that
way. We could treat it as false for boolean arguments only, but:

- what to do with java.lang.Boolean? null or false?
- method resolution becomes more complicated: does (jcall "foo" nil)
select foo(boolean) or foo(Object)?

by the way, I'm not sure about the handling of nil for method
resolution even now, as there can be an ambiguity among different
overloads when you pass null; I believe we should signal an error in
that case, and I'm pretty sure we don't do it now.

Just my .02€

More information about the armedbear-devel mailing list