Re^2: Legacy code question

While I agree philosophically with you and haukex, I have seen quite a fair bit of code in the wild “written” by users like bigup401. Code that never made sense, was written without use strict, often worked by side-effect or accident or only on a narrow subset of possible input, and is full of no-ops left-over from writing code by cut-and-paste testing.

Comment on Re^2: Legacy code question Download Code

Replies are listed 'Best First'.
Re^3: Legacy code question by karlgoethebier (Abbot) on May 14, 2019 at 12:20 UTC
"...writing code by cut-and-paste testing." To be honest: This was the way i coded my Java stuff the last three years i was in office. A funny side-effect of this practice was my my best node ever on PM. Best regards, Karl «The Crux of the Biscuit is the Apostrophe» `perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'`Help	[reply] [d/l]
Re^4: Legacy code question by Your Mother (Archbishop) on May 14, 2019 at 13:50 UTC
Indeed. The more confusing or the worse the documentation for a library is, the more likely I am guilty of the same thing. I endeavor however to both clean it up, attempt to enable the most strict checking, and leave tests behind after I finally understand the situation.	[reply]