On Wed, 25 Sep 2013, Sven Schreiber wrote:
I noticed that Gretl doesn't complain if I wrongly write:
set csv_read_na = "."
Instead (as 'set' shows) it just uses the "=" character and ignores
the
rest of the line, with fatal (but predictable) implications e.g. for
'join'. Maybe it should throw an error if it is getting an unquoted
string, or if it is getting something unexpected at the end.
Furthermore, if I write
set csv_read_na "."
(i.e. without the equal sign), it takes literally the three-character
thing \".\" (quote dot quote) instead of just the dot.
So quoted strings seem taboo here, which I find slightly worrying (and
took me a while to figure out the error).
We could try to patch this up (I'll have a go) but this sort of problem
should go away when we switch to the new command "tokenizer". That's
something I've discussed with Jack; it's a greatly more systematic way of
munching through commands which, among other things, will automatically
catch the case of extra "junk" tokens on the end of a command line.
I have a prototype for this which works nicely, but it'll be quite a
complex piece of surgery replacing the current command parser and it won't
happen before the next release.
Allin