Re: Why does perl need internal CRT structures in Win32?

Hi,
This is a question that would be better asked on the p5p mailing list (
[email protected]), or raised as an Issue at
https://github.com/Perl/perl5/issues .
And I encourage you to ask about this on either one of those 2 forums.

Having someone who is involved in the development of mingw-w64 (such as
yourself) take an active interest in perl is something we'd definitely
welcome.
For example, https://github.com/Perl/perl5/issues/17521 has been causing
some head-scratching for about 3 month.

Cheers,
Rob


On Sat, May 8, 2021 at 6:38 AM Biswapriyo Nath <[email protected]> wrote:

> The issue arises when perl is compiled with GCC and UCRT (Universal C
> RunTime). The UCRT is different than older MSVCT. There are many
> internal undocumented structures in whole win32 directory. In public
> WinSDK, those are just opaque or should be accessed with public APIs.
> For example,
>
> 1. the __crt_stdio_stream_data structure is used as _iobuf or FILE.
> Instead it should be accessed with _fileno.
> 2. the ioinfo structure is used to get/set standard I/O handles.
> Instead it should be accessed with _get_osfhandle.
>
> So, my question, is it possible not to use those internal structure
> but use public documneted APIs instead?
>
> --
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> http://learn.perl.org/
>
>
>