input byte-limited versions of output functions #2756
Labels
C++
c++ wrappers
documentation
Improvements or additions to documentation
enhancement
New feature or request
python
python wrappers
Milestone
See #2754. @zhiayang and @neurocyte make a compelling case that the current
putnstr
family of functions aren't terribly useful, but something that limited the number of input bytes (similarly to allfoo
nbar
functions in the c library) might be.Looking at it, i'm honestly unsure why i ever went with these definitions.
I don't want to simply change the definitions of the functions, so we'd need new symbols (annoying, as the
putnstr
ought follow the c library). I'm inclined to then deprecate the existing functions (leaving them in through at least 4.0), but let's look over the current demo/etc code to see if they're being used. Take a look at growlight and omphalos, as well. Any current uses run a good chance of being buggy due to a confused understanding of how these functions work IMHO.What to call them?
I don't know if my main man @joseluis is still around, but we'd want rust wrappers (and C++, and Python). Probably not too difficult to put together based on what's already there.
The text was updated successfully, but these errors were encountered: