> It's not so much that Perl shouldn't have data structures or modules. > I think what Stephen is saying (and he's not the only one) is that > the bare minimum amount of Perl you *must* know to be productive > is increasing. Either that, or we're giving the impression that > it's increasing. Many people don't want to get bogged down in how > the details of Unicode, upperclass level CS topics or Perl's unique > syntactical peculiarities to parse a damn log file (or find and > use a CPAN module that does it). For me, it's the bare minimum amount of Perl you must *use* to be productive that I see increasing in our plans and discussions. I'm afraid of Perl turning into a verbose monstrosity to please verbosity addicts of languages whose only point of advocacy is Perl FUD. Once quick and dirty dies, Perl dies. David T. Grove Blue Square Group [EMAIL PROTECTED] [EMAIL PROTECTED]
- Re: Perl, the new generation Bart Lateur
- Re: Perl, the new generation Dan Sugalski
- Re: Perl, the new generation Michael G Schwern
- Re: Perl, the new generation Stephen P. Potter
- perlsmall (was Re: Perl, the new generation) Michael G Schwern
- Re: Perl, the new generation Edward Peschko
- Re: Perl, the new generation Nathan Torkington
- Re: Perl, the new generation Mike Lacey
- Re: Perl, the new generation Adam Turoff
- Re: Perl, the new generation Dan Sugalski
- Re: Perl, the new generation David Grove
- Re: Perl, the new generation Stephen P. Potter
- RE: Perl, the new generation Peter Scott
- Re: Perl, the new generation Adam Turoff
- Re: Perl, the new generation Peter Scott
- Re: Perl, the new generation Dave Storrs
- RE: Perl, the new generation Dave Storrs
- RE: Perl, the new generation David Grove
- Re: Perl, the new generation Simon Cozens
- Re: Perl, the new generation Dave Storrs
- Re: Perl, the new generation Nathan Torkington