Re^4: XSLT processing huge XMLs

Unfortunatelly couldnt install them on the win platform (no ppm available and the cpan refuce to complete the task). I suppose that these are the alternatives that i was looking for? Any ideas on how to improve Sablotron on those tasks? Thinking that the XML::Parser::Expat memory leak is common to other perlish approaches... so a general alternative might be usefull. Doesnt it? am i missing something?

Comment on Re^4: XSLT processing huge XMLs

Replies are listed 'Best First'.
Re^5: XSLT processing huge XMLs by demerphq (Chancellor) on Feb 07, 2005 at 15:11 UTC
Sounds like you are missing a C compiler. Get a copy of the latest free MS C compiler (involves installing tons of crap) or get your company to buy one. Either way the amount of money you save by being able to build open source on your MS box will quickly recoup the cost of the compiler. Er, the above is assuming that binary interoperability with MS is important, if it isnt then use cygwin perl and cygwin gcc. OTOH, a native compiler will probably result in a faster executables overall. (With some exceptions, AS'es Perl isnt optimal with respect to certain memory operations, especially realloc.) --- demerphq	[reply]
Re^6: XSLT processing huge XMLs by aquarium (Curate) on Feb 07, 2005 at 16:36 UTC
it's really outdated...without any fancy gui or c++ libraries, but i still have a copy of TurboC, which compiles C code into non-gui executables just fine. the TurboC editor/environment is so nice an simple....it's a shame that nowadays the IDEs are so bloated/complicated. the hardest line to type correctly is: stty erase ^H	[reply]
Re^7: XSLT processing huge XMLs by gellyfish (Monsignor) on Feb 07, 2005 at 16:53 UTC
I would be doubting whether Turbo C can compile Perl though - but would be pleasantly surprised to be proved wrong, you might even get away with using the Borland C instructions and substituting `tcc` for `bcc` in the Makefile. /J\	[reply] [d/l] [select]