Perl 5 RT

### From @rurban On Wed\, Apr 17\, 2013 at 1​:50 PM\, Michael G\. Schwern \ wrote​: > On 4/15/13 1​:31 PM\, Dave Mitchell via RT wrote​: >> The "uninit var"...

### From @rjbs On Wed Apr 17 11​:51​:24 2013\, schwern wrote​: > So I guess we're stuck with this behavior\. I propose three things\. Does this mean that you believe...

### From @schwern On 4/22/13 8​:09 PM\, Ricardo SIGNES via RT wrote​: > On Wed Apr 17 11​:51​:24 2013\, schwern wrote​: >> So I guess we're stuck with this behavior\....

### From @rjbs \* "Michael G\. Schwern" \ \[2013\-04\-23T11​:00​:07\] > I would like to see the warning and top level mistake fixed\. That is a > clear regression\. The rest...

### From @perhunter On 04/30/2013 11​:31 PM\, Ricardo Signes wrote​: > 2\) some further eyes investigating whether removing line 14 above is > actually okay; I'm not sure Ben Tilly...

### From @rjbs On Wed May 01 00​:00​:45 2013\, uri@​stemsystems\.com wrote​: > On 04/30/2013 11​:31 PM\, Ricardo Signes wrote​: > > 2\) some further eyes investigating whether removing line 14...

### From @rjbs \* Ricardo Signes \ \[2013\-04\-30T23​:31​:32\] > 1\) a test for the problem Schwern has reported\, suitable for adding to the > dist > 2\) some further eyes...

### From @rjbs I wrote a test\. I feel good about this change\, and I think it makes sense\, as much as anything in a pure\-perl carp implementation is going...

### From @schwern Thanks\, I did look at it but couldn't make heads or tails of the code\. Does this mean longmess will now produce the same stack trace as...

### From @rjbs \* "Michael G\. Schwern" \ \[2013\-05\-02T09​:25​:22\] > Does this mean longmess will now produce the same stack trace as > everything else? I \*specifically\* and \*only\* addressed...