public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Miroslav Silovic <silovic@zesoi.fer.hr>
To: Jim Blandy <jimb@red-bean.com>
Cc: Marius Vollmer <mvo@zagadka.ping.de>, Ariel Rios <jarios@usa.net>,
	guile-gtk@sourceware.cygnus.com
Subject: Re: Towards guile-gtk 0.18
Date: Sun, 31 Oct 1999 04:34:00 -0000	[thread overview]
Message-ID: <7ezowzhgf1.fsf@zesoi.fer.hr> (raw)
In-Reply-To: <m3wvs412vq.fsf@savonarola.red-bean.com>

Jim Blandy <jimb@red-bean.com> writes:

> I'm not sure if this helps you solve your present problem, but I guess
> it's worth noticing that this "Gosh, our automatically generated
> interface adapter stubs are kind of big!" scene has been played out
> before.  Many more times than once, I'd guess.  So some genuinely
> clever thinking is required here.

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

-- 
How to eff the ineffable?

  reply	other threads:[~1999-10-31  4:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-24 13:14 Ariel Rios
1999-10-25  7:46 ` Miroslav Silovic
1999-10-25 10:55   ` Marius Vollmer
1999-10-25 14:45     ` Miroslav Silovic
1999-10-30 23:05     ` Jim Blandy
1999-10-31  4:34       ` Miroslav Silovic [this message]
1999-10-31  5:14       ` Marius Vollmer
1999-10-31  9:54         ` Keith Wright
1999-11-01  6:37           ` Jim Blandy
1999-11-02 21:42             ` Keith Wright
1999-11-13  7:42 ` Towards guile-gtk x.xx Daniel Skarda

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=7ezowzhgf1.fsf@zesoi.fer.hr \
    --to=silovic@zesoi.fer.hr \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=jarios@usa.net \
    --cc=jimb@red-bean.com \
    --cc=mvo@zagadka.ping.de \
    /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).