mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Gardner, Ryan P" <ryan.p.gardner@boeing.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: [musl] Storing common macros and function stubs in libc-test
Date: Fri, 6 Sep 2024 01:36:17 +0000	[thread overview]
Message-ID: <5f0aa778c8744d6fa08cda40e553ee4b@boeing.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2646 bytes --]

             reply	other threads:[~2024-09-06  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  1:36 Gardner, Ryan P [this message]
2024-09-06 15:46 ` Szabolcs Nagy

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=5f0aa778c8744d6fa08cda40e553ee4b@boeing.com \
    --to=ryan.p.gardner@boeing.com \
    --cc=musl@lists.openwall.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).