Hi, I wanted to do some tests before rising my voice, here they are http://cgit.asynk.ch/eo_tokenizer/
this is POC, http://www.complang.org/ragel/ based tokenizer which does not all but most of the job. First time I play with ragel, had much fun!! about the .eo file syntax: YAML is easier than JSON to write and read, but imho both are more machine than human oriented. I think we should to stick to C syntax it should ease everybody's pain and hopefully avoid wrong formatting, editor annoyance... http://cgit.asynk.ch/eo_tokenizer/tree/data/03_properties.c the above eo file example is fully understand by the tokenizer. the latest is realy easy to extand and modify. On Sunday 17 November 2013 15:53, Yakov Goldberg wrote : > Hi all :) > > I'd like to start new thread on discussion of Eo format. > --- Hell'O from Yverdoom Jérémy (jeyzu) ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
