From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite/ada] Put testcase code in own directory
Date: Thu, 20 Jan 2005 17:18:00 -0000 [thread overview]
Message-ID: <41EEE817.4080908@gnu.org> (raw)
In-Reply-To: <20041108211630.GD649@gnat.com>
Joel Brobecker wrote:
> Hello,
>
> This implements something I have been thinking about doing for
> a little while. The idea is have the code for each testcase be
> in its own subdirectory. For instance, this change moves the code
> for null_record.exp to the null_record/ subdir.
>
> The reason for this is to avoid name clashes. It is much more common
> in Ada to split the code between several compilation units. The model
> used in C where you usually have one .c file per testcase doesn't
> apply well to Ada.
>
> The framework I'm trying to implement is that we would have one
> .exp file named <testcase>.exp, and have the sources located in
> subdir <testcase>/.
(put on head developer hat)
Yes, ok. And going forward as the testsuite expands to include more
complex multi-file cases this is only going to become more common.
Andrew
prev parent reply other threads:[~2005-01-20 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 21:16 Joel Brobecker
2004-11-11 16:43 ` Andrew Cagney
2004-12-01 3:20 ` Joel Brobecker
2004-12-01 4:54 ` Daniel Jacobowitz
2005-01-20 17:18 ` Andrew Cagney [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=41EEE817.4080908@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.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