Reflection - Confirm SqueakSource references still relevant

[dmitrizagidulin]

The Using method wrappers to perform test coverage section has two SqueakSource references.

Method wrappers are a well-known technique for intercepting messages. In the
original implementation(http://www.squeaksource.com/MethodWrappers.html), a
method wrapper is an instance of a subclass of ==CompiledMethod==. When
installed, a method wrapper can perform special actions before or after invoking
the original method. When uninstalled, the original method is returned to its
rightful position in the method dictionary.

and

In Pharo, method wrappers can be implemented more easily by implementing
==run:with:in:== instead of by subclassing ==CompiledMethod==. In fact, there
exists a lightweight implementation of objects as method
wrappers(http://www.squeaksource.com/ObjectsAsMethodsWrap.html), but it is not
part of standard Pharo at the time of this writing.

Is this distinction (original implementation vs Pharo) still relevant? Perhaps update the links to SH?

[nicolaihess]

I think the distinction is still valid, and there is no (official pharo) package at SH.
(but neither MethodWrappers nor ObjectsAsMethods are working on Pharo)