Alexander Klenin <kle...@gmail.com>: > 2) In OBJFPC mode, do not accept "abstract" keyword and change warning to > error.
Please don't. At least in the past there were quite some classes in the FCL that did not implement all declared methods (IIRC also in fpImage). Honestly, sometimes I don't even know what they are supposed to do and thus - don't know how to implement them. Obviously this also means, they are placeholders for something which I don't need right at the moment. Forcing the programmer to implement such, when he doesn't even know what for, is definitely more annoying than a warning. As an example, there are/were "Open" and "Close" methods in TXHTMLDocument, which I finally implemented with a null-method just to get rid of the warnings when instantiating descendants. The missing documentation tells me - nothing. Of course. So I suppose, these methods are really very important and the whole program will fail if they are neither implemented nor called. :P Vinzent. -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
