From: Andy Wingo <wingo@pobox.com>
Subject: Re: Finally ready to talk more substantively about 1.9 (and tng).
Date: Sat, 08 May 2004 19:44:11 +0100 [thread overview]
Message-ID: <1084041850.14533.15.camel@localhost> (raw)
In-Reply-To: <1084041609.14317.13.camel@localhost>
Copying to guile-devel to show my ignorance to all!
On Sat, 2004-05-08 at 19:40, Andy Wingo wrote:
> Hey,
>
> On Thu, 2004-05-06 at 18:23, Andreas Rottmann wrote:
> > > (for-each (lambda (f) (close f)) items)
> >
> > This should be (for-each (lambda (file) (close file)) items)
>
> Or, as a bikeshed, (for-each close files).
>
> > I agree that these names are a bit overly generic. I'll quote the list
> > of maybe too generic (g-wrap) exports here, so we can discuss about
> > name changes.
> >
> > description
> > 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!
>
> OK, another nitpick. GTK is where I'm most familiar with generic
> functions. When they have getters, they use `get-' before the name. It
> is a mental clue that the function is a generic. It's not so schemy, but
> then, generic functions aren't all that schemy either. And of course
> `get-' doesn't make sense as an accessor. Perhaps then you should be
> using slot-set!, etc anyway. Just a thought.
>
> Cheers,
--
Andy Wingo <wingo@pobox.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-05-08 18:44 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
2004-05-09 1:12 ` Kevin Ryde
[not found] ` <1084041609.14317.13.camel@localhost>
2004-05-08 18:44 ` Andy Wingo [this message]
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=1084041850.14533.15.camel@localhost \
--to=wingo@pobox.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).