Ugly, and brings in a problem that does not matter: parse. The problem being solved is reduce repetitive code that C/eet forces you, instead of it we'll start doing parsers for different languages, then people brings in requests for multi line comments, etc
Okay, whe can do single line, dumbed down... Then we get complaints and need to doc, then people don't read and we're not much better than the simple we did. Also if we request a struct per file, or forbid nested structs, were much like now, but harder to parse. IOW right now parser comes tested and for free, not using it does not bring much, adds pain. On 7/12/10, Carsten Haitzler <ras...@rasterman.com> wrote: > On Mon, 12 Jul 2010 13:23:22 -0300 Leandro Pereira <lean...@profusion.mobi> > said: > >> Raster, >> >> On Sun, Jul 11, 2010 at 10:40 PM, Carsten Haitzler <ras...@rasterman.com> >> wrote: >> > >> > i agree. though my take on it is that i'd prefer it to be done as part >> > of >> > the c src like this: >> > >> >> This was not done because I'd like to use the same .geneet files for >> other languages: one input generates source for C, Python, >> whatever-else-someone-needs. This is pretty similar to, for example, >> Google's protobuf generators[1], and I like the approach of it being >> language-agnostic, even though I understand your point of easily >> keeping the structures in sync with the structures in the C source >> file. >> >> Adding non-encoded data is simple enough: a "noencode" keyword could >> be added to variables to opt them out of being encoded in the eet file >> (but still write the getters/setters/etc). In fact, this is already >> implemented :) >> >> [1] http://code.google.com/p/protobuf/ > > hmmm maybe a compromise. both python and c and c++ and nigh on every lang > supports commenting of some form. all you need is for geneet to know how to > strip out comments. right? > c/c++: > "/* eet:" <geneet string here> "*/" > c99/gcc/c++ "c+= style": > "// eet:" <geneet string here> "\n" > python: > "# eet:" <geneet string here> "\n" > lua: > "-- eet:" <geneet string here> "\n" > etc. > > etc. - you just need to take input file and throw out all content outside > the > above snippets. the resulting filtered content is the geneet core. you just > need that geneet format to be simple enough to stick in such comments > without > problems. > > much nicer and now extensible for nigh on any languages? > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Sent from my mobile device Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
