aboutsummaryrefslogtreecommitdiffstats
path: root/doc/info/chap
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2015-10-12 03:21:05 +0200
committerMattias Andrée <maandree@operamail.com>2015-10-12 03:21:05 +0200
commit80e5ebff1126f523b4ee6d00b7494c1a559bbaa0 (patch)
tree2fdcb7edd802009eda727e854df9549ffe6c535c /doc/info/chap
parentderp (diff)
downloadslibc-80e5ebff1126f523b4ee6d00b7494c1a559bbaa0.tar.gz
slibc-80e5ebff1126f523b4ee6d00b7494c1a559bbaa0.tar.bz2
slibc-80e5ebff1126f523b4ee6d00b7494c1a559bbaa0.tar.xz
info: intro
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'doc/info/chap')
-rw-r--r--doc/info/chap/introduction.texinfo42
1 files changed, 42 insertions, 0 deletions
diff --git a/doc/info/chap/introduction.texinfo b/doc/info/chap/introduction.texinfo
new file mode 100644
index 0000000..e846bda
--- /dev/null
+++ b/doc/info/chap/introduction.texinfo
@@ -0,0 +1,42 @@
+@node Introduction
+@chapter Introduction
+
+@cpindex Hosted environment
+@cpindex Unhosted environment
+The C programming language does not provide
+an built-in functions or constant values.
+It only, provides a few basic numerical
+data types. In fact, it does not even call
+the function @code{main}. All of these
+facilities are provided by the C standard
+library. A C environment with a C standard
+library is called a hosted environment; one
+without it is called an unhosted environment.
+Almost all software written in C are written
+in hosted C. There are practically only two
+types of software not written in an unhosted
+environment, the C standard library (commonly
+called @command{libc}) implementations
+themself, and operating system kernels and
+programs started before it.
+
+The Stockholm C Standard Library, or simply
+@command{slibc}, described in this document,
+is an implementaton of a C standard library for
+@sc{POSIX} systems. It is aimed at supporting
+@sc{C99} and newer dialects of @sc{ISO}@tie{}C,
+and no other programming languages. @command{slibc}
+is not aimed to replace an existing @command{libc}
+implementation or suiting a particular niche.
+Rather, @command{slibc} is intended as a learning
+experiences for its developer. It does however,
+add extensions (features) that are not defined
+by the standards it covers or even existing
+@command{libc} implementations.
+
+@command{slibc}'s header files document all
+features it implements. This manual is intended
+as a more extensive documentation. It is written
+with the assumption that you are familiar with
+the C programming language.
+