Re: extensions in vms/ext

Peter Prymmer <[email protected]>
Newsgroups gmane.comp.lang.perl.perl5.porters,gmane.comp.lang.perl.ports.vms
Message-ID <OFA6A63511.2A2DE702-ON85257626.003DB328-85257626.003DDD7A@factset.com>
"Craig A. Berry" <[email protected]> wrote on 09/02/2009 08:35:05 PM:

> On Sep 2, 2009, at 4:00 PM, Nicholas Clark wrote:
> 
> > Would it be possible to move vms/ext/DCLsym to ext/VMS-DCLsym, and
> > vms/ext/Stdio to ext/VMS-Stdio, with conditional (not) building 
> > analogous
> > to how ext/Win32* are only built on Windows?
> >
> > I think that would make my plans for refactoring make_ext.pl simpler.
> > (to allow moving dual-life modules modules involved with 
> > Makefile.PLs into
> > ext too). Right now ext/$foo and vms/ext/$bar are at different depths.
> 
> 
> That should be fine, and if for some reason it isn't, we'll find out 
> pretty quickly and deal with it.
> 
> VMS::Filespec is more of a special case because it's used during the 
> build and has hand-rolled XS code hard-wired in vms/vms.c, but because 
> of that it also doesn't need to go through xsubpp or other extension- 
> building steps and shouldn't have any need for special treatment in 
> make_ext.pl.

There may be some changes needed for configure.com and the descrip.mms
template file.  If a test tgz is released I may have some time
to take a look too.

Peter Prymmer
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.