>For efficiency, I've snipped quite a bit :-). > >> >>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. > >Perl will never be a compiled language the way FORTRAN and COBOL are, >though of course it compiles its scripts to bytecode before >executing them. On the Perl to C translator, see: > >http://www.perldoc.com/perl5.8.4/pod/perlcompile.html > >I think what this gets you in that subset of cases for which it even >works is a Perl op-tree implemented in C. In other words, you get a >C program that executes the particular stream of Perl byte codes that >make up your program. > >
Combined with Nico Baggus' remark: that's ok - for me anyway. See what can be achieved on VMS for that. >>>>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. > >Calm down, Willem. What the project needs is more developers able >and willing to keep up the tradition of letting Perl be Perl, and use >the C run-time, homegrown hacks, VMS system services, DCL, and >anything else within reach to make that happen. What the project >does NOT need is to have this list become yet another forum for OS >wars. > Don't worry, I don't start a war. I just wanted to point out that this is exactly what is needed on the VMS side. I'm quite willing to team in, were it not that my knowledge of Unix (or Windows) is limited to the 'outside' of these system. But I'll try and work my way into Perl to let it work - whereever required and possible - the VMS way as well. (What level of platform independence is either required, advisable or just handy? And in what way can discrepancies be handled? These are, IMHO,. quite basic questions, if you want Perl to be really usable on virtually ANY platform. But that might well be a very different discussion) Willem Grooters OpenVMS developer & System manager e: [EMAIL PROTECTED] w: www.grootersnet.nl
