Bug in MS C unlink() ?

[Jerome Schneider]

In article <9849 at smoke.BRL.MIL>, gwyn at smoke.BRL.MIL (Doug Gwyn ) writes:
> In article <1205 at naucse.UUCP> jdc at naucse.UUCP (John Campbell) writes:
> >Oh well, I just followed up to suggest that MSC and PC implementors shouldn't
> >provide an unlink() that is not compatible with the unix counter part.  ...
> >.....

MSC 5.x provides the atexit() mechanism for stashing up to 32 function 
pointers to be called at exit (and _exit).  This would seem the likely
spot to process any unlinks() from open file handles.  Agreed, it does
not address the question of what I/O to an unlinked but open file really
means. 

-- 
Jerome Schneider              UUCP: killer!jls.DALLAS.TX.US (guest account)
Aspen Technology Group        Ft. Collins, CO    Voice: (303) 484-8466