Issue status update for
http://smalltalk.gnu.org/project/issue/82 Post a follow up: http://smalltalk.gnu.org/project/comments/add/82 Project: GNU Smalltalk Version: <none> Component: XML Category: tasks Priority: normal Assigned to: Reported by: bonzinip Updated by: elmex Status: active I've thought about this too when writing the Expat binding. But currently I just do a <prereq>XML</prereq>. But splitting XML.st up would be indeed very useful for maintenance reasons (i lost a bit the overview in that big file :). If I find the time I might even do this. elmex Previous comments: ------------------------------------------------------------------------ Fri, 28 Sep 2007 06:51:03 +0000 : bonzinip SAX, DOM and the parser are logically separate parts but they are included in a single package. This is necessary in order to support other parsers such as Expat. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Issue status update for
http://smalltalk.gnu.org/project/issue/82 Post a follow up: http://smalltalk.gnu.org/project/comments/add/82 Project: GNU Smalltalk Version: <none> Component: XML Category: tasks Priority: normal Assigned to: Reported by: bonzinip Updated by: bonzinip Status: active Starting from a syntax-converted version, it should be much easier. bonzinip Previous comments: ------------------------------------------------------------------------ Fri, 28 Sep 2007 06:51:03 +0000 : bonzinip SAX, DOM and the parser are logically separate parts but they are included in a single package. This is necessary in order to support other parsers such as Expat. ------------------------------------------------------------------------ Fri, 28 Sep 2007 09:14:33 +0000 : elmex I've thought about this too when writing the Expat binding. But currently I just do a <prereq>XML</prereq>. But splitting XML.st up would be indeed very useful for maintenance reasons (i lost a bit the overview in that big file :). If I find the time I might even do this. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Issue status update for
http://smalltalk.gnu.org/project/issue/82 Post a follow up: http://smalltalk.gnu.org/project/comments/add/82 Project: GNU Smalltalk Version: <none> Component: XML Category: tasks Priority: normal Assigned to: Unassigned> Reported by: bonzinip Updated by: bonzinip Status: active (By the way, this task was indeed inspired by your Expat bindings). _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Issue status update for
http://smalltalk.gnu.org/project/issue/82 Post a follow up: http://smalltalk.gnu.org/project/comments/add/82 Project: GNU Smalltalk Version: <none> Component: XML Category: tasks Priority: normal Assigned to: Unassigned Reported by: bonzinip Updated by: bonzinip Status: active I split the big single source code file into several smaller ones, and abstracted parts of XMLParser into a superclass SAXParser. It is still one big package, but it is easier to separate it (Robin, wanna try?...) and from SAXParser you can derive your Expat parser. That's done in *[hidden email]--2004b/patch-598*. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Issue status update for
http://smalltalk.gnu.org/project/issue/82 Post a follow up: http://smalltalk.gnu.org/project/comments/add/82 Project: GNU Smalltalk Version: <none> Component: XML Category: tasks Priority: normal Assigned to: Unassigned Reported by: bonzinip Updated by: bonzinip -Status: active +Status: fixed Fixed in patch-625. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Free forum by Nabble | Edit this page |