> Other than this one warning, I think ruby -w is useful, and I would > prefer that our code not throw warnings. >
As a side issue, do we want to deal with all the warnings the code presently throws if you run it -w (I'm not advocating this, just raising the question). Spot checking, it looks like some of them have been there for several years. I guess my point is, I *don't* think ruby -w is useful, or at least it's warnigs should be taken with a big grain of salt. It warns on too many things (default variable initialization, redefining methods, etc.) that seemed like they should generate warnings to the C-programmers who wrote ruby but are now, going on fifteen years later, seen as good sound idiomatic ruby. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
