Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Luis Machado <lgustavo@codesourcery.com>,
	GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] D: Fix crash when expression debugging
Date: Sun, 08 Jan 2017 10:38:00 -0000	[thread overview]
Message-ID: <CABOHX+eyxxhjHZgXxio0++wxSQ3qzA6P8yBmE-qpf68bbJEpzg@mail.gmail.com> (raw)
In-Reply-To: <a4474fbb312d66156ffaaa0085d9e8ef@polymtl.ca>

On 5 January 2017 at 17:13, Simon Marchi <simon.marchi@polymtl.ca> wrote:
>>>>>>> +if { [skip_d_tests] } { continue }
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> We should output a message:
>>>>>>
>>>>>> untested "skipping d language tests"
>>>>>>
>>>>>> It may be more reasonable to just return instead of continuing? The
>>>>>> effect
>>>>>> will probably be the same, but it is a bit confusing to read
>>>>>> "continue"
>>>>>> without a visible loop.
>>>>>>
>>>>>
>>>>> I did a quick grep, and it seems like everyone is skippingtests in
>>>>> this way except for gdb.ada and gdb.btrace which are doing { return -1
>>>>> }
>>>>>
>>>>>
>>>>
>>>> That's a bit of a stretch. Take, for example, a few of the examples in
>>>> gdb.base. You will see a number of them returning.
>>>>
>>>> The problem here is inheriting past confusing practices when we use some
>>>> existing files to create new ones, which is not your fault really. I'm
>>>> guilty myself. :-)
>>>>
>>>
>>> Yes indeed. I wasn't disagreeing, just questioning the two competing
>>> ways of returning.
>>>
>>> I will update to use return and push this in then if there's no
>>> disagreement. :-)
>>>
>>
>> Hopefully someone will chime in for a second opinion. :-)
>
>
> +1 :)


FYI, committed patched as-is except for the following adjustment as discussed:

-if { [skip_d_tests] } { continue }
+if { [skip_d_tests] } { return -1 }


Thanks for the review.


  reply	other threads:[~2017-01-08 10:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  0:02 Iain Buclaw
2017-01-04 16:08 ` Luis Machado
2017-01-04 19:38   ` Iain Buclaw
2017-01-04 19:48     ` Luis Machado
2017-01-04 20:38       ` Iain Buclaw
2017-01-04 20:54         ` Luis Machado
2017-01-05 16:13           ` Simon Marchi
2017-01-08 10:38             ` Iain Buclaw [this message]
2017-01-05 17:31         ` Yao Qi

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=CABOHX+eyxxhjHZgXxio0++wxSQ3qzA6P8yBmE-qpf68bbJEpzg@mail.gmail.com \
    --to=ibuclaw@gdcproject.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=simon.marchi@polymtl.ca \
    /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