From: Michael Snyder <msnyder@vmware.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Shorten lines of >= 80 columns.
Date: Wed, 05 Jan 2011 21:38:00 -0000 [thread overview]
Message-ID: <4D24E4B9.40500@vmware.com> (raw)
In-Reply-To: <4D24B777.4030403@vmware.com>
Michael Snyder wrote:
> Pierre Muller wrote:
>>>> case LOC_CONST_BYTES:
>>>> - internal_error (__FILE__, __LINE__,
>>>> - _("gen_var_ref: LOC_CONST_BYTES symbols are not
>>>> supported"));
>>>> + internal_error (__FILE__, __LINE__, _("\
>>>> +gen_var_ref: LOC_CONST_BYTES symbols are not supported"));
>>>>
>>>> I think this kind of changes confuses cvs
>>>> for the 'cvs diff -u -p':
>>>> it might regard the new line
>>>> +gen_var_ref: LOC_CONST_BYTES symbols are not supported"));
>>>> as a new starting function line and
>>>> report a wrong function name...
>>>> Of course not really for your example here,
>>>> as the start of the line is
>>>> the name of the function itself...
>>>> But I remember having seen
>>>> wrong function name reported with 'cvs -u -p'
>>>> due to the use of '_("\'
>>>> construct which force starting next line without
>>>> spaces...
>>>>
>>>> Pierre Muller
>>>> GDB pascal language maintainer
>>> Hmmm... well, we already have tons of similar constructs in the tree.
>> Yes, I know, and it should of course not
>> retard your commit.
>
> No, I'm concerned about it. If I can see a "nice" solution, I will
> make changes.
>
>> I was just wondering if we could try to avoid
>> those construct in the future, but I am not sure there is a
>> simple solution...
>>
>> In general, I was wondering if we could use
>> ,_(
>> "gen_var_ref: LOC_CONST_BYTES symbols are not supported"));
>> instead of
>> ,_("\
>> gen_var_ref: LOC_CONST_BYTES symbols are not supported"));
>>
>> at least for case that are shorter than 80 - 5(2'"'+2')'+1';') chars?
>> But this might be against GNU coding style.
>
> The trouble with that is that emacs will not indent it that way.
Got it. I can split this up like this:
internal_error (__FILE__, __LINE__,
_("gen_var_ref: LOC_CONST_BYTES "
"symbols are not supported"));
Submission to follow after final regression test.
next prev parent reply other threads:[~2011-01-05 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 19:10 Michael Snyder
2011-01-04 19:19 ` Pierre Muller
2011-01-04 20:00 ` Michael Snyder
2011-01-05 9:02 ` Pierre Muller
2011-01-05 18:25 ` Michael Snyder
2011-01-05 21:38 ` Michael Snyder [this message]
2011-01-06 4:32 ` Joel Brobecker
2011-01-06 18:05 ` Michael Snyder
2011-01-04 19:27 ` Mark Kettenis
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=4D24E4B9.40500@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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