On Tue, Sep 10, 2019 at 06:48:17PM +0200, Mattias Andrée wrote: > What is the point of doing your own mini-libc within the > program? Aren't you just making it less portable and > adding more code to read?
More code to read? Have you read the code of a standard libc? Not to mention the SDK deps? Moreover, this "mini-lib", as you said it, is actually compiled as 1 code unit with the application code (on a pi3 for the aarch64 port in a few secs, max optimization, lol). Hardware portability code is really thin, and linux devs are smoothing that out (it's a WIP). I personally use it on x86_64 (my station) and aarch64 (pi3). Your question feels a bit like the following one : what's the point of suckless? In the end, if this does not fit your definition of suckless, don't bother and just look away, don't be offended, I do not expect less. Btw, I have also the receiving part but the code is quite older: https://rocketgit.com/user/sylware/lnanosmtp I just did a bit of refactoring for the "1 compilation unit" suff and some updating (I personally use it on aarch64). As I did explain, gogol did a fine job at pushing me coding all that. -- Sylvain
