This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Handle \r\n in gdbreplay

From: Paul Koning <paulkoning at comcast dot net>
To: Tom Tromey <tromey at adacore dot com>
Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org
Date: Thu, 21 Feb 2019 11:12:07 -0500
Subject: Re: [PATCH] Handle \r\n in gdbreplay
References: <20190221140513.29508-1-tromey@adacore.com> <83sgwhfa1o.fsf@gnu.org> <87y369jfby.fsf@tromey.com>


> On Feb 21, 2019, at 11:06 AM, Tom Tromey <tromey@adacore.com> wrote:
> 
>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> I'm okay with treating \r\n as a single \n, but do we really want to
> Eli> treat a single \r as if it were \n?  I thought systems which used that
> Eli> EOL convention are not really widespread, to say the least.
> 
> I normally handle \r this way out of habit I suppose.  It doesn't matter
> that much to me, I guess \r isn't likely to be seen or made by accident.

Supposedly \r alone is newline in Mac OS 9 and before, which at this point is sufficiently ancient history it may no longer be interesting.

	paul

References:
- [PATCH] Handle \r\n in gdbreplay
  - From: Tom Tromey
- Re: [PATCH] Handle \r\n in gdbreplay
  - From: Eli Zaretskii
- Re: [PATCH] Handle \r\n in gdbreplay
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]