Re: [Sooc-devel] Message handlers, interfaces

[Dan R. <sta...@gm...>]

Multiple interface types seems kind of hefty, but I'll let you think about
it some more.

On 9/3/07, Mike Richman <mik...@gm...> wrote:
>
> It sounds like there are good reasons for Sooc to have interfaces that
> can have partial or (maybe) complete default implementations, and
> other good reasons for Sooc to have interfaces that forbid default
> implementations.  Maybe it should allow both?
>
> I haven't thought this through completely, but maybe there can be
> something like s_iface and s_pure_iface.  Pure interfaces would forbid
> any default implementations either by providing no means of connecting
> handlers or by zeroing the whole iface at the end of its init
> function.
>
> Also, regardless of how interfaces end up working, I think it might be
> nice to have a debugging mode at runtime.  It can be on or off.  When
> it's on, each class will track where its messages are connected.  User
> code could then do something like s_dbg_msg_connections (stream,
> Class).  There could potentially be other debugging help when
> debugging mode is on.  This message tracking will be non-trivial to
> implement, though.
>
> -Mike
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Sooc-devel mailing list
> Soo...@li...
> https://lists.sourceforge.net/lists/listinfo/sooc-devel
>