On Wed, 2007-04-25 at 21:57 -0700, Erick Tryzelaar wrote: > skaller wrote: > > It opens up the issue of what > > to do with string literals. In Python it is very painful, > > because the literals don't support nice block indent style. > > > > In this case .. attempts to make the code look nice > > turn out to cause a bug. AFAICR trailing whitespace > > is elided (because you can't see it). Thus > > > > """hello > > """ > > > > will be 'hello\n' even if you put extra ' ' after hello. > > If you put > > > > """hello \ > > """ > > > > it adds the white space .. but removes the \n ... ;( > > > > Not very consistent.. > > There's been a library, textwrap, since python 2.3 to work around this: []
Sure, we can easily incorporate ANY semantics. IN fact one possible project for 1.1.4 is Perl like regexp handling using TRE. Indeed we could incorporate Tcl directly in Felix, or Lua, or even Perl/Python .. :) The question is: what do we want with strings and mini-languages encoded in strings? And what is a consistent way to cover the different options/combinations .. this includes 8 bit strings vs 32 bit strings vs byte strings vs UTF-8. What we have now is basically an accumulation of hacks .. there isn't even a lexexp for character constants. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
