Re: ITLA

[Neil Jerram]

Andreas Rottmann <address@hidden> writes:

> Tom Lord <address@hidden> writes:
> 
> ,----
> |   Each interactive command will be defined by an ordinary Scheme
> |   procedure supplemented with a _declaration_.  The declaration lists:
> | 
> |   ~ the name of the command
> |   ~ a documentation string for the command
> |   ~ a list of options and parameters to the command, each
> |     specified by:
> | 
> |         + a parameter name
> | 
> |         + a "type declaration" (e.g., "string", or "new-archive-name",
> |           or "existing-archive-name", or "archive-name".)
> | 
> |         + a description of how it is parsed from options and
> |           arguments provided on command lines
> | 
> |         + a default value
> | 
> |         + an optional prompt string
> | 
> |         + an optional help string for the parameter
> | 
> |   ~ a "type declaration" for the output of the command
> | 

I've already coded something roughly along these lines, from the point
of view of providing infrastructure for command line driven
applications (for example, the Guile debugger).

This is in the modules (ossau interactive) and (ossau interactive XXX)
in http://www.ossau.uklinux.net/guile/guile-interactive-0.7.tar.gz, and
(ossau command-loop) may also be relevant.

Anyone working on this might want to check if they can get some
initial mileage out of my code.

        Neil