We saw this when creating an instance variable of type Object - when implicitly
generating an "oper new", the compiler will only generate a call to "oper bind"
for the object if there is one defined - but if the oper bind is defined after
the object, it will silently omit it.
We need to emit an error if the user defines "oper bind" after an "oper new"
has been generated.
Original issue reported on code.google.com by mind...@gmail.com on 26 Oct 2010 at 11:27
Original issue reported on code.google.com by
mind...@gmail.com
on 26 Oct 2010 at 11:27