# HG changeset patch
# User Tassilo Philipp
# Date 1494713955 -7200
# Node ID 7cb8a0aaf638cd049a677ef3d6ddf8827c1ac2ff
# Parent  91db39538e78c35c88b67639bdb897e31cfaa1ce
- note about c99 (+ anon struct/union) requirements in doc

diff -r 91db39538e78 -r 7cb8a0aaf638 ToDo
--- a/ToDo	Sat May 13 23:02:17 2017 +0200
+++ b/ToDo	Sun May 14 00:19:15 2017 +0200
@@ -4,8 +4,6 @@
   prototype exist (e.g. just calling some pointer), without any declaration... even possible in C, as one has
   to cast to the function type? need to support?
 
-- Add doc note (and on website) on dyncall's c standard compatibility, which is c99 + anon struct extension
-
 - make sure all assembly files declare (or are built) by setting the noexecstack flag,
   compared to translating code with gcc, it's manual for the assembler; this depends on arch
   support (currently it's only done for x86/x64 ELF, but doesn't always work I think... e.g. openbsd 4.0, maybe too old?):
diff -r 91db39538e78 -r 7cb8a0aaf638 doc/manual/manual_overview.tex
--- a/doc/manual/manual_overview.tex	Sat May 13 23:02:17 2017 +0200
+++ b/doc/manual/manual_overview.tex	Sun May 14 00:19:15 2017 +0200
@@ -178,3 +178,10 @@
 \caption{Supported platforms}%
 \end{table}
 
+\subsection{Build Requirements}
+
+The library needs at least a c99 compiler with additional support for anonymous
+structs/unions (which were introduced officially in c11). Given that those are
+generally supported by pretty much all major c99 conforming compilers (as
+default extension), it should build fine with a c99 toolchain.
+
diff -r 91db39538e78 -r 7cb8a0aaf638 dyncall/dyncall.3
--- a/dyncall/dyncall.3	Sat May 13 23:02:17 2017 +0200
+++ b/dyncall/dyncall.3	Sun May 14 00:19:15 2017 +0200
@@ -187,6 +187,13 @@
 	r = dcCallDouble(vm, (DCpointer)&sqrt);
 	dcFree(vm);
 .Ed
+.Sh CONFORMING TO
+The dyncall library needs at least a c99 compiler with additional support for
+anonymous structs/unions (which were introduced officially in c11). Given that
+those are generally supported by pretty much all major c99 conforming compilers
+(as default extension), it should build fine with a c99 toolchain. Strictly
+speaking, dyncall conforms to c11, though.
+.Ed
 .Sh SEE ALSO
 .Xr dyncallback 3 ,
 .Xr dynload 3
diff -r 91db39538e78 -r 7cb8a0aaf638 dyncallback/dyncallback.3
--- a/dyncallback/dyncallback.3	Sat May 13 23:02:17 2017 +0200
+++ b/dyncallback/dyncallback.3	Sun May 14 00:19:15 2017 +0200
@@ -123,6 +123,13 @@
     (123, 23.f, 3, 1.82, 9909ll);
   dcbFreeCallback(cb);
 .Ed
+.Sh CONFORMING TO
+The dyncallback library needs at least a c99 compiler with additional support
+for anonymous structs/unions (which were introduced officially in c11). Given
+that those are generally supported by pretty much all major c99 conforming
+compilers (as default extension), it should build fine with a c99 toolchain.
+Strictly speaking, dyncall conforms to c11, though.
+.Ed
 .Sh SEE ALSO
 .Xr dyncall 3 ,
 .Xr dynload 3
diff -r 91db39538e78 -r 7cb8a0aaf638 dynload/dynload.3
--- a/dynload/dynload.3	Sat May 13 23:02:17 2017 +0200
+++ b/dynload/dynload.3	Sun May 14 00:19:15 2017 +0200
@@ -107,6 +107,9 @@
 and
 .Fn _fini
 symbols exported (rare, but possible).
+.Sh CONFORMING TO
+The dynload library conforms to c99.
+.Ed
 .Sh SEE ALSO
 .Xr dyncall 3 ,
 .Xr dyncallback 3