Just an idea: use the weakness property of functions about c-embed HOT 2 CLOSED

Thanks for the idea! I will have to take a look at this.

The reason why I use a compiler preprocessor directive (to re- #define eopen as fopen), is that it can be easily turned on and off during compile time with a flag. That means that you can use your local filesystem during development, which can change dynamically (without having to embed it first) and embed it quickly at deployment.

Additionally, it lets you use a local and an embedded filesystem simultaneously (in theory - although most use cases would probably use one or the other).

If I were to overwrite the functions with c-embed, then the local file system could not be used unless I removed the c-embed header entirely, which would be a code modification depending on whether you're developing or deploying; one of the main goals of this repo was to avoid this entirely.

from c-embed.

Yes I did not think about mixing local and embedded filesystem. I was only thinking about 100 % embedded filesystem.

from c-embed.