public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Marko Rauhamaa <marko@pacujo.net>
To: guile-gtk@sources.redhat.com
Subject: Re: Fixed memory leaks in gdk-1.2.defs
Date: Fri, 16 May 2003 01:02:00 -0000	[thread overview]
Message-ID: <m3u1bvemnu.fsf@lumo.pacujo.net> (raw)
In-Reply-To: <87r86zhkyc.fsf@zip.com.au>

Kevin Ryde <user42@zip.com.au>:

> Marko Rauhamaa <marko@pacujo.net> writes:
> >
> >  - The arrow notation is more descriptive and idiomatic.
> 
> The type names in mixed case don't appear in any function names
> currently though do they? Isn't it normally gtk-color-something?

I think the function naming scheme is an adaptation of the C function
names ("gtk_color_something") rather than the type names.

> >  - The "intern" suffix is actually misleading (no symbol table
> >    manipulation is going on).
> 
> If you read it as short for "internalize" then it seems fairly clear.
> Ie. a thing is brought to a canonical or efficient internal form.

"Intern" and "internalize" sounds to me like entering symbols into the
symbol table. "Coerce", "convert" and "cast" would sound like type
conversion. Scheme uses the arrow notation for coercion.


Marko

-- 
Marko Rauhamaa      mailto:marko@pacujo.net     http://pacujo.net/marko/

  reply	other threads:[~2003-05-16  1:02 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
2003-05-15 23:03     ` Kevin Ryde
2003-05-16  1:02       ` Marko Rauhamaa [this message]
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=m3u1bvemnu.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).