OK, with that amusing gotcha out of the way, I think that this is incredibly nice to have. Until it was forcibly pointed out to me what you would want to use it for I didn't see the point, but now I do and I will use it. :-)
On a side-note, I complained to merlyn that I remembered the days when I never saw bugs in Perl. Then I found out about some, but never worried about it much. Then I started hitting them myself. He tells me that he has never been bitten by a Perl bug. He knows about them, but has never been hit.
I suspect our definitions may differ though... Here is my guess as to merlyn's definitions. Any bug in a development version does not really count. Any version that breaks stuff merlyn really cares about clearly is a development version. And the stuff that merlyn cares about is a pretty good test suite for what merlyn actually does. Therefore essentially by definition, he will never be bitten by bugs in Perl.
VBG
UPDATE
I have just been told that this bug is fixed in bleeding
edge versions of Perl and will be fixed in 5.6.1. :-)
In reply to RE (8): How to tell eval where the code is from
by tilly
in thread How to tell eval where the code is from
by Yaakov
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |