From: Jason Duerstock <jason.duerstock@gmail.com>
To: binutils@sourceware.org
Subject: Re: ld error message %C format
Date: Thu, 19 May 2011 00:10:00 -0000 [thread overview]
Message-ID: <BANLkTim=FodMF3B054fC-Yaiiu5t3o7G1A@mail.gmail.com> (raw)
In-Reply-To: <20110518233336.GR20800@bubble.grove.modra.org>
Hadn't seen that one before. Thank you for the explanation.
Jason
On Wed, May 18, 2011 at 7:33 PM, Alan Modra <amodra@gmail.com> wrote:
> On Wed, May 18, 2011 at 12:03:42PM -0400, Jason Duerstock wrote:
>> >+ fprintf (fp, "%u%s", linenumber, ":" + done);
>>
>> Isn't this a C++ism? Shouldn't it be:
>
> No, just an old C trick. ":"+done is either ":" or "".
>
> --
> Alan Modra
> Australia Development Lab, IBM
>
next prev parent reply other threads:[~2011-05-19 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:48 Alan Modra
2011-05-18 15:51 ` H.J. Lu
2011-05-18 16:04 ` Jason Duerstock
2011-05-18 16:19 ` Andreas Schwab
2011-05-18 23:33 ` Alan Modra
2011-05-19 0:10 ` Jason Duerstock [this message]
2011-05-18 23:59 ` Ian Lance Taylor
2011-05-20 0:00 ` Alan Modra
2011-05-20 0:24 ` Ian Lance Taylor
2011-05-23 6:13 ` Alan Modra
2011-05-24 1:24 ` Ian Lance Taylor
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='BANLkTim=FodMF3B054fC-Yaiiu5t3o7G1A@mail.gmail.com' \
--to=jason.duerstock@gmail.com \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).