public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@mdj.nada.kth.se>
To: "Greg J. Badros" <gjb@cs.washington.edu>
Cc: djurfeldt@nada.kth.se
Subject: Re: Patch to make guile-gtk work with upcoming guile-1.4
Date: Mon, 19 Jun 2000 15:47:00 -0000	[thread overview]
Message-ID: <xy7og4x8f0a.fsf@mdj.nada.kth.se> (raw)
In-Reply-To: <qrr8zw1v0ki.fsf@clavicle.cs.washington.edu>

"Greg J. Badros" <gjb@cs.washington.edu> writes:

> I'd much prefer that this function not be depracated... notice all of
> the redundancies and potential maintenance headaches below.  People
> *will* cut and paste from one section to another, change the *_hook in
> the first line, and forget to change it in later lines, resulting in a
> hard-to-find and nasty bug.

I don't think this will cause much problems, and, actually, I think
the standard interface (scm_make_smob_type/scm_set_smob_xxx) is easier
to read and intuitively understand.

But we'll not let that debate delay release.  Instead we prepare for
the eventuality that it will be removed, and don't bring it forward as
a suggested way to code in this release.

  reply	other threads:[~2000-06-19 15:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-01 21:05 guile-gtk 0.18 Released Ariel Rios
2000-06-18 19:06 ` Patch to make guile-gtk work with upcoming guile-1.4 Greg J. Badros
2000-06-19  2:06   ` Mikael Djurfeldt
2000-06-19 14:11     ` Greg J. Badros
2000-06-19 15:47       ` Mikael Djurfeldt [this message]
2000-06-19 14:49     ` Marius Vollmer
2000-06-19 15:01       ` Greg J. Badros
2000-06-19 21:54         ` Jim Blandy
2000-06-20  8:41           ` Greg J. Badros
2000-06-20  9:15             ` Jost Boekemeier
2000-06-20  9:22               ` Brett Viren
2000-06-19 14:49   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xy7og4x8f0a.fsf@mdj.nada.kth.se \
    --to=mdj@mdj.nada.kth.se \
    --cc=djurfeldt@nada.kth.se \
    --cc=gjb@cs.washington.edu \
    /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).