Hi Seb, Well then, if it is so easy, and artificial, please provide such a function to the Python script that I use for re-indent and validation. I'd certainly have no objections then, would I? I used those functions on all of the code I've ported thus far. I only broke the re-indenter once, and I was able to work around it.
And while I thank you for the explanation here, is there additional documentation for Alias? Perhaps I should be using it in my CANopen library? Thank you, William On Sep 2, 1:55 am, Sebastien Lelong <[email protected]> wrote: > Hi William, > > With "alias", you can create synonyms for everything: variables, constants, > procedures, functions. 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 -~----------~----~----~----~------~----~------~--~---
