DO11: ActiveState languages not working

Windows XP SP3 32-bit.

I've tried two ActiveState languages (python/perl), and I get "Script Engine '<python|perl>' could not be opened" for both of them.

I worried about this when I read "any Active Scripting-compatible script language (VBScript, JScript, etc)", which seems to downplay by way of omission python/perl. I'm hoping they have not been demoted.

I'd like to +1 these posts. Having possibility to use Python/Perl for quickly scripting in Opus would be more satisfying than clumsy VBscript.

There's no reason it shouldn't work as far as I know, as long as it's Active Scripting compatible. Opus doesn't care what language you use.

There does seem to be an issue with ActivePerl and the beta, although it's not something we've intentionally broken.

Until we work out what's causing that problem, you can still use Javascript (JScript) if you want a decent language instead of VBScript. Both are built into Windows.

We would much prefer people used JScript (or VBScript) anyway as it's bad making people install ActivePerl or similar just to use some small add-in scripts. (But ofc. you are free to use whichever languages you want if you have a strong preference, at least if we can make them work again.)

The problem is caused by the script languages not implementing type information, which currently Opus depends on. We'll have a workaround in the next beta.

Is it something that should be reported to ActiveState? If so, could you provide some details (what to report to AS)?

I don't think so since I don't think it's required that they support it - we were just assuming they would since both VBScript and JScript do.

Basically IDispatch::GetTypeInfo is not supported. You could mention it to them if you wanted but we have a workaround for it anyway so it's not a big deal.

Does it work for anyone? I still get the same error in beta3.

ActivePerl worked here w/Beta 3, Win7 x32.

The problem may be limited to XP now, that I use on a test VM.