[Developers] Table keys in thorn Boundary

Erik Schnetter schnetter at uni-tuebingen.de
Tue Jan 20 10:27:11 CST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 20 January 2004 16:46, Tom Goodale wrote:
> On Tue, 20 Jan 2004, Erik Schnetter wrote:
> > --[PinePGP]--------------------------------------------------[begin
> >]-- Thorn boundary uses table keys that contain spaces, e.g. "DECAY
> > POWER". Such keys are impossible to set from a string.  I suggest
> > to change the space characters to underscores, and to add a remark
> > to the table routine documentation that keys containing spaces or
> > equals signs are deprecated, and to add a remark to the
> > maintainers' guide that table keys must be legal identifiers in
> > Fortran.
>
> Why should it matter if they are legal identifiers in Fortran.

It does not, of course.  But people have become used to identifiers 
being letter-followed-by-letters-or-digits, hence that is a good 
practice to use.  Keys are also case insignificant for the Boundary 
thorn.  (I think.)

> Surely a better solution would be to fix the string parser so that it
> can cope with keys with spaces in them.

The parser can.  The grammar does not.  Spaces separate table entries in 
option strings, hence allowing spaces in keys leads to confusion.  If 
someone comes up with a good grammar, it would still be confusing to 
users.

- -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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFADVbfm3uiSwno3f0RAnlFAJ0cVP8hSi+/loBYgYSbkXocRtxHoACeLaJV
nDVtcKX5KVBnPZN6MwM9nCU=
=kmGx
-----END PGP SIGNATURE-----




More information about the Developers mailing list