Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

You certainly don't need to know C++ to be good at Perl.

Having a true object-oriented language in your background might help, but C++ is nowhere near object-oriented enough to make any significant difference in that regard (especially if you learned C first and then moved to C++, which will lead you to write mostly procedural C++ code); and a functional language (e.g., Lisp) would help a lot more, IMO; and in any case if your goal is to be good at Perl no other language will help you more than Perl itself.

Anything more than a cursory knowledge of C is actively detrimental (at first), because it leads to bad habits. This can be overcome, simply by working with Perl more, but there's no advantage to it (from a Perl perspective) until you reach the point (years down the road) where you're ready to start digging into the perl internals.

If your goal is to learn Perl, then you should study Perl. Write code in Perl that does useful things. Hang out on Perlmonks and read more than you post. Go back over your old code that you wrote in Perl a few months ago and notice which kinds of things that you did make it easy to understand and modify and which kinds of things make it difficult. Study Perl, use Perl, learn Perl.


In reply to Re: To be Good at PERL by jonadab
in thread To be Good at PERL by ostra

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (4)
As of 2024-04-24 07:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found