That’s a good point. Naming things in system configuration is always tricky, especially when common terms already carry assumptions.
Using something more descriptive than "port" definitely helps reduce ambiguity. Clear terminology makes configurations easier to understand and maintain, especially when others have to read or reuse them later. On Thursday, 31 March 2011 at 17:16:31 UTC+5 Trevor Vaughan wrote: > I don't like 'port', but I'm having a hard time coming up with a good > alternate. > > sys_service? > > The man page says "The Internet network services list" so perhaps > net_svc or net_service? > > Trevor > > On Wed, Mar 30, 2011 at 6:44 PM, Nigel Kersten <[email protected]> > wrote: > > On Tue, Mar 29, 2011 at 12:56 PM, Stefan Schulte > > <[email protected]> wrote: > > > >> Thank you for all your comments so far. > > > > Thank you for your code! :) > > > > I would like us to have a public think about whether "port" is an > > appropriate name for this though. > > > > > > -- > > Nigel Kersten > > Product, Puppet Labs > > @nigelkersten > > > > > -- > > 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. > > > > > > -- > > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > [email protected] > > -- This account not approved for unencrypted proprietary information -- > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/puppet-dev/af95b78c-e234-4689-b86b-68a43ddb9d84n%40googlegroups.com.
