I wasn't intending to use just an Object in the first place, so it seems to
be non-issue. For now anyways, hopefully the comment I put in reminds not to
stick a plain Object in there later on.
obj was going to be return of some event handler, to redirect to some page.
I set to to a plain Object
> obj being null results in false just fine. But doing "obj = new Object()"
> makes it explode
Sounds like a missing coercion, but what's your use case?
-- Josh
On Aug 30, 2010, at 4:45 AM, LLTYK wrote:
>
> So I have this:
>
>
> obj being null results in false just fine. But doing "obj
So I have this:
obj being null results in false just fine. But doing "obj = new Object()"
makes it explode. Oddly enough, "obj = new Integer(1)" (and presumably any
other subclass of Object), works just fine.
An unexpected application exception has occurred.
Render queue error in BeginRen
