develooper Front page | perl.perl5.porters | Postings from March 2007

Re: test skipping based on $Config{extensions} (was: Re: [PATCH]Re: [PATCH] Re: Win32 modules & cygwin)

Thread Previous
From:
Andy Dougherty
Date:
March 13, 2007 20:15
Subject:
Re: test skipping based on $Config{extensions} (was: Re: [PATCH]Re: [PATCH] Re: Win32 modules & cygwin)
Message ID:
Pine.LNX.4.62.0703132306270.21270@fractal.phys.lafayette.edu
On Tue, 13 Mar 2007, Craig Berry wrote:

> On a related note, I find I am no longer confident I understand what
> "known extension" means.   Porting/Glossary says, "all XS extensions
> included in the package."  It never occurred to me to add the Win32
> extensions to $Config{known_extensions} on VMS until this thread
> started because there is no meaningful sense in which those extensions
> will ever be included in a non-Win32 build.  Is merely occupying space
> in the source tarball what we mean by "included"?

First, known_extensions is probably not terribly useful outside of 
Configure, so I don't know what use one could reasonably make of it. It 
was originally intended to be all extensions included in the source 
tarball + all extensions the user may have unpacked under the source 
directory.  (Since I didn't have dynamic loading, and MakeMaker.PL hadn't 
been invented yet, unpacking extensions under the ext/ tree was how how I 
added extensions to perl5.)  At the time I wrote the description, there 
were no Win32 or VMS extensions.

At the moment, 'known_extensions' contains extensions under ext/.

-- 
    Andy Dougherty		doughera@lafayette.edu

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About