X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Tue, 18 Jun 2013 19:26:05 +0300 From: Eli Zaretskii Subject: Re: General Protection Fault error is intermittent In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <8361xbs7vm.fsf@gnu.org> References: <36e857f0-9899-496b-9fc6-32251e109888 AT googlegroups DOT com> <858cbded-7989-46e6-a997-93f842cdb3b0 AT googlegroups DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Tue, 18 Jun 2013 07:43:24 -0700 (PDT) > From: rugxulo AT gmail DOT com > > > Remind me again, is DOS newline : "\r\l" or "\r\n" ??? > > Most DOS calls assume CR (carriage return) plus LF (linefeed), aka 0xD 0xA. No, DOS calls know nothing about the end-of-line conventions. > The DOS kernel API usually assumes CR+LF. No, the DOS kernel doesn't care. It's the C library that does. The DOS kernel functions always read and write in what we call the "binary mode", i.e. they don't make any conversions between newline and CRLF or vice versa. This is always done by the C library.