There are numerous features of XSL that are not used in many applications. Has anyone ever proposed a minimum subset of XSL that could be a lightweight substitute for full-blown XSL implementations? The reason I am asking is because I am trying to see if I can use XSL in an embedded environment.
Sablotron is already pretty small, but I have been asked to see if it is possible to get the code even smaller. Preferably about half of its current size. So I am asking if this seems like a reasonable goal. There are numerous functions and xsl tags in the spec that we are not using for our stylesheets. Would it be possible to cut down the size very much by removing functionality? I know there have many speed optimizations made in Sablotron, but has anyone explicitly tried to optimize for code size also? Where does most of the code size come from? I know that templates can result in code bloat but there are good type-safe work around for this problem (from Scott Meyer's _Effective_C++_ Item 42).
Sablotron is a great product, and I would like to use it in my architecture if possible, however, the prospect of cutting the code size down seems daunting. How likely do these goals seem?
Thanks,
Dan
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
