4 ms·
It's a shame that CDuce is dead, because it's an interesting take on the "XML transformation language" space: http://www.cduce.org http://www.cduce.org I used
by rwmj 10y ago
It's a shame that CDuce is dead, because it's an interesting take on the "XML transformation language" space: http://www.cduce.org http://www.cduce.org
I used CDuce for a significant SOAP project (http://ocsoap.forge.ocamlcore.org/ http://ocsoap.forge.ocamlcore.org/) after a previous negative experience with XSLT. It (CDuce) was a mixed blessing. It was very easy to parse and transform XML, but lacked major features like being able to print debugging information. Also because CDuce couldn't process XML schemas you ended up having to rewrite the schema in CDuce language in your own code. Code example: http://git.ocamlcore.org/cgi-bin/gitweb.cgi?p=ocsoap/ocsoap.git;a=blob;f=src/wsdl.cd;h=280aeefed56034f934ad8a4c5b37ce1629068826;hb=HEAD http://git.ocamlcore.org/cgi-bin/gitweb.cgi?p=ocsoap/ocsoap....
- masklinn 10y agoI always figured you could get the vast majority of XSLT's benefits without its (numerous) drawbacks by implementing the core match/transform idea in an actual general-purpose expression-oriented language like Haskell or Clojure or Ruby or whatever.
- rwmj 10y agoExactly. CDuce was a noble (but IMHO failed) attempt to add an XML-like DSL with functional-language overtones. For example you could write: transform bib with <_ (a)> [(x::(Author|Title|Url)|_)*] -> [ <book ({isbn="fake"}+a\year)> x ] where the <...> syntax looks similar to XML. (This example copied from http://www.cduce.org/tutorial_patterns.html http://www.cduce.org/tutorial_patterns.html )