An alternative runtime for C11/C23 (mirror)
Go to file
bumbread 3f7c3de288 mb <-> c32 functions 2022-07-18 02:09:43 +11:00
inc fix compile issue 2022-07-16 04:41:38 +11:00
src mb <-> c32 functions 2022-07-18 02:09:43 +11:00
test unicode.h: encoding/decoding UTF-8/16 2022-07-02 18:51:48 +11:00
unicope@0b1530b6a5 bump unicope version 2022-07-16 03:10:29 +11:00
.gitignore I have no idea but something for linux 2022-06-28 23:57:14 +11:00
.gitmodules Use unicope as submodule like a true chad 2022-07-06 13:31:15 +11:00
Makefile build dependency using its build script 2022-07-16 04:44:15 +11:00
bake.cmd Use unicope as submodule like a true chad 2022-07-06 13:31:15 +11:00
bake_cc.cmd Use unicope as submodule like a true chad 2022-07-06 13:31:15 +11:00
build_cuik.cmd Use unicope as submodule like a true chad 2022-07-06 13:31:15 +11:00
readme Update readme 2022-06-26 15:39:15 +11:00
todo Complete tgmath.h 2022-06-28 12:35:26 +11:00

readme

ABOUT
  Ciabatta  -  An implementation of CRT for x86-64 windows and linux platforms.
The  goal  is  to  provide  a  platform-independent  CRT  with  the  purpose of
explicitly  defining  some  of platform-defined behaviours in order to simplify
the development and providing additional functionality to aid the developers in
writing cross-platform applications.

Note that Undefined Behaviour is impossible to define on a CRT level, since the
semantics  of the language can only be changed at the compiler level. Sometimes
the  compilers will replace CRT function calls with builtin functions, which is
meant  as  an optimization, e.g. replacing some forms of prinf() with puts() or
replacing  strlen with an x86 rep movsb instruction. Even if ciabatta does have
a  specific  behaviour  under  given  UB  conditions,  that  behaviour  is  not
guaranteed.

The goals:
  - Providing  API  for sockets, unicode processing (not just encodings), maybe
    the  support  for  common  image  and  data  file  formats and other useful
    non-standard functionality.
  - Making  it  easy  to  port  the library to a new platform, e.g. a custom OS
    kernel or a different processor architecture.
  - Defining  implementation-defined  behaviours  of  some of the functions and
    explicitly documenting them.
  - Make it reasonably fast compared to MSVCRT and GLIBC.

PLATFORM SUPPORT
  OS/Kernel:
  - Windows (64-bit)
  - TODO: Linux
  Processor Architecture
  - x86-64

USAGE
  (TODO)

CONTRIBUTING
  Pull requests are always welcome.


LICENCE

TBD, but probably i'll make it MIT or WTFPL :kekw: