Comment by lelanthran
1 day ago
> This shows that "extremely portable" is actually marketing for "It supports a number of platforms. In my opinion, this number is big".
The number might just be zero - did anyone check if this compiles? I am trying to track down where the function `sp_mem_allocator_alloc_type` is defined (used in 3x places) but it doesn't appear in the GH search results.
I'm not going to clone and build this (too dangerous).
> I am trying to track down where the function `sp_mem_allocator_alloc_type` is defined
A quick glance at the source on github and here you go: https://github.com/tspader/sp/blob/e64697aa649907ce3357a7dd0...
`sp_mem_allocator_alloc_type ` is going through a couple of macro resolutions which ends up at `sp_mem_allocator_alloc`
> I'm not going to clone and build this (too dangerous).
Your computer won't explode just from downloading and compiling some C code, don't worry ;)
The github repo builds and the examples run just fine on macOS by just running `make` in the project directory, although with one warning:
It looks like I need to update my macOS machine! Thanks for the sanity, and thanks for reading.
Only if you want to move from MacOS Sequoia to Tahoe. Tahoe has the Liquid Glass stuff that people don't like as well as other UX changes that have been controversial.
Apple still do security updates on Sequoia.
I'm trying to sort out the whole mess of sp_ht / sp_str_ht_init / sp_str_split_c8 / sp_da_for / sp_da. sp_da_fuq? What is all this stuff?
> Your computer won't explode just from downloading and compiling some C code, don't worry ;)
This is the first time I ever saw anyone dismissing the risk of downloading and running stuff off the internet.
"Don't worry".
Compiling
3 replies →
Did you never install anything on your computing device? It's the same risk, or even worse if it was closed source software installed via an app store
> Your computer won't explode just from downloading and compiling some C code, don't worry ;)
I have no idea what's in the Makefile, and I'm not going to review it just so to try and figure out where a function is defined :-/
I found the function body in about 30 seconds by browsing the code on github via plain old text search. Is that also to dangerous? ;)
Use better tooling, then. Cscope is your friend.
> I'm not going to clone and build this (too dangerous).
Just create a disposable isolated environment, like VM or container, and do it inside? And, yes, does compile.
For C-based projects, use cscope. It found it pretty fast.