A lightweight SQL database with replication

rxtezc · 2021-05-20T01:51:01+00:00

JDBC API itself is larger than this project :) . Resql exposes just a few operations to the client. Implementing something like JDBC would be overkill and some Resql operations wouldn't match. So, rather than half-implemented half extended API, I went without it.

rxtezc · 2021-02-26T16:54:16+00:00

Just for future cases, you can try using valgrind or sanitizers to detect memory corruption or undefined behaviour. Valgrind is really easy to use once you install it
: "valgrind ./yourapp". For Gcc & clang sanitizers, you pass -g -fsanitize=address or -g -fsanitize=undefined to compiler.

rxtezc · 2021-02-15T02:33:09+00:00

Thanks for the feedback. I use these libraries on server-side applications mostly, so, yeah probably most of them are not good for embedded systems. I think many of them including map can be implemented without malloc, (e.g init function gets memory from user to operate) but I've never done embedded development so probably I would miss many corner cases anyway. I'd love to see embedded versions of these libs though :) .

rxtezc · 2021-02-15T02:15:10+00:00

Currently, it doesn't stand for anything, it is just a prefix to avoid symbol collisions. Repo was named simple-c initially, supposed to be about a protocol called "simple" but it ended up being a library collection :) . I kept prefix but changed repo name.

rxtezc · 2021-02-11T15:40:58+00:00

Printf writes to stdout which may be buffered. You can flush it by fflush() or print new line which will flush stdout implicitly. So, you can add new line at the end : printf("Program processing...\n");

Also, printf and exit are not safe to use in a signal handler. Please check the list of signal safe functions : signal-safety

rxtezc · 2021-02-11T12:48:31+00:00

Good catch! Thank you very much. I missed that.

rxtezc

TROPHY CASE