comment on

I can't recall a single good idea accompanied by working code turned away in the past five years I've read the mailing list.

I can. Migrating Win32API::(File|Net|Registry) into the core. Fixing pseudohash lookups so that things like

my $x=[{foo=>[]}];
$x->{foo}=1;
[download]

dont eat up all your ram (darned if i can find the mail that had the patch in it when i search tho). Fixing native Win32 command line handling so globbing is automatic as it would be on VMS and thereby simulating how it works on *nix. Fixing <> so it cant be used to rm -rf /. And thats just with a modest amount of searching, or asking in the CB. I'm sure if I looked hard Id find a bunch more.

I like the idea of votes. I think that certain personalities have historically had their (negative) opinions weighted far more heavily than they should be. A proper voting mechanism would counteract that. IE: "We have 300 people who said that it should work like X, just because PERLGURU thinks otherwise shouldn't outweigh them."

Renaming 'err' to 'dor'... Ummm.... :-)

---
$world=~s/war/peace/g

In reply to Re: The Perl 5 Conspiracy by demerphq
in thread The Perl 5 Conspiracy by chromatic

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks