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

Re: Tabular command processing sans AutoOpts

From: Bruce Korb <bkorb_at_cruzio.com>
Date: 2000-11-13 00:33:53 CET

Karl Fogel wrote:
> Could you post a ChangeLog entry, or whatever, describing the change
> in more detail? Specifically, is it necessary to have all these stub
> files present from the start, even those that aren't being used, or
> could we instead just add them as they're needed?

The goal of the change is twofold:
1. Tabularize the command dispatch. This makes it possible to implement
    svn as a shell much more easily *AND* it makes each command a simple
    plug-in. One could even plausibly theorize about allowing a user
    to load a shared library with their own special-purpose commands.

2. Add in the commands we are pretty sure we want once.
    Each command is listed in five places:

    1. The Makefile.am has an entry for the command procedure file
    2. The command procedure file itself
    3. The command procedure declaration
    4. The command enumeration
    5. The dispatch table entry

    and soon:)

    6. The description of the applicable options for the command

    This is what one generally tries to avoid. I prefer to just have
    #2 and #6 and let some script drive all the glue pieces (#1, 3, 4 & 5).
    I made the assumption that there would be even more objection
    to this than to what I put forth today. If that is not true :-),
    I can easily make a glue script and dump the stubs. But still,
    the empty stubs give you a concrete view of the work we intend
    yet to do. A "better sense of progress" :-)
Received on Sat Oct 21 14:36:14 2006

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