As for the original question, I don't see any reason the various built-in method combination could not have been defined to support :before and :after methods.  But the way they are defined is consonant with the short form of define-method-combination, which implies that the several built-in method combinations would typically be implemented using short form d-m-c.  So the scope of the original question probably should be expanded to include short form d-m-c.

On Fri, May 19, 2017 at 6:20 PM, Steve Haflich <shaflich@gmail.com> wrote:
You're apparently confusing two different meaning of "standard".  It's not the meaning that something is defined in the ANS and therefore built into the standard ANSI CL language.   Rather, it is a standard method-combination that is not the one known as STANDARD-METHOD-COMBINATION.

On Wed, May 17, 2017 at 1:50 PM, Ken Tilton <ken.tilton@weather.com> wrote:
Ah, but the OP specified "built-in" along with "non-standard".

hth

-hk

On Wed, May 17, 2017 at 3:24 PM, Sam Steingold <sds@gnu.org> wrote:
> * Didier Verna <qvqvre@yeqr.rcvgn.se> [2017-05-17 17:33:40 +0200]:
>
> Does anyone know why the non-standard built-in method combinations do
> not support before and after methods?

If you are defining the method combination, you have way more freedom
and flexibility than mere before and after.
Basically, you can do it yourself.

--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
https://ffii.org http://camera.org http://think-israel.org http://no2bds.org
Do not worry about which side your bread is buttered on: you eat BOTH sides.




--
Ken Tilton  |Software Engineer
w: (555) 555-5555      e: ken.tilton@weather.com