Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Craig Berry
On Wednesday, July 23, 2003, at 03:16PM, Michael G Schwern <[EMAIL PROTECTED]> wrote: >On Wed, Jul 23, 2003 at 08:26:01AM -0500, Craig A. Berry wrote: >> We'd have to know (or determine at compile-time) whether the compiler >> had this capability > >Ok, should be a simple matter of having Config

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Michael G Schwern
On Wed, Jul 23, 2003 at 04:03:47PM -0500, Craig Berry wrote: > Again, the advice is general and does not refer specifically to Perl or Perl > extensions. "Everywhere" just means everywhere that the tokens in question will be > seen by the compiler. For a Perl extension, it might make perfect se

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Craig Berry
On Wednesday, July 23, 2003, at 03:18PM, Michael G Schwern <[EMAIL PROTECTED]> wrote: >On Wed, Jul 23, 2003 at 08:16:42AM -0500, Craig A. Berry wrote: >> Putting something >> like the following in a header that will be seen everywhere is what >> I'm talking about. >> >> #ifdef __VMS >> # define

Re: Good news for MakeMaker on VMS

2003-07-23 Thread Michael G Schwern
On Wed, Jul 23, 2003 at 11:24:04AM -0400, [EMAIL PROTECTED] wrote: > Next you'll want to apply Michael Schwern's latest > update to ExtUtils::MakeMaker (bring it up to 6.10_08): > > http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-07/msg01285.html Damn, that's a malformed patch. --

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Michael G Schwern
On Wed, Jul 23, 2003 at 08:16:42AM -0500, Craig A. Berry wrote: > At 12:21 AM -0700 7/23/03, Michael G Schwern wrote: > >On Tue, Jul 22, 2003 at 11:56:04PM -0500, Craig A. Berry wrote: > >> > I hacked up a quick patch to change LSB to LSB1 and MSB to MSB1 (attached). > >> > >> That should work. I

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Michael G Schwern
On Wed, Jul 23, 2003 at 08:26:01AM -0500, Craig A. Berry wrote: > We'd have to know (or determine at compile-time) whether the compiler > had this capability Ok, should be a simple matter of having Configure compile a short C program which contains two symbols with the same case. Just like it tes

RE: Good news for MakeMaker on VMS

2003-07-23 Thread PPrymmer
Carl Friedberg wrote: !Peter, would you mind explicitly listing those four patches? I'm just catching up for another round of !testing... thanks, ! !Carl No I do not mind, in fact I'll CC the list on this since it is tough to keep track of this stuff on a platform that does not support rsync

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Craig A. Berry
At 12:03 AM -0700 7/23/03, Michael G Schwern wrote: >On Tue, Jul 22, 2003 at 11:56:04PM -0500, Craig A. Berry wrote: >> It is possible to configure a build of Perl to use case sensitive >> symbols on any somewhat recent compiler/OS version, but this behavior >> is not the default. > >Why isn't that

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Craig A. Berry
At 12:21 AM -0700 7/23/03, Michael G Schwern wrote: >On Tue, Jul 22, 2003 at 11:56:04PM -0500, Craig A. Berry wrote: >> > I hacked up a quick patch to change LSB to LSB1 and MSB to MSB1 (attached). >> >> That should work. I tend to use a macro to point the case sensitive >> name to another non-con

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Michael G Schwern
On Tue, Jul 22, 2003 at 11:56:04PM -0500, Craig A. Berry wrote: > > I hacked up a quick patch to change LSB to LSB1 and MSB to MSB1 (attached). > > That should work. I tend to use a macro to point the case sensitive > name to another non-conflicting one. That works on any version of > VMS and do

Re: Bit::Vector 6.3 problems on VMS

2003-07-23 Thread Michael G Schwern
On Tue, Jul 22, 2003 at 11:56:04PM -0500, Craig A. Berry wrote: > It is possible to configure a build of Perl to use case sensitive > symbols on any somewhat recent compiler/OS version, but this behavior > is not the default. Why isn't that the default? -- We're talkin' to you, weaselnuts.