Re^9: Socket::getaddrinfo and localized error messages on Windows

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

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

Replies are listed 'Best First'.
Re^10: Socket::getaddrinfo and localized error messages on Windows by Yaribz (Beadle) on Apr 25, 2022 at 21:12 UTC
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]
Re^11: Socket::getaddrinfo and localized error messages on Windows by Yaribz (Beadle) on Apr 27, 2024 at 20:38 UTC
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]