seperate the src layout into headers

[rurban]

seperate the src layout into headers

[jeremyhannon]

when you say "seperate the src layout into headers", would there be one .h for every .c afterwards? This would help since we use Unity/Ceedling for unit testing and Ceedling makes some file structure assumptions. (btw I'd be ok with rolling all string functions into a single safe_str_lib.c file instead of one-function-per-header)

[rurban]

done with 480d59c

the headers stay of course the same. we will not change the API.
it's only the internal src layout.

one single file is highly unusual for a libc. we rather have single files into an archive.
with a shared lib -flto is recommended. with a static lib not needed.
if you cannot use -shared -flto (old linker, old compiler) then a cat into a single src file is ok.

[rurban]

I didn't really read your request, sorry. One h per c makes sense in your case. But for safeclib it would be massive overkill to include all single h files. Do the 2 new splits unsafe and extensions help?

[jeremyhannon]

ok, I understand your file structure preference.

Yes, separating the unsafe vs extensions seems wise. In our structure we've separated what is in the C11AnnexK standard vs other related functions we've added (particularly, truncating versions since the C11AnnexK returns an empty string if the destination is too small). That way the file structure makes clear what is from the standard and what deviates.