On Tue, June 16, 2009 14:29, Luke Kanies wrote: > > On Jun 16, 2009, at 4:38 AM, Kjetil Torgrim Homme wrote: > >> >> Luke Kanies <l...@madstop.com> writes: >> >>> Of course, once you do this, you're in for a world of hurt -- ten >>> seconds after this gets merged, people will want node statements >>> with regexes. >> >> ok, I'll bite :) >> >> I don't care about node matching, but I really think case statements >> should support it, too. ideally also selectors, although that may >> pose a problem for the ephemeral values? > > Yeah, it seems like selectors should support regexes, too.
Yes, I'll extend the syntax to the selectors, that makes sense. I've almost finished node matching, even though I'm not really satisfied of how it works. Node matching is O(1) for the moment, but as soon as you add regexp in the mix, it becomes essentially O(n) :-( The other issue is that nothing is puppet is ready for non-string node names :-(, so there are lots of place where I need to change things... I'll see if I can refactor node names in a specific object to encapsulate the functionality and matching... but I don't really see how it couldn't be O(n). That might really be a penalty for people with a large number of nodes... -- Brice Figureau Days of Wonder --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
