Night-walker

Short answer: bind you struct/class to Dao using the provided C API. Consult modules on how to do that. The API is not documented, but it's mostly self-explaining, and you...

CData is basically a wrapped (C-defined) type/class. In order to use your class in Dao you need to wrap it, registering it as Dao type. It involves defining a `DaoTypeBase`...

My feedback will likely be very long, so I'll split it in parts. Here is chapter one -- borrowing. > borrows from > C++ (object-orientation, syntax) I'd better omit this...

Chapter two -- goals. > classification in the languages universe depicted using scales Might be somewhat redundant unless the audience is deeply academic. I'd focus on hot topics: - growing...

> daopkg (neat package manager for modules) > It is far from usable, so it is better not to mention it. A remark: I stopped working on it because I...

Chapter three -- architecture. > built-in types (lowercase) have no or very few methods That is not a goal or design principle by itself. It doesn't mean much, so I...

Summary. There is a lot of insignificant things which don't really need to be mentioned. I would concentrate on making a solid and clear impression about the language as the...

> Well, then we would need to enhance Dao parser to be able to work with unbound symbols (there are cases which need forward declaration - e.g. recursion). This would...

OK, I see your point. To address the clarity issue, it is indeed sufficient to restrict the use of external method definitions to the file where the corresponding class resides....

That's so confusing that it arguably brings more harm then help: ``` ruby (dao) routine cast(x: list){ ..... io.writeln((list)x) ..... } = none (dao) cast({}) { } = none (dao)...