PXSL Feedback Please let us know what you think about PXSL. We are especially interested in constructive criticism: - What do you like about PXSL? - What do you ~~not~~ like about it? - Is there anything that you find awkward? - Is there a problem that you think PXSL ought to solve well, but it doesn't? - Have you found what you think is a bug? - Do you have a feature request? Share your thoughts. Don't be shy. 2003-07-12 01:10:48.36 2003-07-12 01:10:48.36 comment-PXSL Feedback-1 What is the Limit of PXSL? I have Problem with verry big Source. "fatal error: RTS exhausted max heap size (26845456 bytes)" The Source was 20MByte with 900.000 Line. I use WIN98 with 196 MByte RAM. Thanks for Answer. 2005-06-14 06:23:12.178 2005-06-13 15:49:04.716 comment-PXSL Feedback-2 PXSL is limited only by the amount of memory you have. That said, the ~~pxslcc~~ tool probably is not the most memory-efficient implementation and may consume a lot of memory to process large source files. In your case, it looks like ~~pxslcc~~ is able to consume about 26 MB before running out of memory. That suggests that Win98 isn't giving enough memory to ~~pxslcc~~. Can you free up some memory by not running so many programs in the background? Does running fewer programs change the point where ~~pxslcc~~ exhausts the heap? Cheers,\\ Tom 2005-06-14 19:09:28.18 2005-06-14 19:09:28.105 comment-PXSL Feedback-3 Thanks, I think, I write an sed-Script for this big pxsl´s ;-) I have testet this Way. This Way is possible, without Makro. Jens Grabner 2005-06-18 02:59:43.042 2005-06-18 02:59:42.972 comment-PXSL Feedback-4 Tom, PXSL is great. It makes xslt way more enjoyable to code in and read. Thanks! I have a couple of features I'd like to request: 1) I'd like to be able to include a file with macro definitions in it. I have macro definitions that I use across sets of files and I'd like to be able to maintain these macros in one file or a set of files. 2) I'd like to be able to convert xsl to pxsl while making use of element definitions. For example, when converting: * <xsl:value-of select="/"/> to pxsl, I'd like to have * value-of / be the output produced rather than * xsl:value-of -select=/ through use of the * value-of = xsl:value-of select element definition. Any thoughts? Thanks, Ryan Hanks 2005-12-26 04:10:03.218 2005-12-26 01:40:01.755 comment-PXSL Feedback-5 Ryan, thanks for your kind words about PXSL. Regarding file including, that's something that's been on my to-do list for a while. In the meantime, you can load your common code by listing it first on the command line: {code:none} $ pxslcc common.pxsl myfile.pxsl > output.xml {code} Your second request, however, I probably will not implement because it is a lot of work and provides benefit only in a small number of cases (i.e., when not writing PXSL by hand). In the general case, you're asking for "PXSL minimization" &#8211; a compilation phase that replaces verbose PXSL with condensed PXSL by taking advantage of available element defaults. Since PXSL is designed to be hand written, there is no built-in support for XML-to-PXSL translation. That support is provided by an add-on XSLT stylesheet, which doesn't do much thinking, and doesn't have access to the active element defaults. So, the general minimization you're asking for is not likely to be added. If you just want a smarter, more-idiomatic translator for XSLT stylesheets, however, that you can probably implement by modifying the existing stylesheet to handle XSLT special cases for which there are element defaults. If you wanted to do this, I would be happy to add your smarter stylesheet, with credit, to the XSLT distribution. Cheers,\\ Tom 2005-12-27 13:20:11.923 2005-12-27 13:10:36.066