[Developers] Double quotes around keyword parameter values

[Jian Tao]

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".

Jian
> This is independent of the fact that keyword values that contain
> embedded spaces cannot be correctly parsed when they are not surrounded
> by double quotes.
>
> -erik