Bob Friesenhahn wrote:
On Sun, 21 Dec 2003, Guido Draheim wrote:
Well, that doesn't work that well if you are writing a C++ POSIX binding and don't want to duplicate those data structures. But I see you point. Maybe I should make the affected functions artificially templated, this would get things right.
How do win32 c++ headers deal with shapeshifting types?
It seems to me that most WIN32 file APIs (e.g. stdio) are stuck with 32-bit file offset limitations even though NTFS supports huge files.
Well actually I meant the shapeshifting about other basic types like "int" and perhaps "char". That has somewhat travelled into c++ IIRC but I am not too deep into this to remember anything special about. The c++ suite does support variants of that AFAIR.
There are some extended interfaces which support large file offsets. It is possible to access and use large files with the WIN32 API, but only by using a limited number of low-level interfaces (typically underscore prefixed).
Remember that WIN32 started with NT 4.0 (3.0?) and Windows '95 ...
Yepp, the win32 kernel is largefile but the win32 libc does not expose it in the same and easy way as unix98-compatible platforms do. Didn't we had that topic already? Ah, right, there it is where that impression came from... http://ac-archive.sf.net/largefile/win32libc.html http://ac-archive.sf.net/largefile/win32.html
cheers, -- guido http://google.de/search?q=guidod GCS/E/S/P C++/++++$ ULHS L++w- N++@ s+:a d(+-) r+@>+++ y++ 5++X- (geekcode)
