On Wed, Oct 30, 2013 at 3:29 PM, Jonathan S. Shapiro <[email protected]> wrote: > I've been thinking about > type classes vs. (Java/C++) interfaces.
(java/C#)? > It seems to be that the "troublesome" cases are > the "objectless" interfaces, which have all of the same problems that TCs > have (as well as the same resolutions). Yeah, in the Objective-C/Ruby/Smalltalk style where 'Class' is an object too, that just lacks any mechanism (or space) to define state it seems much clearer to think (or talk) about. there, you can pass a class object, where you would typically pass an object instance (given an appropriate prototype), though they lack the ability to have static methods, so everything expects a 'this', even if that this is empty or contains only introspection junk. if trying to apply that same interoperability between thised and thisless seems a bit more painful, in that the calling convention depends on the /that/ of the operand rather than the declaration of the interface at the callsite... which seems rather wonky. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
