🚀 go-pugleaf

Len Charest (charest@ai-cyclops.jpl.nasa.gov) writes:

  I have a generic function with a primary method and at least one
  :AFTER method.  The GF uses standard method combination. In the body
  of the primary method I have a conditional RETURN-FROM statement
  which I had assumed would throw out of the *GF* altogether and skip
  execution of the :AFTER method (essentially overriding the semantics
  of standard method combination)

No, RETURN-FROM is entirely a lexical construct, and refers to the
implicit block wrapping the body of your primary method.  This is
exactly the correct behavior (see CLtL2, page 839).

  ... how do I exit from a primary method such that :AFTER method are
  skipped?  I'd like to avoid use of THROW and non-standard method
  combination.  Is it possible?

Briefly, no.  I can't think of anything else.


John Burger
john@mitre.org