Re: problams with IO::Socket::INET
Tom Christiansen (tchrist@jhereg.perl.com)
Tue, 27 Jan 1998 22:58:50 -0700
>ERROR! I'm not even going to read anymore. If you continue to ignore good
>programming practices you're screwed. If you want i could compile a list of
>newbie errors and then present them as reasons for why the syntax in perl
>is wrong. Anybody who chooses to use ambiguous code is stupid.
>
> my $copy = new $type();
>
>Get it right.
That's not what the docs say. Get it right, yourself.
Nothing in perlobj tells you to use those parens, and a C++ programmer
isn't going to. I don't recall being forced to use parens in C++.
We can't stop people from doing it. The docs currently lead you down
a primrose path.
I developed the syntax for a lot of this, stuff, Mark. I've *very*
familiar with it. For example, I'm the one who first thought about
CLASS->meth as well as $obj->meth.
I made some mistakes. We all did. I'm sorry for that now. Don't
compound the error.
No I/O syntax. End of Story. It's just too dangerous.
--tom