I tested with only changing the string constants on the patch from "@name" to "$(name)" and "@class" to "$(class)" and it seems to work fine till now, again as I pointed out it's a simple text replacement.
The other part I didn't submitted because I don't think it'll be accepted but for my own I also accept "@" as a separator on the widget name field like "d...@colors@depth" this string end up on generated source code as "dbf_color_depth" but I can retrieve it as a macro "$(dirty_name)" and I'm using like this: =o->user_data((void*)"$(dirty_name)"); To get: o->user_data((void*)"d...@colors@depth"); And with that I can split and extract several meanings from it. En 22/12/2010 00:58:58, Michael Sweet <[email protected]> escribió: > On Dec 21, 2010, at 6:14 PM, Matthias Melcher wrote: >> ... >> Same thought here. I'd lean more toward shell scripting syntax like >> "$(class)" because it is more familiar (to me, admittedly), and it >> allows adding text right after the variable name. Also, $$ would have >> to generate a single $. >> >> BTW, is the $ sign used anywhere in C++? Computer says "no" (grep \\$ >> src/*.cxx). Cough. So it would be a nice candidate. @ is not used in >> C++, but objective C. > > > +1 for using "$(class)", "$(name)", and "$$". > > ________________________________________ > Michael Sweet, Easy Software Products _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
