From 97d41f8b945158d35ce979e3354fe47a908178d3 Mon Sep 17 00:00:00 2001 From: Ray Date: Thu, 30 Apr 2020 20:13:22 +0200 Subject: [PATCH] Updated raylib libc dependency (markdown) --- raylib-libc-dependency.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/raylib-libc-dependency.md b/raylib-libc-dependency.md index 1b8b5e7..20b23c4 100644 --- a/raylib-libc-dependency.md +++ b/raylib-libc-dependency.md @@ -14,7 +14,7 @@ While working on raylib 3.0 I took some time to analyze that dependency in detai ### stdio.h -Note that file loading functionality is currently being centralized to `LoadFileData()`/`SaveFileData()`, most of the file access calls below will disappear soon, replaced by memory buffers parsing. +Note that file loading functionality is currently being centralized to `LoadFileData()`/`SaveFileData()`, most of the file access calls below will disappear soon, replaced by memory buffers parsing (Issue [#1232](https://github.com/raysan5/raylib/issues/1232). | module | libc function | raylib function | | :----: | --------------- | ----------------- | @@ -57,3 +57,5 @@ Note that file loading functionality is currently being centralized to `LoadFile | :----: | --------------- | ----------------- | | text | va\_list, va\_start(), vsprintf(), va\_end() | TextFormat() | | utils | va\_list, va\_start(), vsprintf(), va\_end() | TraceLog() | + +Considering the size of raylib, there is not much dependency on *libc*... that's an interesting consideration for embedded devices development where custom *libc* implementations could be used. \ No newline at end of file