[Developers] Double quotes around keyword parameter values

[Erik Schnetter]

On Friday 27 May 2005 19:40, Jian Tao wrote:
> On Friday 27 May 2005 12:00 pm, developers-request at cactuscode.org 
wrote:
> > Jonathan suggests that I point out that keyword values that contain
> > spaces still require to be enclosed in double quotes.  This is not
> > what I changed.  I changed the following:
> >
> > The CST stage contained an explicit check that the default keyword
> > value is enclosed in double quotes.  There is no corresponding
> > check at the other places where keyword values appear.  I removed
> > this explicit check only.  That is, I changed the code that checks
> > default values, not the code that parses keyword values.
>
> I think it might be better to check the double quotes explicitly. For
> 2 reasons:
>
> 1. There is an explicit check already(the one you want to remove).
> 2. double quotes are required anyway in some special cases.
>
> Requiring and checking double quotes explicitly will probably make it
> less confusing for users. The rule will just be "adding double quotes
> to strings".

This is about keywords, not strings.  I would rather go the other way, 
namely specifying that keywords must consist of first an alphabetic, 
and then alphanumeric characters.  This way, keywords are like 
identifiers in computer languages.

-erik

-- 
Erik Schnetter <schnetter at aei.mpg.de>   http://www.aei.mpg.de/~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.cactuscode.org/pipermail/developers/attachments/20050527/f6c48f67/attachment-0002.bin