Front page | perl.perl5.porters |
Postings from May 2012
Spent the week intermittently continuing to work on the code-calling
aspect of /(?{})/. I've managed to get it working with (an enhanced)
MULTICALL with all tests passing; although it needs more tests and work.
In particular, things like /(?{die/next/last/caller})/ no longer SEGV.
I took the Executive Decision that the only sane semantics for regex code
blocks were to treat them similarly to sort blocks, tie methods, %SIG
handlers etc, where a new stack is pushed, 'next', 'goto' etc can't
see anything external to that block, and 'return' returns from the code
block, not any enclosing sub.
Report for period 2012/04/30 to 2012/05/06 inclusive
SUMMARY
-------
Effort (HH::MM):
0:00 diagnosing bugs
9:55 fixing bugs
0:00 reviewing other people's bug fixes
0:00 reviewing ticket histories
0:00 review the ticket queue (triage)
-----
9:55 TOTAL
Numbers of tickets closed:
0 tickets closed that have been worked on
0 tickets closed related to bugs that have been fixed
0 tickets closed that were reviewed but not worked on (triage)
-----
0 TOTAL
DETAIL
------
[perl #34161] METABUG - (?{...}) and (??{...}) regexp issues
2012/05/02 0:30 fix
2012/05/04 1:35 fix
2012/05/05 2:30 fix
2012/05/06 5:20 fix
--
More than any other time in history, mankind faces a crossroads. One path
leads to despair and utter hopelessness. The other, to total extinction.
Let us pray we have the wisdom to choose correctly.
-- Woody Allen
Thread Next