From: Neil Jerram <neil@ossau.uklinux.net>
Cc: gnu-arch-users@gnu.org, ttn@glug.org, guile-user@gnu.org,
guile-devel@gnu.org
Subject: Re: ITLA
Date: 03 Mar 2004 11:22:38 +0000 [thread overview]
Message-ID: <85d67uxji9.fsf@ossau.uklinux.net> (raw)
In-Reply-To: 87r7wc4bxm.fsf@alice.rotty.yi.org
Andreas Rottmann <a.rottmann@gmx.at> writes:
> Tom Lord <lord@emf.net> 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
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-03-03 11:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
[not found] ` <E1AxlJY-0002cb-00@surf.glug.org>
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` ITLA Miles Bader
2004-03-03 11:22 ` Neil Jerram [this message]
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
[not found] ` <E1AziNk-0007mW-00@surf.glug.org>
2004-03-06 20:39 ` ttn's build system Andreas Rottmann
2004-03-10 18:59 ` Andreas Rottmann
2004-03-10 22:28 ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22 ` Tom Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85d67uxji9.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=gnu-arch-users@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).