On 11/06/2013 05:42 AM, Andrew Haley wrote:
On 11/04/2013 05:21 PM, Jason Merrill wrote:
Surely it should be valid to allocate a Java boolean type. Andrew,
how should that work?
It's not allowed. All objects that are allocated by new must be of
class type (i.e. instances of a subclass of ja
On 11/04/2013 05:21 PM, Jason Merrill wrote:
> Surely it should be valid to allocate a Java boolean type. Andrew,
> how should that work?
It's not allowed. All objects that are allocated by new must be of
class type (i.e. instances of a subclass of java.lang.Object), but
boolean is a primitive
On 11/04/2013 06:21 PM, Jason Merrill wrote:
Surely it should be valid to allocate a Java boolean type. Andrew,
how should that work?
Thanks. The problem we are facing (assuming we want to resolve this old
isue) is that something seems seriously broken for the builtin Java
types as declared in
Surely it should be valid to allocate a Java boolean type. Andrew, how
should that work?
Jason
Hi,
we have got this very old bug, where we ICE in build_java_class_ref
because TYPE is an INTEGER_TYPE and we try to use TYPE_FIELDS on it.
Shall we apply something like the below and resolve it for good?
Alternately, we could maybe provide the same message we currently
provide in release-bu
