Re: _tfinddata64_t

On 18/10/13 13:10, Earnie Boyd wrote:
>> So, should we also adjust the non-unicode case for _tfinddata_t, in
>> tchar.h, or should we just drop these altogether?
> 
> No.  See http://msdn.microsoft.com/en-us/library/se784sk6.aspx.

Doh!  Had I added site:msdn.microsoft.com to my google search terms, I
might have found that; as it was, "msdn" and "_tfinddata64_t" didn't
turn it up, (at least not sufficiently close to the top).

So, while "no" doesn't answer the question, the answer is clear: we need
to adjust the definition in tchar.h, to be correct for both cases.

> We also might want to map the misnamed types to the corrected names
> for the 4.0.4 point release and remove the mapped types in 5.0.

Perhaps.  The lack of complaints about the current incorrect definitions
suggests that the feature isn't much used; it may be sufficient to
simply correct the errors, and forget about preservation of the incorrect.

-- 
Regards,
Keith.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk