--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README.txt	Thu Mar 19 22:26:28 2015 +0100
@@ -0,0 +1,56 @@
+This document intends to layout a style to follow for language bindings,
+depending on the nature of the language.
+
+
+Naming
+------
+
+If possible and no name clashes exist with other bindings, use the language's
+shortest name or file suffix and append 'dc' or 'dyncall'. E.g.:
+  Ruby: rbdc
+  Go:   godc
+  ...
+
+
+Code style
+----------
+
+* Imperative:
+
+  - Object oriented or prototype:
+
+      Create 2 objects, one as a handle to each external library (e.g. extlib), one as a handle to a callvm
+
+  - Without objects:
+
+      Wrap dyncall as close as direct
+
+  - Statically typed (and no direct way wrap types in a generic way and or 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:
+
+      Write a single call function and let users pass arguments, directly - if needed for type-conversion, this
+      should be done via call signature
+
+
+
+* Functional:
+
+  @@@ ToDo
+
+
+
+* Other language features
+
+ - Namespaces/modules/packages
+
+     Use and name dyncall or dc (@@@ choose one)
+     Use casing depending on language requirements (e.g. 'Dyncall' for ruby as modules are const)
+
+ - Function overloading or default arguments
+
+     Use if available to define things like CallVM stack size; use independently named functions, otherwise
+