Why do you care "What people say"?
Does that affect how much jobs pay?
Some like to code in triplicate: String newString = (new StringBuffer(aString)).append(anInt).toString();
Whilst others prefer to masticate: char *newString = strcat( aString, sprintf( malloc( 6 ), "%6d", anInt ) ); (**)
For some, every step is very hard won: (*)
Perlers just like to get the job done: my $newString = $aString . $anInt;
Fashions, as we all know, have a tendancy to come and go.
But functionally, we wear clothes to keep warm.
A dried meat dress, will never suppress
the utility of jeans. Even if they're torn.
So decide for yourself, what's important to you.
Being part of the crowd who cry "Perl's dead!" aloud.
Or one of the thousands that, every day,
get the job done using Perl. Their way.
(*)Hard won:
(**)Bugs intentional!
-
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.
|