From 858cfd9e747871a4a84699d5a8f63d87be485fee Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 1 Jun 2004 13:58:57 +0000 Subject: add a couple thoughts so I remember them --- doc/TODO | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'doc') diff --git a/doc/TODO b/doc/TODO index 9be577a6..083c713c 100644 --- a/doc/TODO +++ b/doc/TODO @@ -115,3 +115,14 @@ since protocol probably modifies the API. But we could have it there as a safety net. +- STRING_OR_NIL is wrong, doesn't work in C++ etc. ; should not have done that. + Use empty string or special string values or separate functions/signals + or whatever instead. + +- For recursive types, one approach is that "structs" are done as parens, + so e.g. s(ii) is a string and struct { int; int; } etc. Type codes + then all have to be done as strings not single ints. + We could also put the type signature for the message body in a header field. + An "any" type has the type string included in the value. + + -- cgit