unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: Andreas Rottmann <a.rottmann@gmx.at>,
	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: Sun, 09 May 2004 11:12:43 +1000	[thread overview]
Message-ID: <87llk24d4k.fsf@zip.com.au> (raw)
In-Reply-To: 87wu3ovl0v.fsf_-_@trouble.defaultvalue.org

Rob Browning <rlb@defaultvalue.org> writes:
>
> Don't get me wrong, I agree that prefixes are uglier[2], but for
> public APIs they do have the advantage of being very predictable for
> the user.

Just to chuck in my two cents worth, I wouldn't be in a hurry to break
out goops for something that's not inherently oop.  Or short names
either, since I think short names tend to seem like a good idea at the
start, but as a program gets big you forget what belongs to what, and
wish for at least some sort of naming regularity as guidance.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2004-05-09  1:12 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 [this message]
     [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=87llk24d4k.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=a.rottmann@gmx.at \
    --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).