--- David Golden <[EMAIL PROTECTED]> wrote: > Maybe it's too late, but which versions of Sub::Uplevel and > Contextual::Return were you using?
Sub::Uplevel 0.12 (and old version. Forgot to check that). Contextual::Return was 0.2.1 both with and without the patch listed in http://rt.cpan.org/Public/Bug/Display.html?id=26101. > I attempted to fix Sub::Uplevel as of version 0.16 to play nicely > with > Contextual::Return -- but as you said, finding a minimal test case is > difficult. > > It's also a potential issue for Hook::LexWrap, so if I can find a > permanent fix, that would be a good thing. Reminds me of how djberg was complaining in his journal (http://djberg96.livejournal.com/) about Ruby developers who alter basic types in incompatible ways (can't find the post, though). Particularly as you get larger and larger code bases, finding code which globally changes behavior can cause mysterious problems. To date, we've been forced to remove the following bacause of bugs: UNIVERSAL::can Contextual::Return And we removed UNIVERSAL::isa because it caused a measurable slowdown in our test suite (about 2%). For smaller projects, you have fewer interactions. For large projects, globally altered behavior is playing russian roulette without counting the bullets. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
