[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240906154626.GB2724612@port70.net>
Date: Fri, 6 Sep 2024 17:46:26 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: "Gardner, Ryan P" <ryan.p.gardner@...ing.com>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: Storing common macros and function stubs in libc-test
* Gardner, Ryan P <ryan.p.gardner@...ing.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.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
