nanoprintf
printf
nanoprintf | printf | |
---|---|---|
5 | 16 | |
577 | 2,345 | |
- | - | |
5.5 | 0.0 | |
12 days ago | about 1 year ago | |
C++ | C | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nanoprintf
-
nanoprintf VS callback_printf - a user suggested alternative
2 projects | 16 Aug 2023
- Nanoprintf – The smallest public printf implementation for its feature set
-
DOOM! on the #emfcamp TiDAL badge
It turns out that DOOM expects a little more POSIX compliance from it's C library than Micropython provides, in particular the printf implementation is lacking many features. The good part is that because I'm building an entirely separate binary application, I can use someone elses printf, and finally, after a lot of pain, it runs!
-
Actual Challenges Faced In Software
You might be interested in this or similar: https://github.com/charlesnicholson/nanoprintf
- Nanoprintf v0.1.0 Released, drop-in [v]snprintf
printf
- Nanoprintf – The smallest public printf implementation for its feature set
- Thank you senpai!
-
Sprintf without C library
https://github.com/mpaland/printf i think this would work
-
Nolibc: A minimal C-library replacement shipped with the kernel
Seems unlikely. My spot check of the the two vfprintf implementations shows no flow from one to the other, and shows that part of the Cosmopolitan code has an older lineage than nolibc.
The nolibc source has many reference to copyright held by "Willy Tarreau", under LGPL-2.1 OR MIT license, with a copyright date starting in 2017.
The string "Tarreau" does not exist in the Cosmopolitan library, so that's a strong negative there. Let's look closer.
The file organization is quite different. And so is the implementation. So that's another negative.
Compare the vfprintf in nolibc at https://elixir.bootlin.com/linux/v6.2-rc4/source/tools/inclu... (a 'minimal vfprintf()') with the one in cosmopolitan starting at https://github.com/jart/cosmopolitan/blob/master/libc/stdio/....
Right away we can see nolibc places many functions in the same file while Cosmopolitan uses a one-function-per-filename organization.
Cosmopolitan's fvprintf locks the file (which nolibc doesn't need to do) then calls vfprintf_unlocked which calls __fmt at https://github.com/jart/cosmopolitan/blob/master/libc/fmt/fm... , which is the actual implementation. It look very different from NOLIBC's.
Okay, so perhaps that's they way now but not at the beginning?
We can also go back to Cosmopolitan's original implementation and see how vfprintf goes through https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... to call "palandprintf", which https://github.com/jart/cosmopolitan/blob/c91b3c50068224929c... says is copyright "Marco Paland" from 2014-2019.
That's a few years older than the start of nolibc, available from https://github.com/mpaland/printf , and part of https://github.com/embeddedartistry/libc , a "libc targeted for embedded systems usage".
Thus, multiple factors seem to agree that nolibc code is not used in the Cosmopolitan library.
-
How should I go about implementing printf-like function in my library?
I wrap this C implementation in a C++ Logger class and use it to "print" into a simple buffer. Then the static buffer is periodically unrolled into a transport layer using a static Logger::transmit() function in my BSP. I'm working with very little flash, so the linked implementation is essential.
-
A 1 hour interview for an embedded engineering position
There are many good and tiny printf's fir embedded on GitHub. https://github.com/mpaland/printf eg Better than the bsd printf mostly
- is it safe to use printf()?
-
Sprintf on STM32?
I'm sure sprintf itself is working in their library, so try to find other issues first, BUT, as a last resort you can try another lib: https://github.com/mpaland/printf/
-
Would you merge with them?
looked at that account, found this one too
What are some alternatives?
defmt - Efficient, deferred formatting for logging on embedded systems
trice - 🟢 super fast 🚀 and tiny 🐥 embedded device 𝘾 printf-like trace ✍ code, works also inside ⚡ interrupts ⚡ and real-time PC 💻 logging (trace ID visualization 👀)
printf - Tiny, fast(ish), self-contained, fully loaded printf, sprinf etc. implementation; particularly useful in embedded systems.
z88dk - The development kit for over a hundred z80 family machines - c compiler, assembler, linker, libraries.
doomgeneric - Easily portable doom
anal-encryption-2.0
lfbb - A Lock Free Bipartite Buffer Library written in standard C11
elk - A low footprint JavaScript engine for embedded systems
esp-idf - Espressif IoT Development Framework. Official development framework for Espressif SoCs.
modorganizer - Mod manager for various PC games. Discord Server: https://discord.gg/ewUVAqyrQX if you would like to be more involved
callback_printf - callback_printf allows the implementation of portable sprintf, snprintf, vsprintf and vsnprintf like output functions. The code includes wrappers for those functions. It supports all formats of the C 11 standard. wchar_t arguments and strings are printed as UTF-8. It's pretty fast, threadsafe and has no dependencies to other libraries.
vformat - A Python str.format() like formatter, based on Text.Printf