On Friday 28 November 2003 08:44 pm, Jim Weirich wrote:
> T. Onoma wrote:
> > but can anyone explain why we have pre and post if wrap does them both?
>
> Pre and Post cannot effect the incoming parameters[1], nor can they
> effect the return result.  Wrap can do both.
>
> So, pre/post are "safer" if you don't want to change the semantics of
> the base method (e.g. logging).

okay, i see how that can be useful. cool. these are quite a nit differnt from 
wrap. they are only for monitoring purposes. limited but useful, and safe.

  defpre
  defpost

work for me. while the : is nice it strikes too much like a naming, especially 
with the new hash notation on the way { a: 1 }.

-t0