From: John K. <jko...@on...> - 2005-12-14 16:43:31
|
Marcelo Matus wrote: > Hence, I think that accepting "0" as a integer value was an > error in 1.3.27, and now the behavior is at least consistent, > which is the idea behind the new Unified Typemap Library, > > - For each type, there is only one method for conversion and checking, > which is used in all the typemaps, overloading, etc. <snip> >> >> ie, "0" is implicitely coerced to 0, but in 1.3.28 it fails since the >> argument is recognized to be a non-integer type. Note that this is the >> same behavior now for perl, python, tcl and ruby. >> Just wanted to spark this thread again. That is indeed how it works in python and php as well. My only real objection is to this behavior in Perl that it's not very Perl-ish. Those other languages have stronger typing, and there's a way to convert a string to an integer. Does Perl have as clean a way (like int() in python or intval() in php) to force this conversion? I've been using (1*$x), but that's pretty ugly. John |