Here is an email I received in response to my essay on how to write unmaintainable code. My responses are marked with a ∇ and green type.
You are quite right. The essay started as therapy. I would get so angry when I encountered poor code. The essay was an opportunity to ridicule it and lampoon it. I discovered that readership for my essays on how to write unmaintainable code had orders of magnitude better readership than my essays on how to write good code. Now when I encounter terrible code, I clap my hands in glee — another item for my collection.
I am sending you two suggestions into Unmaintainable code howto. I think both of them are beautiful way for writing messier code.
function foo(bar) {
var baz = function() {
return bar;
}
return baz;
}
var x = foo(2);
y = x(); // y is 2;
By mixing closures which have side-effects and reusing variables from global scope, one can create beautiful parts of
code, even more beuautiful than the obfocusator would.
I have never seen code like that before, outside of FORTH. Are you sure that would compile? I am so used to Java where all the case clauses must be evaluated at compile time without duplicates.
I would appreciate, if you find at least some pieces of this code helpful for extending your Unmaintainable code howto.
|
|
available on the web at: |
http://mindprod.com/feedback/unmain/closure.html |
optional Replicator mirror
|
J:\mindprod\feedback\unmain\closure.html | |
![]() |
Please email your
feedback for publication,
letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear
wording, broken/redirected link reports, suggestions to improve this page or comments to
Roedy Green :
| |
| Blog | Canadian
Mind
Products
IP:[65.110.21.43] Your face IP:[50.19.155.235] |
|
| Feedback | You are visitor number 11. | |