Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make language setting tests more robust
Date: Thu, 02 Feb 2017 01:24:00 -0000	[thread overview]
Message-ID: <c104f454574b6e0c82c5d4c611d16cf9@polymtl.ca> (raw)
In-Reply-To: <58925832.8050306@redhat.com>

On 2017-02-01 16:50, Keith Seitz wrote:
> Regarding gdb_test_no_output et al, this grokking of args needs to be
> banished from the test suite. It adds unnecessary complexity. I would
> encourage maintainers to request revision when such a thing is proposed
> for the test suite.

Ok, good to know I'm not the only one :).  When I encounter procs that 
use this pattern, I have to either:

A. Pray that the documentation is still up to date
B. Read the code to decode what's being used where

Both are not very fun.


  parent reply	other threads:[~2017-02-02  1:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 15:17 Luis Machado
2017-02-01 18:38 ` Simon Marchi
2017-02-01 19:22   ` Luis Machado
2017-02-01 19:25     ` Simon Marchi
2017-02-01 21:50   ` Keith Seitz
2017-02-01 23:29     ` Luis Machado
2017-02-02  1:24     ` Simon Marchi [this message]
2017-02-01 20:21 ` [PATCH,v2] " Luis Machado
2017-02-02  1:33   ` Simon Marchi
2017-02-03  0:37   ` Pedro Alves
2017-02-06 14:54     ` Luis Machado
2017-02-06 15:09       ` Luis Machado
2017-02-06 16:51       ` Pedro Alves
2017-02-06 18:04         ` Luis Machado
2017-02-06 18:08           ` Pedro Alves
2017-02-06 18:22             ` Luis Machado
2017-02-06 18:24               ` Pedro Alves
2017-02-06 19:56                 ` Luis Machado

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=c104f454574b6e0c82c5d4c611d16cf9@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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