Your comments remind of Avoid fancy words, an idea expressed in Strunk and White's Elements of Style. I wouldn't be the first programmer to suggest this book helps us think about how we program, even though it discussed writing in a natural language - English - as opposed to a programming language.
Why use clever terminology when plain words suffice? For Perl, our stands out as a neologism. In time it will become an established part of the language. But it isn't there yet, at least not for all Perl users. It's a matter of judgement, or ear as Strunk and White put it:
Only the writer whose ear is reliable is in a position to use bad grammar deliberately; only he is able to sustain his work at the level of good taste.
Whether we use our, or other neologisms in Perl, is a matter of taste and timing. At present, both are contentious: our has existed in Perl long enough for common use, but too short for universal acceptance. I avoid it in public code for the reasons you mention, but those reasons become weaker as time passes.
-
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.
|