so far ?
Probably the latter. This is an easy matter with the
`__DEFINE_CPP_OVERLOAD_SECURE_FUNC_*` macros. You may propose a patch
(or wait for me for a few days).
From 8e401bb2a237aa2e55fdb62963ebc589a8ddedb9 Mon Sep 17 00:00:00 2001
From: Scr3amer
Date: Sun, 7 Mar 2021 03:31:22 -0500
merge request system.
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
From f0c63b8787c803be71e6b72bf09d364a8c9ac402 Mon Sep 17 00:00:00 2001
From: Scr3amer
Date: Sun, 7 Mar
Oops sorry. I thought it would have been easier with that system. My bad.
Please find the patch enclosed to this mail.
Just to be sure that it is the proper file format I used this command
to generate it:
git format-patch -1 HEAD
Is it good ?
One last thing, pure curiosity but is there a s
Hello Liu,
Thanks for the quick reply.
I submitted a pull request (hoping it makes things easier than just a
patch in a mailing list).
https://sourceforge.net/p/mingw-w64/mingw-w64/merge-requests/17/
Cheers,
Scr3am
Liu Hao a écrit :
在 2021-03-05 08:10, scr3a...@auresium.com 写道:
Note t
Hello again,
I also noticed something in
https://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/mingw-w64-headers/crt/sec_api/stdlib_s.h
We are missing the C++ variants of the wcstombs functions that we can
find here in MSDN:
https://docs.microsoft.com/en-us/cpp/c-runtime-library/refer
Hello everyone,
It is the first time I involve myself in an open source community so
sorry if I do something wrong.
I noticed that there is a discrepancy between the API exposed by MinGW
and the one in official Windows headers for the function
SymLoadModule64.
https://sourceforge.net/p/min
