-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm using the latest Windows snapshot, and I did a simple test to
check how things are about the decimal point vs decimal comma
notation. So numbers must be entered with decimal point, but the
outputs are with decimal commas; is this the final decision?
About difficulties on handling scripts saved by users using decimal
commas, should it be established that "session files should always be
saved with decimal points, and at the moment of loading the session
the numbers are filtered to reflect user preference.", this way the
interactive environment would use user preference for inputting numbers.
Or alternatively, for readability of the session file, it stays as it
was saved, only that on the first(s) line(s) should appear a special
gretl directive, like for instance:
# gretl::decimal=","
# gretl::list_separator=";" # this way a function call
would be: function_name( x ; y )
# gretl::thousands="."
or a single directive, like;
# gretl::notation=",;."
This way, by default, if no directives, no need for more processing.
And if directives match current user options, no need to filter the
numbers. So a user reading a session file would know how the numbers
are represented even if not using Gretl.
What you think about this?
My test output was obtained using Windows version, with the "use
locale decimal setting" checked (locale is Portuguese settings).
- -----
gretl console: type 'help' for a list of commands
? genr myvariable=1.2345678
Generated scalar myvariable (ID 5) = 1,23457
? print myvariable
myvariable = 1,23457
? genr myvariable=1,2345678
Syntax error in command line
?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Netscape -
http://enigmail.mozdev.org
iD8DBQFD2VGSHvesJJ5UqvkRAp5pAKDt4H6UnJJlS9TK0Adz0xQuVeqhkQCglsYZ
bAV5Rn92mee0pPa3K93jIgM=
=2htW
-----END PGP SIGNATURE-----