On Wed, Mar 14, 2007 at 08:01:47AM -0700, Ken Taylor wrote: > Ah, I sort of remember a post about that... but I thought it was simply for > cross-language code generation. But if it's meant to also include > human-readable documentation, and information for vobject structure > validation, then that would be very sweet :)
Right, the original motivating factor was to have an interface language that will make it easy to define cross-network and cross-language calls. That goal has expanded to include most other vobject aspects including children, embedded properties, namespaces, inheritance, and of course human-readable documentation. I'm also working towards having the vobject type document defined in itself, allowing reflection of the whole system. I've been doing a lot of reading, and I believe it would be accurate to say that the s5 design is evolving into an Erlang-meets-Smalltalk pattern: massive microthreading, highly reflexive dynamic runtime, but implemented as language-neutral kernel rather than a comprehensive programming environment. -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ]
signature.asc
Description: Digital signature
_______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
