From: Miles Bader <miles@lsi.nec.co.jp>
Cc: gnu-arch-users@gnu.org, a.rottmann@gmx.at, ttn@glug.org,
guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: ITLA
Date: 02 Mar 2004 12:26:48 +0900 [thread overview]
Message-ID: <buoad30x72f.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <200403012155.NAA20825@morrowfield.regexps.com>
Tom Lord <lord@emf.net> writes:
> I'm not quite agnostic about using GOOPS in this particular area.
> Really, I'm mostly against it except as it helps "internally" in
> various modules.
...
> It's kind of a situation where K.I.S.S. is the dominant design
> consideration.
Yeah...
When I read the post to which you replied, I had this sinking feeling I
was seeing the Beginning of the Creep.
-Miles
--
If you can't beat them, arrange to have them beaten. [George Carlin]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-02 3:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
[not found] ` <E1AxlJY-0002cb-00@surf.glug.org>
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` Miles Bader [this message]
2004-03-03 11:22 ` ITLA Neil Jerram
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
[not found] ` <E1AziNk-0007mW-00@surf.glug.org>
2004-03-06 20:39 ` ttn's build system Andreas Rottmann
2004-03-10 18:59 ` Andreas Rottmann
2004-03-10 22:28 ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22 ` Tom Lord
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=buoad30x72f.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=a.rottmann@gmx.at \
--cc=gnu-arch-users@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=miles@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).