New profiles spec

[Scott James Remnant]

On Sun, 2007-06-03 at 11:36 +0100, Alex Smith wrote:

> Hmm, I thought of a few things in terms of the behaviour when parsing 
> the profile:
> 
>   * What should the parser do if it encounters an enable/disable stanza 
> for a job that's already been specifically mentioned? Should it override 
> the previous definition for that job, or should it simply ignore the 
> second value and dump a warning to syslog?
> 
In the job definition, repeating a stanza is considered to be an error.

>   * Would it be better to store the values in an NihHash or an NihList? 
> Currently my implementation uses NihList, but I discovered NihHash when 
> poking around job.c. I don't really see any reason to change apart from 
> being able to look up profile entries by job name, and that can be done 
> with an NIH_LIST_FOREACH.
> 
A hash is more efficient if you're doing many lookups by name,

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20070603/5804d2f5/attachment.pgp