All scripts reference the same engine, each in their own context with
their own unique threads.
Aaron
On 11/22/2010 10:20 AM, Doug Lee wrote:
I was mostly thinking memory and context switching. I'm assuming that
each script either has its own complete engine instance, in which case
using two engines doesn't matter at all, or has a reference to an
engine, in which case it could impact memory usage and, less likely,
performance because of switching among engines to run parts of
different scripts. This is something about Windows ActiveScript that
I have never fully known.
On Mon, Nov 22, 2010 at 10:14:48AM -0500, Aaron Smith wrote:
The impact would be negligible. Performance would be measured more by
what the scripts are doing rather than what languages they're doing
in.
Aaron
On 11/22/2010 9:16 AM, Doug Lee wrote:
Any idea how much of a footprint, memory or performancewise, is
created by having scripts running in both VBScript and Javascript at
once in Window-Eyes? This is a very likely scenario given that WE
allows both (and of course others) to coexist. Example: If a user
runs AIM, whose WE scripts are in Javascript, and Winamp, whose WE
scripts are in VBScript, this will happen.
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
