From: Rob Browning <rlb@defaultvalue.org>
Cc: G-Wrap development <g-wrap-dev@nongnu.org>, guile-devel@gnu.org
Subject: Re: G-wrap 1.9 public API (goops, generics, and modules).
Date: Fri, 07 May 2004 10:20:27 -0500 [thread overview]
Message-ID: <87hdusuuv8.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87wu3ovl0v.fsf_-_@trouble.defaultvalue.org> (Rob Browning's message of "Fri, 07 May 2004 00:55:28 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
> I'm still hesitant about really generic names outside of guile core.
> I wouldn't be quite as hesitant if guile itself had defined a
> documentation generic for use in its global documentation
> infrastructure, and if it had, or adds one later, then I presume we'd
> have trouble here.
>
>> typespec
>> c-name
>> argument-count input-argument-count optional-argument-count
>> arguments argument-types
>> return-type return-typespec
>> generic-name
>> class-name type options c-type-name all-types add-option!
>> var wrapped-var
>> visible? default-value number name render no-op?
>
>> Hmm, variable-name and wrapped-variable-name? A bit long, but
>> bearble I think.
Oh, and upon re-reading my message this morning, I can see that my
editing of the replies didn't make it at all clear here that Andreas
and I are both interested in changing some or all of the exported
names as we prepare for release. The question is just "to what". For
those who hadn't seen the history, my reply didn't make that clear.
The above was my own forshortening of the conversation in the previous
message, and the full message I was replying to can be seen on the
g-wrap-dev mailing list. (Apologies to Andreas for any possible
misharacterization.)
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-05-07 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87llk55zpw.fsf@trouble.defaultvalue.org>
[not found] ` <87smedeagi.fsf@ivanova.rotty.yi.org>
2004-05-07 5:55 ` G-wrap 1.9 public API (goops, generics, and modules) Rob Browning
2004-05-07 15:20 ` Rob Browning [this message]
2004-05-09 1:12 ` Kevin Ryde
[not found] ` <1084041609.14317.13.camel@localhost>
2004-05-08 18:44 ` Finally ready to talk more substantively about 1.9 (and tng) 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=87hdusuuv8.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=g-wrap-dev@nongnu.org \
--cc=guile-devel@gnu.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).