The user should be able to provide own implementations for both the Casio syscalls and the syscalls like read(), write() etc. Therefore, these functions should be defined explicitly weak using the weak attribute: __attribute__((weak)).
At a later stage of development, gint might override the syscalls with own (more sophisticated) versions.
The user should be able to provide own implementations for both the Casio syscalls and the syscalls like `read()`, `write()` etc. Therefore, these functions should be defined explicitly weak using the weak attribute: `__attribute__((weak))`.
At a later stage of development, gint might override the syscalls with own (more sophisticated) versions.
The user should be able to provide own implementations for both the Casio syscalls and the syscalls like
read(),write()etc. Therefore, these functions should be defined explicitly weak using the weak attribute:__attribute__((weak)).At a later stage of development, gint might override the syscalls with own (more sophisticated) versions.