Keeps track of the API implementation progress. [](https://github.com/ngagesdk/Pico-8/actions/workflows/api-tests.yml) In case you want to help: - Avoid floating-point arithmetic. - Implement unit tests: [tests](https://github.com/ngagesdk/Pico-8/tree/main/tests), [coverage](https://github.com/ngagesdk/open8/issues/30) - Implement API functions, grouped by category and in alphabetical order, 4 spaces, no tabs: [api.c](https://github.com/ngagesdk/Pico-8/blob/main/src/api.c) - Ideally, the functions should provide identical values to the corresponding Pico-8 functions. Use the [Education Edition](https://www.pico-8-edu.com/) and the [Manual](https://www.lexaloffle.com/dl/docs/pico-8_manual.html) for reference. - Reference the issue number in your commit message: #5, #6, etc. - Keep branches at a [minumum](https://dev.to/jobinrjohnson/branchless-programming-does-it-really-matter-20j4). - Write your code in C99 or ANSI C. - Use ANSI C for all changes within z8lua.
Keeps track of the API implementation progress.
In case you want to help:
Use the Education Edition and the Manual for reference.