Well said, Vasile, Is there some (central) place where I can read about the pros and cons of 'alias' versus 'var .. is' ? I'm happy with 'var .. is', which has been around a long time. Why break something that has been working fine for years? 'Cleaner' and 'Easier' are not good reasons.
I have lots of 'old' JAL code that I am considering 'porting' to JALV2. Why put artificial barriers in my way? Does using Alias save a stack level, RAM, or have some truly measurable benefit? Just asking... William On Aug 31, 11:19 pm, [email protected] wrote: > Comment #7 on issue 86 by vsurducan: Use "alias" instead of "var ... > is"http://code.google.com/p/jallib/issues/detail?id=86 > > Keeping the compatibility with the old code is an important issue. I think > both > alias and var...is should coexist in the newer versions of compiler. > Meaning "var..is" should have the same functionality as "alias" in the > future > compiler versions as well even the new written code will use alias. > > Vasile > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences > at:http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
