[Developers] Double quotes around keyword parameter values

[Erik Schnetter]

On Friday 27 May 2005 16:41, Erik Schnetter wrote:
> There was an inconsistency in where double quotes around keyword
> values where required by the CST stage.  They were required only for
> the default value.  I changed this so that keyword value now do not
> need to be enclosed in double quotes any more; this makes it
> consistent.

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.

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

-- 
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/cdfdef5c/attachment-0002.bin