From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3008 invoked by alias); 12 Sep 2003 23:02:16 -0000 Mailing-List: contact guile-gtk-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: guile-gtk-owner@sources.redhat.com Received: (qmail 2991 invoked from network); 12 Sep 2003 23:02:15 -0000 Received: from unknown (HELO snoopy.pacific.net.au) (61.8.0.36) by sources.redhat.com with SMTP; 12 Sep 2003 23:02:15 -0000 Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) by snoopy.pacific.net.au (8.12.3/8.12.3/Debian-6.4) with ESMTP id h8CN2EBt004509 for ; Sat, 13 Sep 2003 09:02:14 +1000 Received: from localhost (ppp113.dyn228.pacific.net.au [203.143.228.113]) by mongrel.pacific.net.au (8.12.3/8.12.3/Debian-6.4) with ESMTP id h8CN0NQR023292 for ; Sat, 13 Sep 2003 09:00:24 +1000 Received: from gg by localhost with local (Exim 3.35 #1 (Debian)) id 19xwvV-0000Tr-00; Sat, 13 Sep 2003 09:02:05 +1000 To: guile-gtk@sources.redhat.com Subject: Re: Compiling guile-gobject experiences References: <87ptjornbn.fsf@alice.rotty.yi.org> <20030804162116.GA1217@lark> From: Kevin Ryde Mail-Copies-To: never Date: Fri, 12 Sep 2003 23:02:00 -0000 Message-ID: <871xulk3v7.fsf@zip.com.au> User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q3/txt/msg00078.txt.bz2 Andy Wingo writes: > > But I do agree that it's a problem. I think reducing the size of the > generated code is the best solution, personally. A bit less error inlining might help. I can see how the cleanup stuff ends up needing it, but there's plenty of cases with no cleanups. Perhaps building a list of cleanups at runtime would keep it down. It'd be nice to call foreign functions just based on a little set of argument types, with no actual individual glue code at all. I've got an idea gnu smalltalk has something like that. I don't think there's any way to portably make a C call from runtime arguments, in general, but it wouldn't be hard to setup the right thing for each CPU+ABI, with a bit of assembler. Or maybe gcc could help.