| delorie.com/archives/browse.cgi | search |
| From: | "Mark E." <snowball3 AT bigfoot DOT com> |
| To: | djgpp-workers AT delorie DOT com |
| Date: | Tue, 23 Jan 2001 15:35:47 -0500 |
| MIME-Version: | 1.0 |
| Subject: | Re: Where does gcc -o foo make foo.exe |
| Message-ID: | <3A6DA4D3.25820.8356D7@localhost> |
| In-reply-to: | <200101232005.PAA03563@envy.delorie.com> |
| References: | <3A6D9470 DOT 4200 DOT 42F8E2 AT localhost> (snowball3 AT bigfoot DOT com) |
| X-mailer: | Pegasus Mail for Win32 (v3.12c) |
| Reply-To: | djgpp-workers AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp-workers AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
> > > I used __file_handle_modes to store the required flag so that was no problem. > > I also have a function to zero fill the space that is to be filled. Where > > should this function go? I'm thinking src/libc/dos/io but a confirmation > > would be good before I start touching files. > > In cygwin, I put it inside the code for write(). Nobody else uses it. My problem comes from djgpp having write which calls _write and each takes care of calling a fsext hook for write. Mark
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |