[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why no "default" editor in Ev2?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 17 Jan 2012 16:41:27 -0500

On 01/17/2012 04:31 PM, Hyrum K Wright wrote:
> I'm working at experimenting with a simple Ev2 consumer implementation
> (see the ev2-export branch). In doing so, I've once again noticed
> that anybody implementing such a consumer has to implement every
> receiver. We don't provide default implementations, nor a way to only
> specify certain callbacks we're interested in. This is getting a bit
> tedious.
> Is this part of the design, or simply an oversight? Is there any
> drawback to providing default no-op implementations of the various
> receivers?

You mean, the way we have default implementations of all the old editor
functions that are overridden only as necessary? One could argue that no-op
default receiver implementations are deceptive to drivers of the interface.
 But then, the Ev2 driver can't legitimately expect any particular behavior
from the Ev2 implementation itself, so... *shrug*. I say "+1 on no-op
default receiver functions".

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2012-01-17 22:42:19 CET

This is an archived mail posted to the Subversion Dev mailing list.