> When I tried running puppetd --debug --verbose --trace after making > changes for const_defined? without changing File, I ran into some > stack traces regarding no method error for File which made me suspect > that somehow Ruby 1.9.x changed some of the behavior for searching for > constants in moduled namespaces. When I add the double colons to > explicitly tell File to use the top-level File object instead of > possibly being confused with Puppet::Type::File these warnings went > away. > > Frankly, I would rather not change it but I am not sure if this is > something with the way the code is implemented that does not work with > Ruby 1.9.x or this should be brought up with the Ruby core team. If > there is a better way to handle this, I would be willing to try it. >
So if I'm not mistaken the "--debug --verbose --trace" aspect is incidental? 1.9.x does change how constants are found but I suspect that a less ad hoc solution is needed. Note that I don't have one to offer at the moment, just a feeling that forcing specific class references to be absolute is asking for maintenance problems. I'll add it to my list of things to look into, and would be glad to hear of anything else you turn up along these lines (thanks, by the way, for kicking this off). -- Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
