Perl5porters wants us to believe that they care a lots about backwards compatibility. This is, however, not true, as shown by how many of my obfuscations doesn't work anymore with recent perl versions, or they give warnings even when you don't enable warnings.

This node tries to be a comprehensive listing of which of my obfus still work and which don't. I'll try to update this node with newer breakage in the future.

This trend is also not specific to the obfu I write. The following section is of course just a selection, but you monks are encouraged to post tales about your broken code in replies: then maybe p5p will listen to us and stop these incompatible changes if they hear enough people complain. (Yes, I'm not completely serious, but this is the obfu section so I don't have to say that, right?))

Comment on Bitrotten obfuscations
Select or Download Code
Replies are listed 'Best First'.
Re: Bitrotten obfuscations
by eyepopslikeamosquito (Chancellor) on Oct 22, 2010 at 11:05 UTC

    Saturn still kaleidoscopes, The Earth still spins. All in the solar system is good and as it should be.

    Much to my surprise, Larry Witticisms from perl Errors still works -- from perl 5.005 all the way to perl 5.12. Given that this obfu creates random Larry witticisms based on the precise wording of perl error messages that is a huge and very pleasant surprise. I salute the Perl 5 Porters! Update: It finally broke with perl 5.14 (thanks to ambrus for pointing this out).

Re: Bitrotten obfuscations
by choroba (Canon) on Dec 18, 2014 at 13:17 UTC
    3-D Stereogram, Self replicating source. doesn't work in 5.14.4, still works in 5.10.1. Anyone interested can try to bisect the change more accurately.
    لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
Re: Bitrotten obfuscations
by awwaiid (Friar) on Jan 21, 2011 at 19:53 UTC
    My JAPH from a while back doesn't work in recent perls... but that's not surprising based on what it uses for it's source data :)