Michael Van Canneyt <[EMAIL PROTECTED]>:
> Apparently not. The patch was studied by Peter: > 1. It introduces a new feature, and as such will be only intyroduced > after 2.0 has been released. No trouble, it means that all interface features I'm implementing will probably (multilpe inheritance, object properties, interface handlers) go there (if accepted). It just means that I have more time to fit your needs better. > 2. As a side effect, it allows assigning any class to any class, > which is definitely wrong. > Easy fix, what do you need a compiler or runtime error? If I find time it may be today, but surely until start of the next week (I will not have my notebook where I'll reside, just public terminal). If I get it correctly, compiler error. > Seems like after the patch too much wrong code is allowed to work as well :) > > But I'm not qualified to speak about the compiler patches. Peter or > Florian should do that. > Ok, no flexibility (:Doing other features too, and I didn't test object to object:) That was the reason for my try to ask questions "how would you like?" (I think that I at least 4 times asked whom to talk about how to implement). Now you finally said how. And patch will be corrected to fit constraints. It is not my project and the last thing I would like would be enforcing unwanted boundaries (or the lack of it, it can still exist as my patch). regards ml > Michael. > > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > ---------------------------------------------------------------------- This mail sent through Horde-Toaster (http://qmailtoaster.clikka.com/) _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
