From: Kevin Ryde <user42@zip.com.au>
To: Marko Rauhamaa <marko@pacujo.net>
Cc: guile-gtk@sources.redhat.com
Subject: Re: texinfo documentation
Date: Fri, 23 May 2003 23:57:00 -0000 [thread overview]
Message-ID: <87of1tjjwy.fsf@zip.com.au> (raw)
In-Reply-To: <m3llwxe0l4.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "23 May 2003 15:53:59 -0700")
Marko Rauhamaa <marko@pacujo.net> writes:
>
> I'm sorry but I don't understand that comment. What "documented
> interfaces" are you talking about,
The functions and variables that an application programmer using
guile-gtk will utilize. How they work internally doesn't matter, not
directly.
> and what do you mean by "tying them down"?
Currently not all aspects (of how stuff works from within guile) are
spelt out in as much detail as would be desirable. In my view at
least.
next prev parent reply other threads:[~2003-05-23 23:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 1:21 Kevin Ryde
2003-05-12 1:52 ` Marko Rauhamaa
2003-05-23 22:01 ` Kevin Ryde
2003-05-23 23:36 ` Marko Rauhamaa
2003-05-23 23:57 ` Kevin Ryde [this message]
2003-05-24 0:05 ` Marko Rauhamaa
2003-05-24 2:19 ` Kevin Ryde
[not found] ` <m3llwwdhjf.fsf@lumo.pacujo.net>
2003-05-25 22:48 ` Kevin Ryde
2003-05-25 23:28 ` Marko Rauhamaa
2003-05-26 0:06 ` Kevin Ryde
2003-05-26 2:42 ` Marko Rauhamaa
2003-05-29 23:37 ` Kevin Ryde
2003-05-30 1:06 ` Marko Rauhamaa
2003-06-13 22:05 ` gdk-string-to-compound (was: texinfo documentation) Kevin Ryde
2003-07-07 22:30 ` gdk-string-to-compound Kevin Ryde
2003-05-29 23:43 ` texinfo documentation Kevin Ryde
2003-06-01 4:31 ` Marko Rauhamaa
2003-06-02 23:51 ` gdk-window-get-origin (was: texinfo documentation) Kevin Ryde
2003-07-07 22:29 ` gdk-window-get-geometry " Kevin Ryde
2003-05-26 0:07 ` gdk-rectangle-new " Kevin Ryde
2003-05-26 1:20 ` Marko Rauhamaa
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=87of1tjjwy.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-gtk@sources.redhat.com \
--cc=marko@pacujo.net \
/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).