News for hackers. Stuff that matters.
Re:Minimalist C Libraries by ajross on Sunday June 10, 2018 @02:26PM (#17279447)
> In your custom kernel project, your custom allocator() can return a buffer from a memory pool you handle yourself.

We're done. "It's OK, you can just write your own heap-like API!" is just not remotely responsive to the kind of problems I'm talking about, and that you think it is is sorely tempting me to put more words in your mouth.

If you don't think these libraries are useful, that's fine. Don't use them. Don't presume to understand the application realm before you've worked in it.

Re:Minimalist C Libraries by lyricaljoke on Sunday June 10, 2018 @03:12PM (#17279693)
I also work in the resource-constrained / embedded native space and have had to work within the kinds of constraints you're describing. I think you're severely misunderstanding what the comment you're responding to is proposing.
Re:Minimalist C Libraries by ajross on Sunday June 10, 2018 @03:25PM (#17279758)
Then you'll have to point me to a real world example of an API that works like that, because this is balderdash (seriously? Implement malloc and free on top of a stack-based memory pool just to decode a buffer?) to my eyes.