in reply to Re^7: Socket::getaddrinfo and localized error messages on Windows
in thread Socket::getaddrinfo and localized error messages on Windows

Thanks for all this information, however the system getaddrinfo function is already used in my case (and in your case also I think ?).

Indeed the error constants used aren't the ones defined for the emulated versions. Same for the error messages. Your message made me wonder if it was really the case, so I also added debug traces in Socket.pm to make sure of it.

So I don't think your proposal (defining d_getaddrinfo and others) could change anything regarding the problem, but maybe I missed something or misunderstood ?

  • Comment on Re^8: Socket::getaddrinfo and localized error messages on Windows

Replies are listed 'Best First'.
Re^9: Socket::getaddrinfo and localized error messages on Windows
by syphilis (Archbishop) on Apr 25, 2022 at 09:08 UTC
    So I don't think your proposal (defining d_getaddrinfo and others) could change anything regarding the problem

    Aaah ... yes ... I think that's right. As I noted at the end of my Socket bug report, the bug I reported there is in the config settings, not the Socket module.
    Sorry for the interference ... I'll leave you in peace to get on with it.

    Cheers,
    Rob
[reply]
      Sorry for the interference ... I'll leave you in peace to get on with it.

      No interference at all, thanks a lot for taking a look at the problem !

      For the record I'm using a workaround similar to the one I have posted above. When I have some time I will try to take a closer look at the problem and try to find a real fix, but for now it seems to works.

[reply]
        FYI this bug seems to have been fixed somewhere between Strawberry Perl 5.36.1.1 and Strawberry Perl 5.38.0.1 (bug is present in 5.36.1.1 but not in 5.38.0.1, although both use same Socket module version 2.037). So I guess it actually was an issue with Perl core ?
[reply]

In Section Seekers of Perl Wisdom