Collections-C, generic data structures for C
1–10 of 63 posts
Re: Collections-C, generic data structures for C
#2It looks like all collections store void pointers. I don't see any abstractions to help with pointer lifetimes, which remains the main problem I encounter when trying to write large programs in C that dynamically allocate memory.
Re: Collections-C, generic data structures for C
#3Would be nice to have parallel structures like "Intel threading building blocks" provides.
https://en.m.wikipedia.org/wiki/Threading_Building_Blocks
I recommend this book to understand such structures:
https://www.goodreads.com/book/show/14788830-structured-para...
Re: Collections-C, generic data structures for C
#4Has this library been stress tested? I am interested in using this library for a spaceflight application, but reliability is paramount in our situation.
Re: Collections-C, generic data structures for C
#5I try and plug http://concurrencykit.org/ whenever I see someone looking for something like this. It's built around providing portable atomic intrinsics for parallel code, but the data structures are also very well done and work just as nicely for single threaded code.
Re: Collections-C, generic data structures for C
#6Has this library been stress tested? I am interested in using this library for a spaceflight application, but reliability is paramount in our situation.
I stopped looking when I saw it doesn't check for malloc failure. I am going to say space flight is a no-go.
Re: Collections-C, generic data structures for C
#7It looks like all collections store void pointers. I don't see any abstractions to help with pointer lifetimes, which remains the main problem I encounter when trying to write large programs in C that dynamically allocate memory.
Start using arenas wherever you can. Makes memory management in C programs substantially simpler.
Re: Collections-C, generic data structures for C
#8Has this library been stress tested? I am interested in using this library for a spaceflight application, but reliability is paramount in our situation.
I stopped looking when I saw it doesn't check for malloc failure. I am going to say space flight is a no-go.
Some of the functions do check for malloc failure and others don't. It's on github--Have you submitted a pull request? Wow--guess the idea of sending a patch to an open source project is now controversial.
Re: Collections-C, generic data structures for C
#9klib [1] is another good one I recently came across. In fact, I'll just leave this great curated list of free software libraries right here:
Re: Collections-C, generic data structures for C
#10It looks like all collections store void pointers. I don't see any abstractions to help with pointer lifetimes, which remains the main problem I encounter when trying to write large programs in C that dynamically allocate memory.
It looks like all collections store void pointers
Does that mean that if you're running as 32bit and want to store a number larger than that (a double or int64_t or so) or a POD that all of these have to be allocated seperately?