From: David Pirotte <david@altosw.be>
To: Mark Harig <idirectscm@aim.com>
Cc: guile-devel@gnu.org
Subject: Re: Indexing Scheme and C identifiers separately
Date: Mon, 25 Apr 2011 13:16:55 -0300 [thread overview]
Message-ID: <20110425131655.1d06162c@rascar> (raw)
In-Reply-To: <8CDD0E83970C890-1820-11709@webmail-m029.sysops.aol.com>
Hello Mark,
Le Sun, 24 Apr 2011 18:43:54 -0400,
Mark Harig <idirectscm@aim.com> a écrit :
> On Sun, Apr 24, 2011 at 07:09:07PM -0300, David Pirotte wrote:
[...]
> What would be of some help to get this project started is a
> list of the identifiers:
>
> 1) A list of all Scheme procedure names
> 2) A list of all C procedure names
> 3) A list of all Scheme variable names
> 4) A list of all C variable names
> 5) A list of all Scheme type names
> 6) A list of all C type names
Yes, that's what I meant. What you get, looking at
http://www.gnu.org/software/guile/docs/docs-2.0/guile-ref/index.html, is ...
Looking at 'Procedure Index', for example not really knowing what your looking for
but presumably starting with letter 's', as a 'pure' scheme programmer, reaching
scm-xxx, you'll have to hit more or less 33 times page down [depending on your
display and browser size obviously] to 'continue' with other 'scheme' indice entries
[they may be other entries, at the beginning they are *scm_]. If you realize you
probably have passed and missed the item you're looking for, you'll have to hit 33
times page-up ... not a big deal but it would be really nice to have 'per language'
indices.
If [and only if :-)] it can be easily done [which I assumed, but ...], i would
suggest the following [assuming a 'grouping' by language but i don't have a problem
if it is by 'proc' 'var' and 'type'
Indices
. Concept Index
. Scheme Procedure Index
. Scheme Variable Index
. Scheme Type Index
. C Procedure Index
. C Variable Index
. C Type index
. R5RS Index
> (By "all names", I mean "all names included in the Guile
> Reference Manual", not, for example, "all C function names
> in Standard C".)
Thanks God :-)
> Also useful would be more suggestions for the Concept Index.
> ...
I will if and when I have a useful comment to make but so far I think it really is
good.
Many thanks for your work on the manual.
Cheers,
David
next prev parent reply other threads:[~2011-04-25 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 19:46 Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-24 14:33 ` Andy Wingo
2011-04-24 20:36 ` Mark Harig
2011-04-24 21:00 ` Andy Wingo
2011-04-24 21:58 ` Mark Harig
2011-04-25 8:01 ` Andy Wingo
2011-04-24 22:09 ` David Pirotte
2011-04-24 22:43 ` Indexing Scheme and C identifiers separately Mark Harig
2011-04-25 1:18 ` Noah Lavine
2011-04-25 16:16 ` David Pirotte [this message]
2011-05-20 22:53 ` Neil Jerram
2011-04-25 19:49 ` Patch: New section "Invoking Guile" for chapter "Programming in Scheme" Mark Harig
2011-04-26 18:07 ` Neil Jerram
2011-04-26 21:01 ` Ludovic Courtès
2011-04-27 9:40 ` Andy Wingo
2011-04-27 10:23 ` Ludovic Courtès
2011-04-27 19:29 ` Neil Jerram
2011-04-27 16:54 ` Mark Harig
2011-04-27 19:40 ` Neil Jerram
2011-06-30 11:23 ` Andy Wingo
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=20110425131655.1d06162c@rascar \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=idirectscm@aim.com \
/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).