>second, for hoots and hollers, i subclassed/extended the SAXFilter >class ... thinking that it looked like the descendent of everything >else, thinking that it was itself the parser and handler, and tried to >override some of the callback functions ... but when i call parse on >it, i get an error about abstract methods.
If you forget the override keyword after a function declaration, you may get abstract errors. You can't call an abstract function directly. I'm not sure if this has anything to do with it, but maybe Java's class ancestor/inheritance system is a bit different causing you issues since you come from that background and have memorized how to code classes that way. Would need to see some sample code that is giving you the abstract error, though. I just finished dealing with an "abstract error" and all I did was forget to place the override keyword after the function declaration in the *derivative* class. Just to add to the confusion: Tstrings is abstract.. so calling something like TStrings.create isn't right but TStringList.create is okay. begin ObjectOrientation:= confusion end; _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
