From: Marko Rauhamaa <marko@pacujo.net>
To: guile-gtk@sources.redhat.com
Subject: Re: Fixed memory leaks in gdk-1.2.defs
Date: Mon, 12 May 2003 07:55:00 -0000 [thread overview]
Message-ID: <m38ytcppwg.fsf@lumo.pacujo.net> (raw)
In-Reply-To: <871xz53raq.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au>:
> Marko Rauhamaa <marko@pacujo.net> writes:
> >
> > - gdk-1.2.defs: Indicated that gdk_font_intern and gdk_color_intern are
> > now deprecated. (I don't think anybody used them anyway.)
>
> I've been using them for the purpose described in the README, namely
> to get a conversion from a string just once.
>
> I guess there's other ways to do that, but for upward compatibility
> I'd suggest keeping those routines.
Aha, didn't think of that.
I have submitted this generalization of the scheme: Whenever a
'conversion option is specified for a boxed or struct type, such an
"intern" function is generated automatically. However, I have chosen to
name the converter function ->type (for example: ->GdkFont, ->GdkColor)
for two reasons:
- The arrow notation is more descriptive and idiomatic.
- The "intern" suffix is actually misleading (no symbol table
manipulation is going on).
For compatibility reasons I have retained the two "intern" functions but
still deprecate them.
Marko
--
Marko Rauhamaa mailto:marko@pacujo.net http://pacujo.net/marko/
next prev parent reply other threads:[~2003-05-12 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 6:33 Marko Rauhamaa
2003-05-12 1:05 ` Kevin Ryde
2003-05-14 1:18 ` Marko Rauhamaa
2003-05-12 1:08 ` Kevin Ryde
2003-05-12 7:55 ` Marko Rauhamaa [this message]
2003-05-15 23:03 ` Kevin Ryde
2003-05-16 1:02 ` Marko Rauhamaa
2003-05-17 8:08 ` Marko Rauhamaa
2003-06-18 23:31 ` GdkEvent copy under signal handler (was: Fixed memory leaks in gdk-1.2.defs) Kevin Ryde
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=m38ytcppwg.fsf@lumo.pacujo.net \
--to=marko@pacujo.net \
--cc=guile-gtk@sources.redhat.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).