On 28 May 2010 11:25, James Paige <[email protected]> wrote: > On Thu, May 27, 2010 at 07:07:38PM -0400, Mike Caron wrote: >> On 27/05/2010 6:38 PM, James Paige wrote: >> >Mike, was there any special reason why Reload.SerializeXML uses print >> >statements rather than writing to a file? >> > >> >--- >> >James >> >> I wrote it as a debugging function. If it wrote to a file, then I >> wouldn't be able to see it on screen in reloadtest! :) >> -- >> Mike > > I guess what I am really looking for is a reload2xml command-line tool > so I can easily debug reload files on disk.. > > and actually it doesn't matter that SerializeXML prints to the console, > because I could just do > > reload2xml somefile.reld > somefile.xml > > --- > James
Writing to standard output is the Unix way anyway! Speaking of xml, Mike mentioned a couple weeks ago that the Reload code grinds to a halt when processing some translated 64MB xml document. Since I enjoy optimisation to a rather evil degree, I'd like to look at it sometime. What are some good testcases? _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
