From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: unhandled keywords to goops "make" should signal errors
Date: Thu, 28 Mar 2002 00:19:10 -0800 [thread overview]
Message-ID: <E16qV7m-0008E7-00@giblet> (raw)
In-Reply-To: <15522.49014.788932.395068@winona.neilvandyke.org> (nwv@neilvandyke.org)
From: "Neil W. Van Dyke" <nwv@neilvandyke.org>
Date: Thu, 28 Mar 2002 02:00:06 -0500
If I understand Bug 11 correctly, then it appears to be a very
different problem than the one I report.
what you request for consideration must surely have been considered
before. if we figure out precisely how it is different and how it is
the same, perhaps we can apply that understanding.
because my personal coding has not yet advanced to using goops
regularly, my conjecture from reading related material is that keyword
handling in goops follows a non-blocking scheme reflecting its original
design model. i imagine when i do finally get to designing classes and
instantiating objects, i would view mixin techniques darkly if they were
(in return) so opaque.
perhaps i misunderstand the nature of keywords in goops and compare it
against other keyword disciplines, fruitlessly. how would i tell?
goops can be extended to do such error checking, in any case.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-03-28 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15498.49326.697620.427859@winona.neilvandyke.org>
2002-03-28 4:06 ` unhandled keywords to goops "make" should signal errors Thien-Thi Nguyen
[not found] ` <15522.49014.788932.395068@winona.neilvandyke.org>
2002-03-28 8:19 ` Thien-Thi Nguyen [this message]
2002-04-24 18:36 ` Marius Vollmer
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=E16qV7m-0008E7-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@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).