PF>   In fact, you should not let another dll (that has it's own
runtime) PF>   touch a 'FILE *' at all (for fread, fprintf,  anything).

 DD> Makes sense.  If, for some reason, you decided to let another dll
 DD> handle a file that had been opened by another bit of code, would you
 DD> suggest using DosOpen() with an 'HFILE' file handle, or _open() with an
 DD> 'int' file handle?

No -- if you take my argument farther,  what I am saying is that only the
unit that opened the file should do i/o to it.   For example, let's say you
create a dll called "logfile.dll" -- the prototypes for it might
look like this:

 LOGFILE *LogOpen(char *filename);
 int LogWrite(LOGFILE *lf, char *fmt, ...);
 void LogClose(LOGFILE *lf);

Where LOGFILE is a private structure that would contain the file handle,or
FILE*,  or whatever....the caller does not (and should not) need to know.


--- Maximus/2 3.00