Re: use PerlScript && die;

Replies are listed 'Best First'.
Re: Re: use PerlScript && die; by $code or die (Deacon) on Sep 04, 2001 at 22:32 UTC
I've contemplated the idea of a command-line shell that used ActiveX scripting for it's "procs". I'd love to use Perl for that, but they can be mixed with basic, etc. I have written Inline::WSH which allows you to use VBScript and JScript in your perl programs. It's a bit rough around the edges so I'm not going to publish it until it's a bit more robust. But then, I've also wondered whether anyone would be interested in such a beast! I wrote it mainly to have a play around with the Inline module. It's very nice, thanks Brian! Windows script Components offers a way to make a COM object in Perl. Absolutely! Its nice, flexible, cheaper and easier than PerlCtrl :) doesn't need compiling, etc. But it's not as portable. I do like Windows Script Components. So I think Perlscript is wonderful. I'd be inclined to diable it for HTML pages, but have it around for files that are obviously meant to be programs. I agree with you. PerlScript is nice, just not in a web browser. I might be wrong, but if you disable PerlScript by setting that registry key, I think it only disables it in IE. As I said, I might be wrong - I haven't tested it. Error: Keyboard not attached. Press F1 to continue.	[reply]
Re: Re: Re: use PerlScript && die; by John M. Dlugosz (Monsignor) on Sep 05, 2001 at 01:19 UTC
What is the portability difference between PerlCtrl and Perl in a WSC? They are both pretty much win32-only topics. Oh, you mean the way PerlCtrl can create a single EXE for running on a machine without Perl?	[reply]
Re: Re: Re: Re: use PerlScript && die; by $code or die (Deacon) on Sep 05, 2001 at 05:10 UTC
you mean the way PerlCtrl can create a single EXE for running on a machine without Perl? Yep - sorry I wasn't very clear on that point. The Perl Dev Kit makes for more distributable applications - especially components. That is if you don't mind distributing components that are around 1mb or more :). You can do it without freestanding mode and have a nice dll around 30k. I worry whenever I see components that are much more than 100kb. It's understandable why they are so big with PerlCtrl - it is compiling perl along with it! On the other hand, if you know your target machines are running Perl - I see no reason not to use WSH to create a component. You can always copy and past the code into a PerlCtrl template at a later date. One other thing I haven't looked into in much detail is the licensing for the Perl Dev Kit. I am pretty sure that you can distribute your applications without worrying, but I imagine that you're only meant to install it on one machine at a time. At least with WSH you can develop your component on any Win32 machine running Perl. By the way, do you think anyone would be interested in an Inline::WSH module? Error: Keyboard not attached. Press F1 to continue.	[reply]
Re: Re: Re: Re: Re: use PerlScript && die; by John M. Dlugosz (Monsignor) on Sep 05, 2001 at 18:52 UTC