From 499ca6c243b05da176a2d4bd9a2317f0b28afc7f Mon Sep 17 00:00:00 2001 From: Alex AUVOLAT Date: Sat, 19 May 2012 11:45:49 +0200 Subject: Introducing FWIK, the userland C++ framework. Far from complete. --- doc/fwik.txt | 9 +++++++++ doc/vfs.txt | 6 +++++- 2 files changed, 14 insertions(+), 1 deletion(-) create mode 100644 doc/fwik.txt (limited to 'doc') diff --git a/doc/fwik.txt b/doc/fwik.txt new file mode 100644 index 0000000..d038b2a --- /dev/null +++ b/doc/fwik.txt @@ -0,0 +1,9 @@ +FWIK + +FWIK (is not an acronym) is a C++ library for userland applications, built +especially to run on the T/CE kernel. + +It includes : +- I/O (files, directories, terminals) +- Strings, vectors, sets, maps +- ... diff --git a/doc/vfs.txt b/doc/vfs.txt index 5a6a0b2..680df73 100644 --- a/doc/vfs.txt +++ b/doc/vfs.txt @@ -32,13 +32,17 @@ struct file_info { File open modes flags : - FM_READ open for reading - FM_WRITE open for writing -- FM_APPEND append data - FM_TRUNC truncate existing file - FM_CREATE create file if it doesn't exist - FM_DELETE delete the file - incompatible with everything else note : if mode contains neither FM_READ nor FM_WRITE, then the file will be created/truncated according to the flags given, but will not be actually oppenned, so the return value of open will be 0. +Important remark : +The kernel does NOT keep track of what your current position in the file is. And it's a bit hard, too, +because terminals behave differently than files, and so do directories, etc. So that's why there is no +FM_APPEND : when you open a file, you can do whatever you want. + Link modes : - LM_SYMLINK - LM_HARDLINK (don't count on that really being implemented) -- cgit v1.2.3