Date: Sun, 11 Jul 1999 11:10:21 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Michel de Ruiter cc: djgpp-workers AT delorie DOT com Subject: Re: DJGPP cvs and gcc-2.95 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 9 Jul 1999, Michel de Ruiter wrote: > - There are 8 filenames ending in .orig in manifest/djlsr202.mft. I > realize the *203.mft have not been created yet, so the *.orig will > not be in them. True? Not necessarily. Some such files are left in djlsr, in case we change our minds and want the older version, or if the changes are too radical and scary. I don't know what did DJ plan for v2.03, but on v2.02 there are a few of those. > - I remember having discussed a patch (proposed by me :-) to > src/libc/dos/io/setmode.c, so setting a tty to O_BINARY would at > least give an interruptible situation. Is the situation fixed, in > some other way, or do we want to leave the situation as is (at least > for 2.03)? Nothing's changed in this aspect since v2.02, except that you now have termios that Does The Right Thing for single-character input. > - src/libc/dos/io/setmode.txh discusses to some length the possibility > to read the console in binary mode. Is there any situation where > this could be useful? Why, yes--if you want to read the console in binary mode ;-) Seriously, though: I don't understand the question. The discussion in the docs draws upon experience from several programs that really do what is described there. One example that comes to mind is the ported Less; gzip and cat are two others. I wrote all that docs in the hope that my experience will be useful to someone, some day... > And, as the input is line buffered, > __djgpp_set_ctrl_c will not really help to generate signals, will > it? Or do I still miss something, about console in binary mode? When you switch the console to binary mode, the library puts the console device into raw mode, whereby input is not line-buffered anymore, at least not by DOS. So you *can* say e.g. "read (0, &c,1)" and read a single character into c. > During compiling, gcc issued the following warnings. I have not had > the time to "correct" them (yet). Neither have I. All those warnings pop up with GCC 2.7.2.1 as well. > scheck.c: In function `scheck': > scheck.c:56: warning: cast discards qualifiers from pointer target type What's scheck.c? I don't think I ever saw that file.