R
True, you could incorporate the reference that way, but I don't think that
changes the way the compiled version of VB handles calls to the script
engine... I think it still temporarily "drops out" of the compiled code to
interface with the script engine... that action, and the interaction to pass
values back and forth, is what I think slows down the compiled program when
it uses scripts. VBA, not being compiled, does not appear to have this
problem; or, if it does, its impact is less noticeable than in compiled VB.
Of course, with a regular expression engine, the time saved by the regular
expression parsing may offset the script interaction slowness; but as a
rule, compiled VB'ers tend to stay away from scripts.
Rick
Programming is a hobby with me -- not a vocation.
I have a familiarity with BASIC (I was a student at Dartmouth
when it was being developed); Pascal, JCL, Assembly language
and now VBA.
This familiarity was provoked by various needs at the times.
You sound like you may be older than I am (I am on the young side of 60).
With me it was mostly BASIC and VB, but I have also worked with FORTRAN,
C/C++ and various Unix scripting languages.