From: Paul G. <pga...@qw...> - 2001-02-20 23:03:36
|
On 20 Feb 2001, at 17:11, the Illustrious Earnie Boyd wrote: > Paul Garceau wrote: > > > > > My first thoughts were something like libisonew.a or > > > libnewansi.a but if dirent goes there also (I don't think it > > > should), those are not appropriate. My idea was to keep it > > > strictly for missing ISO C89/C99 functions, mainly the > > > latter. > > > > How about libisoansiext.a or libisoext.a? (personally > > I like > > libisoext.a) but don't have any hard-preferences... > > > > Just something that popped into my head when I was > > thinking > > about what was mentioned above. > > > > Yes, if we're speaking strictly of ISO extensions this > libisoext.a fits nicely. <g> Thanks, Earnie. Peace, Paul G. > > Earnie. > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |
From: Paul G. <pga...@qw...> - 2001-02-21 00:43:55
|
<color><param>0100,0100,0100</param>On 20 Feb 2001, at 22:50, the Illustri= ous Danny Smith wrote: <italic><color><param>0000,7F00,0000</param>> Hello all > > The attached file contains a start for libnewname.a. > It contains function which are in C89 and C99 standard but not in > msvcrt.dll They are based (mostly) on Doug Gwynn's Q8 package, > with the Q8 macros replaced with appropriate values for mingw </italic></color> Can you give me a link? I'm not having much success try= ing to find Doug Gwynn's Q8 package using Google. I did find wmemchr, and the following seems to be a derivation from ISO/IEC 9899:1990/Amendment 1:1995 (E). <italic><color><param>0000,7F00,0000</param>> > functions declared in wchar.h (patched file) > wmemchr > wmemcmp > wmemcpy > wmemmove > wmemset > fwide (declared as extern inline) > mbsinit (declared as extern inline) </italic></color>In terms of the following <italic><color><param>0000,7F00,0000</param>> function declared in inttype= s.h (new file). > imaxabs > imaxdiv > strtoimax (alias strtoll) > strtoumax (alias strtoull) > wcstoimax (alias wcstoll) > wcstoumax (alias wcstoull) </italic></color> Could be added to either an existing .a (eg. libmingw32.= a) or we could create a new library called libcwcext.a. Some Unix systems put inttypes.h into /mint. Did some checking and found that inttypes.h wasn't included as part of Cygwin because it is not considered Unix Standard, as useful as inttypes.h could be, especially as the industry shifts from 32bit to 64bit desktop processors....64bit compilers are not something I know a great deal about. As it stands, however, it appears that we don't really have a problem here when it comes to adding inttypes.h. It is just a matter of deciding how... <italic><color><param>0000,7F00,0000</param>> The fwide and mbsinit don't = really do anything useful, </italic></color> Well, perhaps not...my win32api documentation tells me t= hat fWide is defined to be used as part of shell (shellobj.h) and is specifically defined for use as part of DROPFILES: <italic><color><param>0000,7F00,0000</param>> Defines the CF_HDROP and CF_= PRINTERS clipboard formats. In the > CF_HDROP case, the data that follows is a double - > null-terminated list of file names. For CF_PRINTERS, the data > that follows are the printer friendly names. > > typedef struct _DROPFILES { > DWORD pFiles; // offset of file list > POINT pt; // drop point (coordinates depend on fNC) BOOL > fNC; // see below > BOOL fWide; // TRUE if file contains wide characters, > // FALSE otherwise > } DROPFILES, FAR * LPDROPFILES; > > > Members > > fNC > > Nonclient area flag. If this member is TRUE, pt specifies the > screen coordinates of a point in a window=92s nonclient area. If it > is FALSE, pt specifies the client coordinates of a point in the > client area. </italic></color> "mbsint" is not included as part of Win32api. > <italic><color><param>0000,7F00,0000</param>> but they don't really need t= o yet. </italic></color> Peace, Paul G. Nothing real can be threatened. Nothing unreal exists. |