in reply to Re: Re: use PerlScript && die;
in thread use PerlScript && die;

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?

Replies are listed 'Best First'.
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]
      You can do it without freestanding mode and have a nice dll around 30k.
      I didn't know it could make a DLL. I tried PerlApp and saw it make EXE's.

      Yea, ship the perl.dll separatly. It's no worse than VisualBasic with it's huge DLL. Or rather, ship them together but install them as separate parts, installing or updating the DLL as needed, and installing the bundled component.

      By the way, do you think anyone would be interested in an Inline::WSH module? .
      I have no idea. Why would anyone need another scripting language when writing in Perl? Writing someting in C I can see the need for, but Java or Basic?

      But here's a novel use: spin off objects as servers to do your multithreading needs.

      —John

[reply]

In Section Meditations