# HG changeset patch
# User cslag
# Date 1459004175 -3600
# Node ID 390380ef6362ae07c29ef4e9312a199637b55412
# Parent  079718588eb6849375b4ec0c37fc3347cc02542e
- general readme update

diff -r 079718588eb6 -r 390380ef6362 README.txt
--- 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