Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: include file problem: namespaces?

From: Joe Kesselman <keshlam-nospam@-------.--->
To: NULL
Date: 5/6/2006 4:07:00 PM

Interesting project!

My reflex is to suggest that you consider restructuring this as a 
rules-driven process, using XSLT (which is, after all, a rules-based 
nonprocedural language, and can do more intelligent processing than the 
simple C preprocessor you've been playing with).

(There's definitely something to be said for writing your "library 
functions" in a higher-level language that's explicitly designed for 
manipulating XML rather than trying to do it at a lower level. And 
applying inflection does sound very much like a styling problem, even if 
it's in the temporal rather than spatial rendering domain.)

Caveat: Depending on exactly how your data is structured and what kinds 
of rules you're tyring to apply, XSLT may or may not be a reasonable 
approach. I freely admit that I'm biased because I've been working on 
XSLT processors for the past five years, and I do recognize that this 
general-purpose tool isn't a good fit for all tasks. But this sounds 
like a case where it might be entirely appropriate.

-- 
() ASCII Ribbon Campaign  | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry


-- 
() ASCII Ribbon Campaign  | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent