> From: Gavin Smith <[email protected]> > Date: Thu, 19 Feb 2026 17:40:38 +0000 > > At this stage, I'm actually slightly concerned about adding new include > directives to files and worry it could cause breakage due to the wrong > definitions being used, files being included in the wrong order, or whatever. > I don't want to do another pretest as it has already been tested enough > and we are hardly making any changes now, and it's a burden on interested > users who want to help test the pretests.
I agree. > I notice that convert/call_conversion_perl.c does not include any system > include files either and yet it uses fprintf and size_t, at least. Yet > there have been no reports of errors. Evidently the correct header files > are being included indirectly. Yes, through main/converter_types.h. But there's no way for me to get the prototype of strndup by including some system header, because MinGW doesn't have this function, so strndup will not appear in any system header.
