aboutsummaryrefslogtreecommitdiff
path: root/devel/dyncall
diff options
context:
space:
mode:
authorJimmy Olgeni <olgeni@FreeBSD.org>2008-06-01 09:42:37 +0000
committerJimmy Olgeni <olgeni@FreeBSD.org>2008-06-01 09:42:37 +0000
commita249020977a2394eb6f6b41a59e49167878d5f8d (patch)
tree5d607d247327f1beb39661a2ddfb9b78f6f2cd45 /devel/dyncall
parent75ef30fdb03f8f8cf0ccf2ea00b086adac621054 (diff)
downloadports-a249020977a2394eb6f6b41a59e49167878d5f8d.tar.gz
ports-a249020977a2394eb6f6b41a59e49167878d5f8d.zip
Notes
Diffstat (limited to 'devel/dyncall')
-rw-r--r--devel/dyncall/pkg-descr2
1 files changed, 1 insertions, 1 deletions
diff --git a/devel/dyncall/pkg-descr b/devel/dyncall/pkg-descr
index 778bf94c19fa..4a449301da30 100644
--- a/devel/dyncall/pkg-descr
+++ b/devel/dyncall/pkg-descr
@@ -1,7 +1,7 @@
The dyncall library encapsulates architecture-, OS- and compiler-specific
function call semantics in a virtual "bind parameters from left to right
and then call" interface allowing programmers to call C functions in a
-completely dynamic manner. In other workds, instead of calling a function
+completely dynamic manner. In other words, instead of calling a function
directly, the dyncall library provides a mechanism to push the function
parameters manually and to issue the call afterwards.
This means, that a program can determine at runtime what function to