John Reid wrote:
>  Environment: Windows XP SP2, 2.8GHz P4, 1GB RAM
>  Logged in as "limited user" (i.e. not administrator on local machine)
>  
>  VBScript Converter:
>  ===================
>  Wonderfully useful app!  I've also used this to convert VBScript parts 
>  of SQL Server DTS packages to PerlScript.
>  The Wscript object is not implemented, but I wouldn't have expected it 
>  anyway.
>  
>  MS example version.vbs shows up many unimplemented functions & errors:
>  
>  #### Error: Unexpected method of wscript.version at 
>  /PerlApp/VBSPerl/WScript.pm line 322, <FH> line 28.
>  #### Error: Haven't yet implemented function scriptenginemajorversion
>  scriptenginemajorversion
>  #### Error: Haven't yet implemented function scriptengineminorversion
>  scriptengineminorversion
>  #### Error: Can't resolve progID WINMGMTS
>  #### Error: Can't resolve progID WScript.Shell
>  
>  
>  ------------------------------------------------------------------------
>  
>  _______________________________________________
>  PDK-Beta@[...].com
>  http://listserv.ActiveState.com/mailman/listinfo/pdk-beta

Hi, John,

You're right about not implementing the WScript object.  The Perl
code the tool generates is expected to be run from an environment
outside a WScript host.  For a related reason, we didn't convert
ScriptEngine*Version, as the Perl values wouldn't bear any relation
to the VBScript version.

How is the VBScript code referencing WINMGMTS and WScript.Shell?  We have examples
using both that pass our regression tests?

Thanks for the feedback.  Glad you find the tool useful.

- Eric