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.
Misleading Subject (Score:1)
I'm not fond of seeing such misleading attributions. I'll try to give you the benefit of the doubt and assume that you actually think this is what he is saying, but I have a difficult time seeing how you (or anyone) can come to that conclusion.
If Paul had stated,
Would it make sense to summarize it as follows?
Re:Misleading Subject (Score:2)
Indeed it is poor logic, but it is what he uses to support that Perl is unreadable. I don't know why he connected those two. What do you think it means when he connects those two things?
Re:Misleading Subject (Score:1)
I don't think that's what he's saying at all (neither point, in fact). His point is that comments don't guarantee programs that are "written for people to read, and only incidentally for machines to execute."
I meant that your summary was poor logic. It's the classic logic problem. If A, then B. Does this mean if B, then A? How about if not B then not A?
In a footnote, he states, "The way to make programs easy to read is not to stuff them with comments." Regardless of whether you agree, clearly it is a logical fallacy to equate this statement with, "Comments make Perl unreadable." A logical conclusion would be, "Comments don't make programs readable." See the difference?
I also happen to think that Paul intends to be discussing programming as a craft, not programming languages.
Reply to This
Parent
Re:Misleading Subject (Score:2)
The two statements I pulled out do not connect with each other, but Paul specifically and on purpose connects them. He's using one to support the o