From: Pedro Alves <palves@redhat.com>
To: Manish Goregaokar <manish@mozilla.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Use strtok_r instead of strsep in rust_get_disr_info
Date: Wed, 29 Jun 2016 10:44:00 -0000 [thread overview]
Message-ID: <d7f5a723-662a-04ef-1147-599ec4367852@redhat.com> (raw)
In-Reply-To: <CAFOnWkkFv0p8sZk71xDptmVH74cQUCyfL-AKP5iBY0D02XB8PA@mail.gmail.com>
On 06/29/2016 11:38 AM, Manish Goregaokar wrote:
> strsep moves the pointer to the end of the string. We want to ensure
> the early break happens, since we need token to contain the name of
> the variant at this stage.
>
> strtok doesn't do this. However, strtok does make it NULL, which we
> don't want either. I added a check for it in my most recent email,
> tests still pass.
Right, that one is OK. Please push.
Thanks,
Pedro Alves
prev parent reply other threads:[~2016-06-29 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 10:14 Manish Goregaokar
2016-06-29 10:26 ` Pedro Alves
2016-06-29 10:32 ` Manish Goregaokar
2016-06-29 10:35 ` Manish Goregaokar
2016-06-29 10:36 ` Pedro Alves
2016-06-29 10:39 ` Manish Goregaokar
2016-06-29 10:44 ` Pedro Alves [this message]
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=d7f5a723-662a-04ef-1147-599ec4367852@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=manish@mozilla.com \
--cc=tom@tromey.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