On Thursday 28 November 2013 14:30, Tom Hacohen wrote : > On 28/11/13 11:57, Jérémy Zurcher wrote: > > On Thursday 28 November 2013 11:13, Tom Hacohen wrote : > >> On 28/11/13 11:08, Jérémy Zurcher wrote: > >>> 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... > >> > >> The problem with c syntax, is that we'll never be "there". That is, > >> we'll be stuck in the land of similar enough to call it C, but > >> incomplete enough to be annoying and confusing. > >> > >> Just like vim mode is on most editors. > > > > did you looked at my example file ? > > vim just like writting it and it does what we want. > > > >> > >> We need very specific things that the C syntax doesn't support (that's > >> why we need .eo files in the first place), so instead of hacking around > >> something that wasn't designed for it. Why not make something new that > >> is simple, easy to learn (i.e immediate transition from c) and designed > >> for the task? > > > > because it is useless, > > we just need to understand a few keywords inherits, properties, methods, > > params, set, get > > then tokenize a very minimal C like construct : definition { ... }; > > > > but you can call it new if you want ;) > > While the hacks to make editors work with the syntax look nice, they're > not perfect, and that's related to my previous point about vim: it works > nice for your example, maybe for a few other things, but then we'll hit > a wall, and that will be really annoying. > > The syntax does look fine though, except for the = mark after the > "return". Why not just "return Eina_Bool" ? > Also, if we are already ; delimited, why not: > legacy = evas_object_visible_get; ? you are right, both fixed now, took just a few seconds. > > Anyhow, while your suggestions will trick simple syntax highlighters, > it'll drive my vim+clang mad. Same goes for any other "advanced" > editors. Unless of course you don't set it to C, and then you lose the > advantages. I'm sure you can disable vim clang plugin (which I will test now) on .eo > > I'm actually kinda fine with this syntax (after the few improvements). > > -- > Tom. > > > > ------------------------------------------------------------------------------ > 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 --- 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
