Advertisements

seemingly both. It's a bug in the MS C stat() function, has been filed
already 2004-01 at ActiveStatehttp://bugs.activestate.com/show_bug.cgi?id=29239 and (likely) can be
circumvented by using Win32::UTCFileTime from CPAN (which contains a
comprehensive explanation).

Advertisements

You would think that the corrections offered by Win32-UTCFileTime could be
incorporated into the perl source. Why that hasn't happened is a question
that should probably be raised with the perl porters (p5p) rather than
ActiveState.

"Sisyphus" <> wrote:
>> I wonder why ActiveState doesn't solve this.
>
>You would think that the corrections offered by Win32-UTCFileTime could be
>incorporated into the perl source. Why that hasn't happened is a question

One could also use a C compiler without the stat() bug as far as I
understand.
>that should probably be raised with the perl porters (p5p) rather than
>ActiveState.

Maybe. I thought it is an ActiveState issue because Cygwin's Perl
works as expected here.

"Oliver Betz" <> wrote in message
news:...
> "Sisyphus" <> wrote:
>
> >> I wonder why ActiveState doesn't solve this.
> >
> >You would think that the corrections offered by Win32-UTCFileTime could
be
> >incorporated into the perl source. Why that hasn't happened is a question
>
> One could also use a C compiler without the stat() bug as far as I
> understand.

Yes - that's my understanding, too. I gather it's a MSVC++ bug, not a Win32
bug, and that a perl compiled on Win32 with, say, MinGW(which is the
compiler I generally use) or Borland won't suffer the problem.
>
> >that should probably be raised with the perl porters (p5p) rather than
> >ActiveState.
>
> Maybe. I thought it is an ActiveState issue because Cygwin's Perl
> works as expected here.
>
> What is ActiveState's contribution?
>

Afaik, they pretty much just take the cpan source, compile it with VC6, and
make the binaries available to the public. Of course, they also contribute
to that cpan source - but I don't regard it as their responsibility to fix
this specific problem. I would think, however, that the perl porters as a
whole would be keen to see this issue resolved - which is why I mentioned
the possibility of contacting them. (It's quite possible that they are
already aware of this, btw. And it's also possible that there are good
reasons that no fix has yet been incorporated into the perl source. This
problem apparently doesn't affect FAT systems - and I don't know if/how that
impacts upon this issue.)

The author of Win32::UTCFileTime might have some advice on how to proceed if
you want to advance the cause. I wouldn't be at all surprised if he has
previously raised it with the porters. (In fact, I'm a little surprised that
he didn't submit patches to the perl source, instead choosing to write a
workaround - which strengthens my suspicion that this problem cannot easily
be fixed.)

Share This Page

Welcome to The Coding Forums!

Welcome to the Coding Forums, the place to chat about anything related to programming and coding languages.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to ask questions about coding or chat with the community and help others.
Sign up now!