Instead of renaming variables in the main source, just run an obfuscater or do some fancy regex work over it and rename things to whatever suits your fancy.
I'd rather be able to "understand" the code I'm reading, rather than "decode" it. On 12/9/06, Peter Michaux <[EMAIL PROTECTED]> wrote: > > On 12/9/06, Martin Bialasinski <[EMAIL PROTECTED]> wrote: > > > > On 12/9/06, Peter Michaux <[EMAIL PROTECTED]> wrote: > > > > > I think el for element, hz for frequency, cb for callback, nv for new > > > value, and lv for last value are not extreme abbreviations. > > > > hz cb nv lv? > > "hz" should have been "p" since this is period not frequency. The > university should shoot me and take away my Physics degree. > > > Are you fucking kidding me? > > No I'm not kidding and I'm also not swearing on a public list. > > > We have the year 2006, not > > 1981 last time I checked! > > But we are still distributing the code every time it needs to be used > so short without being ridiculous is better. Ridiculous would have > been five variables named a, b, c, d, e. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
