I was aware that changes to static variables no longer trigger
binding to execute, but including static variables in a binding
shouldn't cause compilation errors.
Considering the fact that the compiler fails to identify the line
that contains the error, and the fact that the error messages
but including static variables in a bindingshouldn't cause compilation errors.sense in that context, lead me to the conclusion this must be a
compiler bug.
agreed, actually one of our engineers spent two days to spot this and
remove all static variable bindings then all the weird compliation
2 matches
Mail list logo
