public inbox for
 help / color / mirror / Atom feed
From: Ariel Rios <>
To: Miroslav Silovic <>, Jim Blandy <>
Cc: Marius Vollmer <>, Ariel Rios <>,
Subject: Re: [Re: Towards guile-gtk 0.18]
Date: Sun, 31 Oct 1999 17:54:00 -0000	[thread overview]
Message-ID: <> (raw)

Miroslav Silovic <> wrote:

> *grin* Actually there are two problems: size of the automatically
> generated stubs (which is not *really* big, 300kb is managable... and
> I posted a possible method to reduce this size by a significant
> factor), and the fact that all these stubs end up in the same file -
> making building cycle astonishingly long. The former is not too much
> of a problem, while the latter is - and it's also much easier to
> solve, simply split defs file in a clever way.
My suggestion is to split gtk.defs following the diff'rent gtk libraries. In
my opinion in this way we can a neat standard way to make the split and also
we could have better control on how many functions we have wrapped.


Get free email and a permanent address at

                 reply	other threads:[~1999-10-31 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \ \ \ \ \ \ \

* 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).