> Isn't this almost a case for revamping the prototyping system? You can
> define your API in terms the current perl variables (nothing in the above
> suggests that integers versus floats is the main problem) and have a
> prototype system that actually allows you to specify that "argument 3
> sho
> No, I disagree. Perl gains a lot of its expressive power from being lax
> about typing. I suspect it will also impose an unacceptable overhed for
> the vast majority who don't want it - at the very least every variable
> access will have to check an 'are you typed' flag.
I agree that weak typ
The "definition" I've been hearing alot recently is that Perl is a "quick
and dirty scripting language." Fine, I think it does quite well at that.
But as of perl5, it is not a language which makes large development easy.
I think Perl needs a couple different faces. It should keep the
quick-n-d
