[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: interface generator

>Note that for certain languages, it would make sense to transform cord
>definitions into object classes, and cord messages into methods on
>those classes.

BTW, it would be nice if a future version of the mcp-cord package would
allow an extended mcp-cord-open that could pass parameters during the cord
#$#mcp-cord-open <auth key> _id: <id> _type: <type> [... optional <keyvals>
used  as parameters for the cord creation ...]
For example, those parameters could be the class constructor parameters.

>>I would also like to remain
>>as compatible as possible with any existing MOO MCP code, the state of
>>which I am not certain.

At the cost of a little overhead, couldn't the interface generator/RPC
system be just 'another package'?