2 ms·
Very nice. I wrote ARON (a righteous object notation) https://code.google.com/p/aron/ https://code.google.com/p/aron/ Whereas your Libucl comes from the conf
by specialist 13y ago
Very nice.
I wrote ARON (a righteous object notation)
https://code.google.com/p/aron/ https://code.google.com/p/aron/
Whereas your Libucl comes from the config management world, ARON is derived from my prior VRML work. Though ARON is a general purpose object graph serializer, I currently mostly use it for config, mostly as sane alternative to the DI and IoC nonsense in the Java world (Spring).
Both Libucl and ARON have a minimalist, typed grammar. Personally, I very much dislike goo like JSON. So you have my enthusiastic support.
I applaud the syntactic sugar you added, like units suffixes, eg 1k. I added UTC date time. I'm still pondering how to add URIs, both relative and absolute.
For reuse, ARON uses labels and references (my take on VRML's DEF/USE) vs Libucl's macros. Your strategy hadn't occurred to me.
Libucl's try/catch is VERY interesting. ARON's include is modeled after Java's imports, where declarations are at the top of the source file. Libucl's strategy is far more robust.
Okay. Enough stream of conscious replying.
Libucl is great.
Ignore the haters.