|
Ideas which have been discussed, and which may or may not happen.
It's unclear what this should do or how to do it without breaking old code.
There is a patch for this, but it may require Unicodification.
($x = "elephant") =~ /e(ph)/;
$1 = "g"; # $x = "elegant"
|
|
What happens if there are multiple (nested?) brackets? What if the string changes between
the match and the assignment?
Some core modules have been accused of being overly-OO. Adding procedural interfaces could
demystify them.
With gdb, you can attach the debugger to a running program if you pass the
process ID. It would be good to do this with the Perl debugger on a running Perl program,
although I'm not sure how it would be done.
A non-core module that would use "native" GUI to create graphical applications.
Currently
foreach (reverse @_) { ... }
|
|
puts @_ on the stack, reverses it putting the reversed version on the stack,
then iterates forwards. Instead, it could be special-cased to put @_ on the stack
then iterate backwards.
|
