delorie.com/archives/browse.cgi | search |
From: | Radical NetSurfer <radsmail AT juno DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Guru Question!! |
Date: | Mon, 16 Oct 2000 17:33:09 -0400 |
Message-ID: | <icsmusk3dhkau8p8g28a38p0qhh23ujpcg@4ax.com> |
X-Newsreader: | Forte Agent 1.8/32.548 |
MIME-Version: | 1.0 |
NNTP-Posting-Host: | 216.202.134.168 |
X-Original-NNTP-Posting-Host: | 216.202.134.168 |
X-Trace: | 16 Oct 2000 17:37:02 -0400, 216.202.134.168 |
Lines: | 28 |
X-Original-NNTP-Posting-Host: | 64.31.79.51 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Paging all DJGPP Guru's! Is the following possible ?? Creating a buffer dynamically with malloc at runtime which is then able to be treated as if it were actually a FILE* openfile("ram_buffer","rb"); [i.e. AFTER this operation actually takes place] SUCH THAT any and all file i/o functions could be used on that __buffer__ even though its actually something that is created in RAM at runtime? [treated as if it were the contents of a file referenced with FILE*, etc.] Is there some kind of emulation for this kind of operation even though FILE I/O isn't what it might be called? ANY discussion appreciated.... email: radsmail AT juno DOT com http://members.tripod.com/~RadSurfer/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |