Web lists-archives.com

Re: [Mingw-users] Secure crt functions not in header files




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26/05/17 15:58, Earnie wrote:
> On 5/26/2017 10:26 AM, Keith Marshall wrote:
>> Notwithstanding the above, and given that we want to keep msvcrt-xref 
>> fully comprehensive, while still generating libmsvcrt.a from the same 
>> symbol reference source, there are some symbols explicitly filtered 
>> out of the import libraries; we could extend the list of such symbols, 
>> if the user population deems it desirable.  I will be guided by the 
>> wishes of any significant number of users here; if you think we should 
>> exclude Microsoft's *_s() nonsense, please say so; if you think we 
>> should support it, please submit patches via the feature request 
>> tracker.
> 
> My vote is to keep them.

I don't have a problem with doing so; however...

> Some poor system might just be using these regardless.

Any such system must (currently) do so, without any dependence on 
prototypes in our headers, for such prototypes don't yet exist.

> I also think if someone wants to provide proper clean room patches
> with appropriate guards for these we shouldn't be glib about adding
> them.

Sure, provided the guards are appropriate, and the poster can cite 
direct MSDN references for content, or can demonstrate a clean room 
technique to fill in any undocumented content.  Hence my request to 
have such patches submitted via our tracker, where we can review, 
discuss, and appropriately vet them.

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZKFYyAAoJEMCtNsY0flo/EC8P/A3vg6ghiubCtOU/II2EsgR5
LhMq/kyy2+CxjojaKCy+6k2EGX6KXw7iHujRhBgkAgnAndLfNppxwZVXJfkIj5Uz
sWjo81GA+4D4vgMY6xygI9F5FQHlwWHozQ6g1PcbEDeXPFdJmurAUZWrO5UuqW5S
UCEVAFGavs6TmdkOoJmIogzCy39gRzQe+LQRemo619z07Q9VidYIz+xsjGnkvhAm
fcVn5ohjYU6b9isXBNxawR0jaZsMVTAKIcIHH5+4oLTqFj4yhqtHr+Ivqd9nBK5w
5lEcbTrtrfVEMFgJrCW15tdK266q+rgehLCiQJXOgIR1bg9cS2LSV5kVmAtvZyJn
XDz88wbv7qmSFVl0XHEgggLv2EWHpAWjz6UlAuF2EZUwCgLILAottcjKXwaF+xVs
c9jl+vKelCec+1IyQ8f9fRkNxxUn4d65V+BuP1BSLCynMZ2vDjEvTqDBJ8fU2pPe
kBOfLxQFAIsfBy6dxYJHD448iAxYB2XgRxIBm9YW/XjHDivvgchmUd9PpTTeklte
LILshXkXRZSOw/N18SmyFC0zb3FbYd/Lhr7arH9csLzmWDCVMHiAyVwKjy15qnFl
GtTVXTxt5m5WIrGmXNoBQHi/UOLR1+dra4dih8tZYQR73GpEPzR5UIbuaFnZh3ly
PU5qasGbxK8RhIhXn7sV
=V9HQ
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe