Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH, doc RFA] Fix lazy string type docs
Date: Thu, 03 Nov 2016 23:55:00 -0000	[thread overview]
Message-ID: <CADPb22TETj2o19MZw2GYby1Swe=4RFeT2r1HvKbxfZz8Nv7euQ@mail.gmail.com> (raw)
In-Reply-To: <83y410l6wa.fsf@gnu.org>

On Thu, Nov 3, 2016 at 12:07 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Doug Evans <dje@google.com>
>> Date: Thu, 3 Nov 2016 11:30:39 -0700
>> Cc: gdb-patches <gdb-patches@sourceware.org>
>>
>> On Thu, Nov 3, 2016 at 11:21 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>>  > Date: Thu, 03 Nov 2016 17:46:28 +0000
>>  > From: Doug Evans <dje@google.com>
>>  >
>>  > +Return the type of a character in @var{lazy-string}.
>>
>>  Hmm... what is "type of a character" in this context?
>>
>>  I have no comments to the markup or the text.
>>
>>  Thanks.
>>
>> Consider char vs wchar_t.
>> e.g.,
>> #include <stddef.h>
>> char foo[] = "bar";
>> wchar_t wide_foo[] = L"bar";
>
> So maybe it would be more clear to say "the type of characters",
> plural?  And perhaps give an example or two of what types these could
> be?

Or how about "the type of an element in the string" ?


  reply	other threads:[~2016-11-03 23:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 17:46 Doug Evans
2016-11-03 18:21 ` Eli Zaretskii
2016-11-03 18:36   ` Doug Evans
     [not found]   ` <CADPb22QnnuHuG+sC=rg5HUJP2L_m1P_J7TTFLv0H-KDd6tON=A@mail.gmail.com>
2016-11-03 19:07     ` Eli Zaretskii
2016-11-03 23:55       ` Doug Evans [this message]
2016-11-04  7:31         ` Eli Zaretskii
2016-11-03 19:04 ` Doug Evans
2016-11-03 21:20   ` André Pönitz
2016-11-04  0:01   ` Doug Evans
2016-11-04 17:53     ` Doug Evans
2016-11-04 19:20       ` Phil Muldoon
2016-11-04 19:29         ` 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='CADPb22TETj2o19MZw2GYby1Swe=4RFeT2r1HvKbxfZz8Nv7euQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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