Michael Van Canneyt wrote:
Nono, it's good that you fixed your bug.
You should never rely on the loading order. For forms, for instance, it is
dependent on the creation in the IDE. A simple cut and paste could change
the order. Relying on this would be bad practice.
Absolutely
The other thing that struck me is that unsatisfied references do not throw an
error - shouldn't they? (It would have made fixing the error a little easier)
How about the following patch:
Delphi doesn't throw an error either, and it should definitely not do so at the
end of local reference resolving; At most this could be done after all loading
is done, and you don't know when that is: forms can be created at any time...
It still seems strange not to throw an error. The point I suggested is
the first time that it is definitely known that the local reference will
never be resolved, as at that point the reference is simply thrown away
if not resolved. (Or am I missing something?)
Colin
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
