hgmerge.py in mainstream mercurial distribution

[Arve Knudsen]

On Dec 11, 2007 2:01 PM, dhruva <dhruvakm at gmail.com> wrote:

> Hi,
>
> On Dec 11, 2007 6:13 PM, Arve Knudsen <arve.knudsen at gmail.com> wrote:
> > There wasn't a whole lot that was said. The gist of it was that Matt
> > required that hgmerge.py be simplified, made easy to extend with support
> for
> > new tools (perhaps defined from outside the Python code?) and made
> > configurable so that people can easily write merge handlers  e.g. for
> > special file types (such as .doc). That was my understanding anyway.
>
> Thanks, I will start exploring ways to simplify and keep it
> extensible. Related to this topic, would it be a nice idea to have
> something like emacs 'defadvice'. Using it, you are redefine some of
> the functions to execute something before it is called and/or after it
> is called. An alternative would be to have hooks 'pre and post' for
> all such functions. This makes it really extensible.


This sounds like an Aspect-Oriented technique to me? Anyway, it is too early
to be considering specific coding techniques IMO, although AOP is pretty
fancy. Better review what kind of configurability is expected on the user
level.

Arve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial-devel/attachments/20071211/8575915c/attachment.htm