At 06:21 PM 1/13/2002 -0500, Michel Lambert wrote: >Trying to track down various MSVC warnings that I'm getting, but I'm stuck >about what to do, for this one: > >In win32, PIOHANDLE is typedef'ed as HANDLE.
Please disregard this code, I've just submitted those as stubs and will be cleaning those up. >Being unfamiliar with win32 io code, I don't know the proper solution to >this. I think there are two options: one is to forgo handles and go with There is no cause for alarm, I haven't put ops into the interpreter for it so it is just compile time code that I will clean up. I had simply been testing the "unix" versions of some calls on Win32 and forgot to delete them out before submitting the stubs. It was only there for people to tinker and look at the layer API, not to consider as real code. >stdio interface, using open, close, etc as defined in VC98\Include\IO.H. The >other is to stick with HANDLE's on windows, and try to find a way to lseek >on HANDLEs. Or alternately, it's perfectly fine the way it is and we just >need to silence the warning. We aren't using stdio, we are implementing our own IO lib, and on Win32 this means using the Win32 calls for all this stuff, I just forgot to delete the code before submitting the stubs for the Win32 layer. I had been concentrating on 2 other layers (unix and stdio). I'll submit some updates this week to clean all this up. For now, the only thing to consider "useable" in the IO system is the fact that it creates the stdin/stdout/stderr handles on Win32 and UNIX systems which can be used instead of fprintf or printf. -Melvin
