-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2 Apr 2007, at 22:44, Yuval Kogman wrote:
proto based OO is really a generalization of many of the other
systems, so i doubt there's a more fitting name. I'd rephrase your
sentance rephrasing 'merely' with 'a specific case of' =)

Yeah, OK :)

I think this specific approach has value even when the rest of your OO implementation isn't specifically prototype based though.

For me it comes under the general heading of minimising the number of mutatable entities in a program - which is generally a kwalitee and perhaps even quality win.

How is it like MVC? Or how may they be used interchangeably?

It's like MVC in the sense that their both views of the same underlying object.

s/their/they're/

Hmm, I never saw MVC like that...  I saw it as separation of
concerns with duck typing in the model and view, and ugliness kept
contained in the controllers, IMHO not much to do with
inheritence/chaining at
all, but i guess that could work.

I saw it as being roughly the same shape as MVC - a single data instance with multiple ways of interacting with it. The link is no stronger than that.

- --
Andy Armstrong, hexten.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFGEXxBwoknRJZQnCERAitzAKDOeH2448HC4ebx9XRWz6vqOz7WtACfcwOy
3HZ9EadfNlugMHJX3kCCtwc=
=3QwP
-----END PGP SIGNATURE-----

Reply via email to