What's there in JALPack is the same as the jallib distribution of Kyle's doc.
Sunish On Thu, Sep 3, 2009 at 11:52 AM, vasile surducan <[email protected]>wrote: > > > On 9/2/09, Sebastien Lelong <[email protected]> wrote: >> >> Hi William, >> >> With "alias", you can create synonyms for everything: variables, >> constants, procedures, functions. >> > > > Damn me if I knew. Thank's Seb. BTW is that described somewhere in one > manual? > As far I read there is nothing either in Sunish jalpack, nor in Kyle > JalV24l distribution. > > However does it hurt to keep a while "var is" and alias in the same time ? > Do you know if Kyle is reading this list? > > thx, > Vasile > > > > Powerful. With "var <type>...is" (don't forget the type, alias don't have >> it, it's important), you can just make synonyms for variables. Two questions >> raise: >> >> 1. with "var <type> ... is", since it's a synonym for an existing >> variables, declared as a type, why repeating the type ? (I guess this is why >> Kyle wasn't that happy with this syntax) >> 2. since "alias" can alias everything, including variables, why keeping >> the "var <type>...is" way ? Having tow ways to do the exact same thing, >> while one being much powerful than the other and fully including features >> isn't a good thing. In that way, cleaner and easier are good reasons IMO. >> >> I guess these barriers are easy to break since there are artificial. A >> simple regex could be your hammer :) >> >> >> Cheers, >> Seb >> >> >> >> >>> 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 -~----------~----~----~----~------~----~------~--~---
