John Rose wrote:
> When you call a function of type, say, (B), you are promising that the
> 32-bit int you loaded onto the stack fits into the declared subrange,
> say, -128..127.
>
> (This is a little-known invariant of the verifier. Although all
> primitive arguments and return values are passe
On Aug 25, 2011, at 11:23 PM, Jeroen Frijters wrote:
> I was surprised by this as well (from an implementers point of view), because
> the use of asType is an implementation detail. Normally when you call a
> method taking a boolean/byte/short/char you also load an int onto the stack,
> so why
Hi all,
I was surprised by this as well (from an implementers point of view), because
the use of asType is an implementation detail. Normally when you call a method
taking a boolean/byte/short/char you also load an int onto the stack, so why
would this case be any different?
Not that it makes
That's a good suggestion; thanks. -- John
On Aug 25, 2011, at 11:06 AM, Rémi Forax wrote:
> Hi John, hi all,
> several people (2 actually :) ask me how to use a boolean/byte/short/char
> as a bootstrap argument.
>
> As you know, you can't because you can't encode a constant
> boolean/byte/shor
