public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Doug Evans <xdje42@gmail.com>, Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add support for embedding scripts in .debug_gdb_scripts.
Date: Fri, 13 Feb 2015 18:05:00 -0000	[thread overview]
Message-ID: <54DE3CE9.1090802@redhat.com> (raw)
In-Reply-To: <CAP9bCMQM_cmsEwxNAjaSo+WNR_xOQ1Sqi6Z0VicUHFTyi47wZw@mail.gmail.com>

On 01/20/2015 04:35 PM, Doug Evans wrote:

> I for one would liked to have seen the data to back up
> the claim that NUL-terminated is archaic.
> It's not that I don't trust someone's judgement, rather it's that that's
> the wrong way to impose the change.

I think saying NUL instead of "null" is as archaic as saying CR instead of
"carriage return", LF instead of "line feed", NL instead of "new line",
etc.  I mean, maybe archaicness is not really the issue.

IMO, it's just a matter of whether we think using the character's
control code symbol is OK instead of the full name.  I think the
decision should be based on that alone.

E.g., would we write:

 "If this section exists, its contents is a list of entries separated
  by CR NL, specifying scripts to load.  The list is terminated with
  a NUL character."

?

Thanks,
Pedro Alves

  parent reply	other threads:[~2015-02-13 18:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 17:32 Doug Evans
2015-01-15 18:11 ` Eli Zaretskii
2015-01-16 17:15   ` Doug Evans
2015-01-16 18:02     ` Eli Zaretskii
2015-01-17  1:16       ` Doug Evans
2015-01-17  8:16         ` Eli Zaretskii
2015-01-18  4:16           ` Doug Evans
2015-01-18 16:23             ` Eli Zaretskii
2015-01-18 20:48               ` Doug Evans
2015-01-19 14:49                 ` Joel Brobecker
2015-01-20 16:35                   ` Doug Evans
2015-01-21  9:57                     ` Joel Brobecker
2015-02-13 16:15                     ` Stan Shebs
2015-02-13 16:45                       ` Eli Zaretskii
2015-02-13 16:46                       ` Andreas Schwab
2015-02-13 18:05                     ` Pedro Alves [this message]
2015-02-15 11:53                       ` Corinna Vinschen
2015-01-19 16:05                 ` Eli Zaretskii
2015-01-31 23:31 ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54DE3CE9.1090802@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).