From: Szabolcs Nagy <nsz@port70.net>
To: "Gardner, Ryan P" <ryan.p.gardner@boeing.com>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [musl] Storing common macros and function stubs in libc-test
Date: Fri, 6 Sep 2024 17:46:26 +0200 [thread overview]
Message-ID: <20240906154626.GB2724612@port70.net> (raw)
In-Reply-To: <5f0aa778c8744d6fa08cda40e553ee4b@boeing.com>
* Gardner, Ryan P <ryan.p.gardner@boeing.com> [2024-09-06 01:36:17 +0000]:
> Hello,
>
> I am currently writing some test cases to contribute to libc-test.
> In regards to reusing common macros and function stubs, where would
> be the most appropriate place to put these? Should these be added
> to `test.h`? Would a new `utils.h` header file be more appropriate?
> A new file would ensure no rework/unexpected redefines with already
> existing tests. Or should the macros needed for a given test be
> defined within that test file, even if many tests use the same
> macros. For example #define TEST(c, ...).
if the macro definition is relatively simple then keep it in the test
so users can more easily use the test outside the test system.
otherwise if you need a lot of shared macros then utils.h is fine.
prev parent reply other threads:[~2024-09-06 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 1:36 Gardner, Ryan P
2024-09-06 15:46 ` Szabolcs Nagy [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=20240906154626.GB2724612@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
--cc=ryan.p.gardner@boeing.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).