Mercurial > pub > dyncall > bindings
changeset 13:390380ef6362
- general readme update
author | cslag |
---|---|
date | Sat, 26 Mar 2016 15:56:15 +0100 |
parents | 079718588eb6 |
children | 7752fcb107e7 |
files | README.txt |
diffstat | 1 files changed, 5 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/README.txt Sat Mar 26 15:55:50 2016 +0100 +++ b/README.txt Sat Mar 26 15:56:15 2016 +0100 @@ -23,14 +23,14 @@ - Without objects: - Wrap dyncall as close as direct + Wrap dyncall as close as possible, exposing function by function - - Statically typed (and no direct way wrap types in a generic way and or RTTI): + - Statically typed (and no reflection/RTTI): Expose all dcArg, etc. calls Expose formatted call ('...') if possible, but as ArgF (instead of CallF), b/c return type is statically typed - - with RTTI: + - with reflection/RTTI: Write a single call function and let users pass arguments, directly - if needed for type-conversion, this should be done via call signature @@ -39,7 +39,7 @@ * Functional: - @@@ ToDo + ... nothing really different from imparative guidelines above? @@ -47,7 +47,7 @@ - Namespaces/modules/packages - Use and name dyncall or dc (@@@ choose one) + Use and name dyncall or dc (prefer former) Use casing depending on language requirements (e.g. 'Dyncall' for ruby as modules are const) - Function overloading or default arguments