public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Zach Frey <zfrey@bright.net>
To: Miroslav Silovic <silovic@zesoi.fer.hr>
Cc: jarios@usa.net, hp@redhat.com, otaylor@redhat.com,
	james@daa.com.au, sopwith@redhat.com, federico@redhat.com,
	guile-gtk@sourceware.cygnus.com, gnome-list@gnome.org
Subject: Re: Common Gtk/GNOME language bindings?
Date: Fri, 17 Dec 1999 06:52:00 -0000	[thread overview]
Message-ID: <19991217100204.A24696@bright.net> (raw)
In-Reply-To: <199912171406.PAA23091@petra.zesoi.fer.hr.>

On Fri, Dec 17, 1999 at 03:06:28PM +0100, Miroslav Silovic wrote:
> So, here is my suggestion:
> 
>  - decide on the common file format
> 
>  - write the spec files (large part of this can be achieved by
>    converting guile-gtk files, or specfiles from some other project)
> 
>  - write the glue and stub generator for the target languages.

 
Well, there's always SWIG < http://www.swig.org/ >, which already
provides a format for a binding hints file (if one doesn't like what
SWIG comes up with as default bindings), and glue/stub code generation.

Supported languages include Perl, Python, Tcl, Java, Eiffel, and 
even Guile.

So maybe it would make sense to see if SWIG does what is desired
before reinventing any wheels.


FYI,

Zach

-- 
Remember, you're a software professional, not a magician.  Leave the
illusions to management.
  -- Dinu Madau

  reply	other threads:[~1999-12-17  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-17  6:24 Miroslav Silovic
1999-12-17  6:52 ` Zach Frey [this message]
2000-01-21  9:00   ` Alex Stark
1999-12-17  8:11 ` James Henstridge

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=19991217100204.A24696@bright.net \
    --to=zfrey@bright.net \
    --cc=federico@redhat.com \
    --cc=gnome-list@gnome.org \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=hp@redhat.com \
    --cc=james@daa.com.au \
    --cc=jarios@usa.net \
    --cc=otaylor@redhat.com \
    --cc=silovic@zesoi.fer.hr \
    --cc=sopwith@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).