[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] include multiple utility modules vs one larger one?
Hello, We have coded a number of XSL functions (about 60) used by a series of XSL stylesheets (about 15). We've put all the functions into one large common XSL which is then imported into all the stylesheets. This has the effect of including much more into a given XSL than is generally used, but was done to (1) ease the problem of knowing which modules to import into which XSLs and (2) avoid posssible circular references which could result from nested imports. Functionally, our approach has seemed to work well so far. Is this considered a best practice or have we implemented an anti-best practice? Aside from an increase in compile time, is there any significant penalty or downside to this approach? Thanks in advance.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|