NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
It's about program design, stupid! (Score:2)
At the higher levels, the how and why of things fitting together and how the data needs to be passed around, most people seem to just attach things with whatever pipe fittings they have close by, rather than using some consistent, overarching philosophy.
On the other side are overly-absract fr
Re: (Score:1)
That's why I prefer to talk about "maintainability" rather than "readability". It shifts the discussion away from syntax to other factors which actually matter.
Second order effects of language syntax (Score:2)
After a few months on the project, they had some interesting insights into the different world views of Perl and Python. A moderately experienced Perl programmer can skim over a random piece of Perl code and i
Re: (Score:1)
Great thoughts, as usual Ziggy.
Without being able to understand the program's design in the large or small, is being able to read the program even interesting? I can't think of a case where it is. Am I missing something?
Re: (Score:2)
I think you're approaching the problem from the wrong direction.
Given a new program and no previous understanding of how it works, you could read the program and build an understanding from there. Consider the first time you approached a full set of basic binary tree primitives, or a bubble sort. It may have been the first time you came across these concepts, but if you could r
Re: (Score:1)
That’s how I feel about Java. Regardless of how crappy the code, it always looks reasonable on a microscopic level.