On 07/05/2011 05:51 AM, Ken Barber wrote:
Then you can also use these anonymous blocks/closures with defaults as well:
class c {
{
Service { hasstatus => true }
service { "a": }
}->
Yes, they should have their own scope, and pretty normal
puppet semantics/conventions. Maybe the only thing
that sets them apart from regular classes is that
you cannot include them anywhere. That, and I would
like to see an $ordered = true|false meta parameter.
I think they should be optionally named, though, so they can be
mentioned in relationships.
we could have both
block { "a": ... }
and just the anonymous
{ ... }
--
vagn
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
