Say... If (and that may be a big "if") we can make sure that all 'top-level' config macros have name as the first parameter...
Or, wait, even better!
Does this look at least vaguely sane? (cluster ("rtr-~3,'0d" 1 10) (machine name linux-host (user "testuser")))
I think that looks mostly sane. :)
One thing that bothers me a little is the use of the optional NAME parameter. It reminds me a little *too much* of Paul Graham's AIF macro (which I love, BTW, but unhiegenic macros can be a bit of a pain). As opposed to AIF, I do like that I can call the symbol whatever I want. :)
I can certainly get used to it, so don't count this as an objection. :)
Are there any packages out there for C-style format strings with Lisp? Personally, I'm very happy with the Lisp-style format strings, but I (unfortunately) have to agree with Ingvar that "end user" types will likely know more about C than Lisp. :P
Should we consider an alternate configuration syntax for Lusers? I guess if it were me, I'd make some macros that expand to the noctool-config macros. Something that might be more familular to someone who has configured Nagios or some such simular tool. IMO, this syntax should feel a lot like Perl (shudder!!!). This would probably add a boatload of maintenance, but might make the "entry fee" a little lower (learning a little Lisp + learning Noctool is harder than using a familular syntax while learning Noctool is basically my thought). It feels a tad preliminary to be thinking about this sort of thing - it is another thing that I've struggled with with LoGS (my potential users don't want to learn (*any*) Lisp!!!)
This way, we allow clustering of any top-level config form, we aren't restricted in the actual parameter (it defaults to substitute "name" but if you prefer, you can replace "blahonga" or "supercallifragilistic" with each generated name).
That sounds great!
Jim
James E. Prewett Jim@Prewett.org download@hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210