Re: [documentation] winedev-kernel

2005-03-13 Thread Troy Rollo
On Sun, 13 Mar 2005 19:21, Dmitry Timoshkov wrote: > "Eric Pouech" <[EMAIL PROTECTED]> wrote: > > > For asynchronous read operations, hFile can be any handle opened with > > > the FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket > > > handle returned by the socket or accept functio

Re: [documentation] winedev-kernel

2005-03-13 Thread Dimitrie O. Paun
On Sun, Mar 13, 2005 at 09:17:08AM +0100, Eric Pouech wrote: > Also, we miss in the KERNEL32 part some information on > - 16 bit support (and DOS of course) > - Global vs local vs heap allocation Yes, these would be very useful. I'll keep it open then. -- Dimi.

Re: [documentation] winedev-kernel

2005-03-13 Thread Eric Pouech
Dmitry Timoshkov a écrit : "Eric Pouech" <[EMAIL PROTECTED]> wrote: For asynchronous read operations, hFile can be any handle opened with the FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket handle returned by the socket or accept function. which means that ReadFile() only works

Re: [documentation] winedev-kernel

2005-03-13 Thread Dmitry Timoshkov
"Eric Pouech" <[EMAIL PROTECTED]> wrote: > >>>For asynchronous read operations, hFile can be any handle opened with the > >>>FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket handle > >>>returned > >>>by the socket or accept function. > >>> > >> > >>which means that ReadFile() onl

Re: [documentation] winedev-kernel

2005-03-13 Thread Eric Pouech
Dmitry Timoshkov a écrit : "Eric Pouech" <[EMAIL PROTECTED]> wrote: For asynchronous read operations, hFile can be any handle opened with the FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket handle returned by the socket or accept function. which means that ReadFile() only works

Re: [documentation] winedev-kernel

2005-03-13 Thread Dmitry Timoshkov
"Eric Pouech" <[EMAIL PROTECTED]> wrote: > > For asynchronous read operations, hFile can be any handle opened with the > > FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket handle > > returned > > by the socket or accept function. > > > which means that ReadFile() only works on s

Re: [documentation] winedev-kernel

2005-03-13 Thread Eric Pouech
Dimitrie O. Paun a écrit : Does this complete task Documentation/Devel Guide/6 on the TODO list? not yet IMO. I'd like to re-balance the content of the archi chapter and the one of the kernel modules chapter (ie move the details of process, DLL and memory handling from the former to the later).

Re: [documentation] winedev-kernel

2005-03-13 Thread Eric Pouech
Dmitry Timoshkov a écrit : "Eric Pouech" <[EMAIL PROTECTED]> wrote: + File management + + With time, Windows API comes closer to the old Unix paradigm "Everything + is a file". Even if it grew better over the years, it's still not 100% + there (for example, you cannot use ReadFile() ov

Re: [documentation] winedev-kernel

2005-03-12 Thread Dmitry Timoshkov
"Eric Pouech" <[EMAIL PROTECTED]> wrote: > + File management > + > + With time, Windows API comes closer to the old Unix paradigm "Everything > + is a file". Even if it grew better over the years, it's still not 100% > + there (for example, you cannot use ReadFile() over > + a socket h

Re: [documentation] winedev-kernel

2005-03-12 Thread Dimitrie O. Paun
On Sat, Mar 12, 2005 at 09:29:44PM +0100, Eric Pouech wrote: > some DocBook cosmetic stuff, and new docu (file management being the most > important one) Very nice! Does this complete task Documentation/Devel Guide/6 on the TODO list? -- Dimi.