Sorry, something went wrong and a reply was sent to the original sender in stead of the list.
So this is our communication. For completeness, I kept all of the original answer. > >>What you ask for is a real PERL compiler that creates VMS-compliant >>objects, isn't it? > >Yes, or even simply a "builder" that could compile and link an >entire set pf perl scripts into an image that one could invoke with >RUN. I guess what I'm saying here is that typically a Perl script >pulls in many other perl modules and if compiling them separately into >individual modules was too hard then for my purposes at this point >just having an image alone would be nice. My particular need arises >from my recent work in Spamassassin. Think about the way it's >used. >It's invoked once for every single mail message coming into the system >and each time it's run that means Perl is re-building (er, um >compiling and linking or whatever the Perl builder does internally) >the program before running it. >That's a ton of wasted CPU time and unnecessary latency in mail >proccessing and won't scale well. > I don't care how it's done. As long as the result is a real VMS executable that can be saved and rerun whenever appropiate. Purely for the sake of efficience (a VERY BIG issue for small systems...) >>Agreed, this could be a big win! > >I think so too. :^) > >>Still, I do have some concerns but didn't reply yet (on- or off-list) >on Craig's message. >>Most important is there is the real danger(!) that Perl programs will >>introduce even more Unix-like requirements like STREAM_LF files and >>inter-process communication (the PIPEs). I agree that if there is some >>form of communication between different systems, you'll have to use >>some 'generic' format, but system-specific methods must be possible >>when communication on one platform (MBX on VMS, for instance). >> >>It should be VERY clear - to ANY developer on this project - that VMS >>is NOT another Unix. It can do some things the Unix way, but it has >>quite some capabilities Unix can only deram about. USE THEM. > >I'm not sure I gather how the latter part of your email connects to >the first part, the part about pre-compiled Perl. > There's no relation - at least, not directly. It's merely a matter of general concern, where I see my VMS machine's security and robustness compromised by the (immature?) Unix- or even Windows-based style of solving trivial issues - where VMS has a perfect solution. But in part, it is. One of the issues I ran into using Java code is the (IMHO ridiculous) inefficiency of this environment. If perl goes the same route, I will abandon it as well. Just for that reason. >Karol > >============================== >Karol E. Zielonko Jr. >OpenVMS Engineering >Hewlett-Packard Company > >If you have me in your address book please configure the entry to indicate >that >I prefer to receive plain text. Willem Grooters OpenVMS developer & System manager e: [EMAIL PROTECTED] w: www.grootersnet.nl
