Hi Peter, On Tue, 2002-12-10 at 03:30, Peter B. West wrote: > Fop-devs, > > I have just run some quick test of property generation, to determine > whether I was actually generating the property sets for the FOs. > Although there are obviously still some bugs in property generation, the > full property sets are being generated. > > I don't think that almost halving the memory usage of the FO tree build > can be accounted for by "unused variables" in the maint code. Rather, > it seems that the rewrite of FO tree building and property > representation has achieved its design goal: significantly reduced > memory usage.
It must be somewhere, used variables maybe ;) It could well be mostly in the properties. Anyway that's great. The only questions I have at the moment: - are markers handled properly, you mentioned something about that earlier so maybe it is dealt with already - what about arbitrary xml anywhere for extensions, is that still possible (also instream-foreign-object but that is probably okay) I know it is not a spec thing but it can enhance using FOP for many users. > To my surprise, it also runs faster, in spite of using an admittedly > less efficient pull parsing method implemented over the top of SAX. > Taking advantage of native pull parsing APIs when they become available > (and the Neko pull parser is slated for release with Xerces soon) will > increase the performance. Fast and low memory is good. > Now if I can work out Forrest, I'll update the documentation. > > Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
