>
>
> So isset(UNDEFINEDCONSTANT) will be isset("UNDEFINEDCONSTANT") which
> will/should
> 1) yield a notice, which is unnexpected for isset
> 2) return true, which is also unexpected.
>
> I don't see much point in that.
>
>
yep, and if we allow expressions then it is the expected behavior, but you
are right that this is will change the current standard that isset/empty
can't raise a notice.
but this isn't specific to isset, empty will also follow the same pattern.-- Ferenc Kovács @Tyr43l - http://tyrael.hu
