o:XML Syntax
Dave Jarvis <djarvis-be7S+VDl30wlJZD/[email protected]> Tue, 24 Aug 2004 14:04:48 -0700
| Newsgroups | gmane.text.xml.o-xml |
|---|---|
| Organization | Invoq Systems Inc. |
| Message-ID | <[email protected]> |
Hello, I have a few simple questions about o:XML, mostly from items I've noticed in other, related constructs (including JavaML and XSL). Before I get into my questions, I would like to say that I'm really impressed on how wonderfully SQL has been integrated into the language. I, myself, have done such language constructs in the past, but didn't hit anything that felt nearly as clean or well-designed. Kudos. 1. What was the driving force behind including the dot notation? Additionally, what would it take to move the interpreter from a dot notation to something completely uninfluenced by target language? Consider: <o:return select="$ling.translate( 'hello' )" /> Compared with the JavaML form: <o:return> <o:value-of target="ling" message="translate"> <o:param>hello</o:param> </o:value-of> </o:return> I realize the first way is succinct (and possibly faster to interpret), yet it seems more difficult to transform into non-C-based languages (e.g., Smalltalk). 2. What would be required to transform o:XML into languages such as Smalltalk, Python, or Ruby? 3. I noticed the license is GPL. Are there plans to move the licensing to LGPL? 4. With respect to logging and SQL calls, is there a 'global' area where a person can set the targets? For example, if I wanted to log to a specific file for 90% of the code, but to a console (e.g., System.out) for the other 10%, would it be difficult? The same for SQL, of course. Instead of having to supply the same SQL information for every call, is it possible to set it once (defaults) then have particular instances override the destination data store as required? Sincerely, Dave Jarvis -- Invoq Systems Inc. t. 250.380.0304 w. http://www.invoqsystems.com