[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f0aa778c8744d6fa08cda40e553ee4b@boeing.com>
Date: Fri, 6 Sep 2024 01:36:17 +0000
From: "Gardner, Ryan P" <ryan.p.gardner@...ing.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Storing common macros and function stubs in libc-test
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, ...).
Kind regards,
Ryan
Content of type "text/html" skipped
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.
