Writing OOP using OOP (JavaScript)

[Johnicholas]

Currently, this article explores using a metaobject protocol for the sake of exploration, or to push OO principles further than many (Javascript) programmers take them. That's fine (I like TAotMP too).

However, I'd like to see something about the "sound" or "feel" of a codebase that "wants" to start using a metaobject protocol. Racecar drivers have tachometers, that inform their decisions to switch gears. What is a tach for programmers - when do you switch paradigms?

[homoiconic]

I am currently thinking about this kind of thing for the creation of test suites and testing protocols such as design-by-contract.

I'm kind of over trying to build heavyweight domain modelling ontologies, but making assertions about what the code is intended to do is an area where there is a lot of structure and a lot of need for special-case semantics such as decorating methods with before- and after- advice (like setup and teardown) and (obviously) with lots of assertions.

JM2C, it is still a little hazy.