Re: When to use 'Class in a parameter list

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

...And then it hit me like the wet kiss at the end of a fist....
(Lightbulb!) Ahhhhhh! Its all coming back to me as if out of an alcoholic
stupor...

O.K. This has me pretty much back on track. I want the class-wide flavor if
inside the routine I want to generalize some part of the operation and
possibly dispatch to other operations that may depend on the specific type
of object sent in.

I really need to work with this stuff more than once a year... :-)

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Ehud Lamm" <mslamm@mscc.huji.ac.il> wrote in message
news:9jk3lr$ki0$1@news.huji.ac.il...
>
>
> The way I explain it to my students is like this "from the 'outside' of
the
> class-wide routine there no dispatching" (i.e., no dispatching on call to
> the class-wide routine), "from the 'inside' you can have dispathcing, by
> calling the dispatching operations" (i.e, calls to primitive routine, made
> inside the class-wide routine).
> Notice that when you call a  routine that expect a specific type, from
> inside a class-wide routine you are, in a sense, giving a class-wide
> actual - and per the table above you may have dispatching.
>
> Another way at looking at this, is to realize that the class-wide
operation
> behave the same for all type in the hierarchy, up to calls to dispatching
> routines. The commonality is expressed by creating a class-wide routine;
the
> routine can be sensitive to the differences between the types in the
> hierarchy by calling type specific (dispatching) routines.
> Aside from the concept of "template function pattern", another common term
> is "factoring out common behaviours" - this may give a better idea what's
> this all about from a design POV.
>
> Ehud Lamm
>
>