El 25/06/2021 a las 20:36, Keith Marshall escribió: > The documentation describes it as a POSIX function, (in name at least, > and albeit deprecated for use with MSVC), but its behaviour definitely > does NOT conform to the POSIX.1 specification. > > I've written a description of the issue, and proposed corrective action, > as ticket https://osdn.net/projects/mingw/ticket/42561 > > I would appreciate a review of my proposed changes, by the MinGW user > community. In the absence of any objections, I plan to incorporate the > proposed (option 4) change into the next mingwrt release. > > TIA. > > Likely I'm the less qualified person to pull an opinion in this list: Anyhow, here it is: If I code for Windows I expect my app to behave as if I have compiled it only with MS tools (VC++, etc). If I have a doubt about some command I usually search for info at MSDN. If I code for multiplatform I expect the same behaviour in all OS's. In case of searching for info, I prefer GNU docs. Knowing that MS Windows does on its own about standards, but time to time they regret and follow them, having my app compliant seems a good idea. If I want to make my life easier, I need a quick way to set/change the target (POSIX or MS), so I can adapt my app to a new MS scenery. My propose: I simple option at compiler command "-D_POSIX_FULL" or "-D_POSIX_MS" that overwrites some default #define in mingw headers. For such default I prefer POSIX-compliant, due to mingw's heart is GNU. THX
Fork