some further comments...
- From: mr_unreliable <kindlyReplyToNewsgroup@xxxxxxxxxxx>
- Date: Mon, 28 Jan 2008 13:11:50 -0500
As for the difficulty in debugging "include files", yes it is.
But, generally speaking one ought to debug the include code
thoroughly (in the context of the main script), before
separating it out into a separate "include file".
As for the (lengthy) time required to retrieve the include
file from a server to satisfy the "wsf" file, one might also
assert that it would take about the same time to retrieve
that same code if used as previously recommended (readall,
eval).
Lastly, as a win98 user, I might also observe that your users
may already be in a "testy mood" at startup, having waited for
a relatively lengthy period for their systems (xp or vista)
to load. It is frankly surprising to me to see a much more
modern software system, on a hardware system that is running
more than 10x faster than my system -- take so much longer
to load...
cheers, jw
.
- Follow-Ups:
- Re: some further comments...
- From: mayayana
- Re: some further comments...
- From: Al Dunbar
- Re: some further comments...
- References:
- Include a vbs file into another vbs file
- From: Jake
- Re: Include a vbs file into another vbs file
- From: mr_unreliable
- Re: Include a vbs file into another vbs file
- From: Al Dunbar
- Include a vbs file into another vbs file
- Prev by Date: Re: Shortcut Parameters
- Next by Date: Re: usb write blocker
- Previous by thread: Re: Include a vbs file into another vbs file
- Next by thread: Re: some further comments...
- Index(es):