Re: [MinGW-dvlpr] _CRTIMP problem

[Earnie B. <ear...@ya...>]

Danny Smith wrote:
> ----- Original Message -----
> From: "Earnie Boyd" <ear...@ya...>
> To: <min...@li...>
> Sent: Thursday, 6 February 2003 11:45
> Subject: Re: [MinGW-dvlpr] _CRTIMP problem
> 
> 
> 
>>Danny Smith wrote:
>>
>>>No, I'll fix in my local patchset and apply to CVS as soon as
>>>mingw-runtime version is bumped
>>>
>>
>>Are there any outstanding issues?
>>
> 
> None to my knowledge.  I intended to wait till after release before
> adding the vscanf functions contributted by  Aaron  (AWLaFramboise).
> 

Great, I'll prepare a release this weekend.  I'll do w32api as well 
while I'm at it.  And I would like to do a MinGW-2.0.1.exe release; but 
  which GCC should I use?  Which binutils?

>  Basic tests with these vscanf functions have all succeeded.  Having
> them in runtime modifies how libstdc++ is built. With them, the
> configury finally says yes:
> #define _GLIBCPP_USE_C99 1
> exposes all the C99 functions  and promotes them to namespace std.

Nice.  What other mingwex extentions should we consider?  Maybe, a 
working ftell, fscan, etc.?

Earnie.