Re: prototype __proto__ super and delegation

Peter Michaux wrote:
[...] Thomas 'PointedEars' Lahn [...] wrote:
Peter Michaux wrote:
On Oct 29, 4:05 pm, Thomas 'PointedEars' Lahn <PointedE...@xxxxxx>
wrote:
cbare wrote:
If __proto__ were an official part of the language, implementing a
decorator or proxy pattern would be nicely simplified compared to
class-based inheritence. The "before-and-after" style of AOP (which is
What do you mean by AOP?
Aspect-oriented programming. It's what's cool these days.
That must be it. I have never had much interest in hypes.

Ignore the hype. APO is useful.

That remains to be seen.

It the extreme opposite of having single DOM0 event handler.
And what would a "DOM0 event handler" be?

<body onload="alert('an explicit example of DOM0 event handler');">

This is not at all a "DOM0 event handler". It is a standardized attribute
(of HTML 4.01) that provides listener code for the equally standardized
`load' event (of DOM Level 2 Events).

It is all about decoupling concerns.
So AOP is nothing more than a synonym for the misguided "Unobtrusive
JavaScript" hype?

No. Nothing to do with JavaScript.

http://en.wikipedia.org/wiki/Aspect-oriented_programming

Thanks for the pointer; I would probably have found that shortly after, though.

Why, `.__proto__' is but a JavaScript shortcut for the ECMAScript-defined
`.constructor.prototype'.
obj.__proto__ is not a short cut for obj.constructor.prototype.
I think it is if you set up the prototype chain properly. I will look into
this later.

One has to do with constructing new objects. The other with already-
constructed objects.

Your statement does not make sense.


PointedEars
--
"Use any version of Microsoft Frontpage to create your site. (This won't
prevent people from viewing your source, but no one will want to steal it.)"
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>
.

Relevant Pages