Mercurial > pub > dyncall > dyncall
changeset 558:9eb5d92e5c5d
doc fix of confusing paragraph
author | Tassilo Philipp |
---|---|
date | Sat, 03 Sep 2022 16:37:22 +0200 |
parents | b36a738c8975 |
children | 52e87d4988e3 |
files | doc/manual/manual_overview.tex |
diffstat | 1 files changed, 7 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/manual/manual_overview.tex Sat Aug 20 21:04:15 2022 +0200 +++ b/doc/manual/manual_overview.tex Sat Sep 03 16:37:22 2022 +0200 @@ -148,14 +148,14 @@ The feature matrix below gives a brief overview of the currently supported platforms. Different colors are used, where a green cell indicates a supported -platform, with both, call and callback support, but lacking aggregate (struct, -union) support, yellow a platform that might work (but is untested) and red a -platform that is currently unsupported. Gray cells are combinations that don't -exist at the time of writing, or that are not taken into account.\\ +platform, with both, call and callback support, yellow a platform that might +work (but is untested) and red a platform that is currently unsupported. Gray +cells are combinations that don't exist at the time of writing, or that are not +taken into account.\\ Light green cells mark complete feature support, including passing aggregates -(struct, union) by value. Dark green means basic support but lacking features -(e.g. dyncall support, but not dyncallback). Please note that a green cell -(even a light-green one) doesn't imply that all existing calling +(struct, union) by value. Dark green means basic support but lacking lesser +used features (e.g. no aggregate-by-value support). Please note that a green +cell (even a light-green one) doesn't imply that all existing calling conventions/features/build tools are supported for that platform (but the most important). % @@@ The rightmost column gives a brief info about calling convention support or other notes.