On Nov 29, 2007, at 7:32 AM, Stephen Deasey wrote:
>
> Are you saying that "false" is not false and "true" is not true?
I'm saying that false IS zero and 1 IS true (better, non-zero is true).
If false IS zero then testing the value for zero EQUALS testing the
value for false. Or not?
This was NOT so in the implementation, hence I had to correct that.
But this can bring us to the question:
set value [ns_config -bool jummy juice false]
if {$value == "true"} {
# ...
}
and all sorts of other weird things. I know I know...
This all ISN'T very clear because Tcl's C-heritage and
LACK of proper boolean type (actually lack of ANY types).
So, we cannot teach Tcl types, we can only make some
approximations. The (ns_config )code was simply too strict
at that place, which broke our scripts at various places.
The change isn't going to break anybody's scripts and is
"in the spirit" of the (Tcl) language.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
