Re: use eiffel to build a CAM library?

[rob@brewster.demon.co.uk (Rob Heyes)]

In article <tgmEnAEI4.G6J@netcom.com>, tgm@netcom.com says...
> I disagree. If one's OO design operates purely in a synthetic domain,
> then callbacks may not be needed. But the real world is composed of
> data representations that must be cajoled into a format acceptable
> to OO techniques. Callbacks are most useful when attempting to parse
> non-OO streams in an OO fashion. Callbacks can be dispatched on some
> discriminant retrieved from the stream, rather than using ugly "if-then",
> "inspect", or "case" type techniques. 

What stops you using an object instead of a function pointer? Provide an 
abstract class that supplies the 'callback function' (and often 
encapsulates other relevant data) then create descendant classes that 
implement the 'callback' as appropriate.  Or am I missing your point, 
e.g. are you thinking of an OS routine that calls your code?

Rob Heyes