Re: Run the Same Macro on Multiple Files
- From: "Jezebel" <warcrimes@xxxxxxxxxxxxxx>
- Date: Fri, 4 Aug 2006 09:14:31 +1000
I think 'requiring' prefixes would be overkill. VB/VBA determines data type
from the declaration, which is all it needs for compilation.
"James Reid" <a8736d53@xxxxxxxxxxx> wrote in message
news:1154643680.126793.280890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"Invidious?" Don't you mean "insidious?" :-)
IMHO, programming languages should require prefixes, not only for
clarity, but also so as to speed up the compilation / interpretation
process. Perl & PHP do it to some extent. In JavaScript a "$" prefix is
allowed for variable names, but is seldom used.
Maybe I'll follow your example, Jezebel, and try to come up with my own
prefix standards.
Jezebel wrote:
The p prefix is my own variable naming convention: p = procedure-level, m
=
module-level, g = global. There are other convetions that also work well
(eg
using the prefix to indicate data type). It seems to me that scoping
errors
are the more serious issue (I've never had problems debugging type
errors,
but scoping problems can be invidious); but the important thing is to
choose
a convention you like, and stick to it. It will save you a *lot* of time
long-term.
.
- Follow-Ups:
- Re: Run the Same Macro on Multiple Files
- From: James Reid
- Re: Run the Same Macro on Multiple Files
- References:
- Run the Same Macro on Multiple Files
- From: James Reid
- Re: Run the Same Macro on Multiple Files
- From: Jezebel
- Re: Run the Same Macro on Multiple Files
- From: James Reid
- Re: Run the Same Macro on Multiple Files
- From: Jezebel
- Re: Run the Same Macro on Multiple Files
- From: James Reid
- Run the Same Macro on Multiple Files
- Prev by Date: Re: Adding complex cross-reference
- Next by Date: Re: FileSearch
- Previous by thread: Re: Run the Same Macro on Multiple Files
- Next by thread: Re: Run the Same Macro on Multiple Files
- Index(es):
Relevant Pages
|
Loading