Re: Question on download by LWP

David Squire <David.Squire@xxxxxxxxxxxxxxxxxxxx> wrote:

John Bokma wrote:

[..]

I can't agree with this. Using strict and warnings is
language-specific advice that helps folk solve and avoid problems. The
readability or not of "camelcase" is person-specific and has nothing
to do with Perl.

"... use underscores to separate words." Programming Perl 3rd ed, p605
(Programming with Style).

"... use underscores to separate words in longer identifiers."
perldoc perlstyle

IMO this has everything to do with Perl as for the same reason using camel
case in Java has everything to do with Java.


So, I have no problems with your saying "I don't like camelcase", but
"don't use camelcase with Perl" to me over-steps the mark.

I just passed on the advice given in Programming Perl ;-)

I, and no doubt others, participate in multiple Perl projects where we
don't always have control over naming conventions (how do you feel
about Hungarian?), and editing that down should surely not be a
requirement for posting here.

For the same reason not using use strict / warnings shouldn't be an issue
if that isn't causing any problem. Yet "we" insist on it being present.
Personally I think the posted problem should conform to at least to
perldoc perlstyle.

I agree with you to stick with the naming conventions of a given project.
And for that very reason, I think it's good to follow in Perl related
newsgroups the naming convention as outlined in perldoc perlstyle /
Programming Perl.

Getting a minimal script is a big enough
ask for most folk.

They need help, and ask "us" do answer their question(s). I think its fair
to ask of them to present their question in a format that's easy to read
for most people. To me that's following perlstyle as close as possible.

Finally, I am not saying to have no point at all: I agree that too much
nit picking can be overwhelming for the OP :-) But I also think I have a
point ;-)

--
John Experienced Perl programmer: http://castleamber.com/

Perl help, tutorials, and examples: http://johnbokma.com/perl/
.

Relevant Pages

  • Re: Problems passing a reference to a hash between functions
    ... M> But as noticed Paul Lalli, we're programming Perl;) ... M> While shorter code is more readable and powerful:) ...
    (comp.lang.perl.misc)
  • Re: reg exp
    ... yes as I read in programming perl as well lead me to this solution. ... and finally found this hint in perldoc perlop: ...
    (perl.beginners)
  • Re: Oreillys "Learning Perl 3rd Edition"
    ... Afterwards I plan on moving upward and onward in perl. ... Oreilly's "Programming Perl" or "Perl Cookbook" would be good to jump ... The old soul mate, which I ...
    (perl.beginners)
  • Re: Installing GDBM_File
    ... >> Programming Perl. ... And probably a pink cover? ... Uhmmm... ... Probably has a lot not in it, since it covers Perl 4. ...
    (comp.lang.perl.modules)
  • Re: They say I write Ruby like Perl
    ... Yeah, the term "camelCase" doesn't have anything to do with Perl, and I don't ... Java, used throughout the standard Java class library and by most Java ... is prevalent in Microsoft code (that is, code written by them and code written ...
    (comp.lang.ruby)