This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Lars Arvestad <arve@nada.kth.se> writes: > GH> Umm... does anyone really want to have to debug their project entries? > GH> It basically isn't a language at all, but just a very simple way of > GH> submitting info for a database... a project is nothing more than a > GH> record with a bunch of keys. I'll be the first to shout the joys of > GH> the lisp-like language, but I don't think I'd want to write everything > GH> in scheme. > > I agree a config language is overkill, but thi has a point with his > wish for a more schememely format. As you say, a project is a record > with a bunch of keys, so why not simply ask for an alist? For example: > > ((name . "Guile project submission parser") > (author . "Greg Harvey") > (status . "Extensively tested.") > (code . "(read)")) > > Could it be more convenient? > Yeah, I think that could work (and save a few 5 keys in the process, though at the cost of 9 & 0). The only thing I wasn't fussy about with this is long fields, like ((status . "It would be in much better shape, but my dog ate it, then a car ran over it")) which wouldn't format all that well in a scheme mode; this is only really a nitpick, though, since it'd be quite easy to allow more than one string (and, as an added bonus, no messing around with obtuse formating conventions) ((name "Guile frobnicator") (authors "Some guy" (email-address "some.guy@someplace.org")) (status "The current version is at " (url "http://someplace.org" "Someplace") ".")) I dislike the separate period, but nothing's perfect. -- Greg