Skip to content

Draft: A simple, conservative approach to handling #203 #207

Open
eyalroz wants to merge 2 commits intodevelopfrom
cmake-option-for-bug-203
Open

Draft: A simple, conservative approach to handling #203 #207
eyalroz wants to merge 2 commits intodevelopfrom
cmake-option-for-bug-203

Conversation

@eyalroz
Copy link
Owner

@eyalroz eyalroz commented Nov 23, 2025

This PR is one of several possible approach to catering to the request in #203 : Allowing use of the library for its non-putchar-dependent functions, without having to provide putchar_().

@eyalroz
Copy link
Owner Author

eyalroz commented Nov 23, 2025

An alternative - and more radical - approach constitutes PR #206 .

@eyalroz eyalroz force-pushed the cmake-option-for-bug-203 branch 4 times, most recently from 04d6bf7 to 38b31a8 Compare November 28, 2025 21:32
@eyalroz eyalroz force-pushed the cmake-option-for-bug-203 branch from 38b31a8 to 0ab9289 Compare December 6, 2025 10:04
…VIDE_PLAIN_PRINTF` (which gets a `PRINTF_` prefix in the source files). This controls whether or not we expose, and define, the functions `putchar_()`, `printf()` and `vprintf()`.
@eyalroz eyalroz force-pushed the cmake-option-for-bug-203 branch from 0ab9289 to e1dbaef Compare December 6, 2025 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant