To me, consistency is key. If your application has to work alongside other code (e.g. in VB) that already uses this nomenclature, then follow suit. If you are working with a legacy application that didn’t use it, don’t introduce it. Figure out what the Romans were doing and keep doing it.
These notations can unintentionally be misleading when used with a “typeless” language, such as Perl is and such that VB often is. You can legitimately find that your szFoo variable contains an integer, or that the value it contains has magically transmogrified itself into one. Thus, the social-contract that has been implied by the naming can’t be upheld by the technology, which might produce confusion. Nevertheless, human beings will still benefit from consistency in naming, whatever that consistency is.
-
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
or How to display code and escape characters
are good places to start.
|
