JScript and VBscript

[Roland Hall]

You know what Dave, you exhaust me. I just deleted all my responses because
it's a dead horse and you obviously have an agenda. So, Happy New Year.

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.

-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-MSDN Library-
http://msdn.microsoft.com/library/default.asp

 

[Michael D. Kersey]

Curiously enough, this can be "circumvented". A function (or Function or
Sub) can be called from any block regardless of which one defines it -- and
regardless of the "execution order".

[posted after Roland became "exhausted"]

The above is a good methodology to follow to prevent confusion. However...

If one were given working code already in production and written by
developer(s) who freely mixed code in different languages without doing
what you describe above, then it would be _necessary_ to be aware of the
subtleties of execution order. Were one to encounter such code a good
first step would be to refresh one's memory on execution order and then
_possibly_ set about refactoring the code in the manner you describe
above. I say "possibly" because there's _always_ a cost and some danger
in modifying working code!

[Meta-observation about this thread:]
This was a very interesting thread for me because I hadn't revisited the
topic in some time and also because of the delightful fact that _all_
parties were presenting correct information and and useful examples but
nonetheless were arguing. For that reason I'm glad that they persisted
even though they seemed somewhat puzzled by each other's posts.

I think Dave's post (above) marks a point whereafter the thread becomes
inadvertently contentious. As the topic unfolds, Roland, Dave and Mark
present useful and interesting information and examples. Had all three
been in the same room discussing the question, any differences would
have been quickly resolved, assumptions more clearly laid out and
misunderstanding more easily avoided. But those of us not in that same
room would never have heard the discussion and would have remained less
enlightened. So thank you!
[End Meta-observation]

Good Luck and Happy New Year to all,
Michael D. Kersey

Programmer's Threat(accompanied by musical theme from "The Good, The
Bad, and the Ugly"): "Touch that code and you own it!"

 

[Dave Anderson]

If one were given working code already in production and
written by developer(s) who freely mixed code in different
languages without doing what you describe above, then it
would be _necessary_ to be aware of the subtleties of
execution order.

If you are suggesting that it would be necessary to be aware of those
subtleties beforehand, I'm not sure I agree, but you do underscore my point
that we should understand the technology we use.

Were I in such a situation, my A PRIORI analysis would almost certainly
alert me to the fact that such subtleties exist, and I would either search
for documentation or test my assumptions to reach clarity on the issue.

In any case, I agree that such awareness necessarily must precede the work.


--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

 

[Dave Anderson]

...whichever your perspective, Dave is wrong!

My New Year's resolution is to stop being wrong, no matter what your
perspective.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

 

[Roland Hall]

:
: Dave Anderson wrote:
: > "Roland Hall" wrote:
: >
: >>Be aware of the execution order...
: >
: > Curiously enough, this can be "circumvented". A function (or Function or
: > Sub) can be called from any block regardless of which one defines it --
and
: > regardless of the "execution order".
:
: [posted after Roland became "exhausted"]
:
: The above is a good methodology to follow to prevent confusion. However...
:
: If one were given working code already in production and written by
: developer(s) who freely mixed code in different languages without doing
: what you describe above, then it would be _necessary_ to be aware of the
: subtleties of execution order. Were one to encounter such code a good
: first step would be to refresh one's memory on execution order and then
: _possibly_ set about refactoring the code in the manner you describe
: above. I say "possibly" because there's _always_ a cost and some danger
: in modifying working code!
:
: [Meta-observation about this thread:]
: This was a very interesting thread for me because I hadn't revisited the
: topic in some time and also because of the delightful fact that _all_
: parties were presenting correct information and and useful examples but
: nonetheless were arguing. For that reason I'm glad that they persisted
: even though they seemed somewhat puzzled by each other's posts.
:
: I think Dave's post (above) marks a point whereafter the thread becomes
: inadvertently contentious. As the topic unfolds, Roland, Dave and Mark
: present useful and interesting information and examples. Had all three
: been in the same room discussing the question, any differences would
: have been quickly resolved, assumptions more clearly laid out and
: misunderstanding more easily avoided. But those of us not in that same
: room would never have heard the discussion and would have remained less
: enlightened. So thank you!
: [End Meta-observation]
:
: Good Luck and Happy New Year to all,
: Michael D. Kersey
:
: Programmer's Threat(accompanied by musical theme from "The Good, The
: Bad, and the Ugly"): "Touch that code and you own it!"

Hi Michael...

Good observation. I think we actually agreed more than we disagreed. Dave
thinks it is good to 'know the code you are developing in' and I think
informing someone of how something works is part of that. That sounds the
same to me but what do I know?

Had we been in the same room, perhaps it would have been more academic and
more evident or perhaps more adjectives would have been used?! So,
whichever your perspective, Dave is wrong! *roar* ...runs out laughing...
Happy New Year!

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.

-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-MSDN Library-
http://msdn.microsoft.com/library/default.asp