unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: tomas@fabula.de
Cc: guile-user@gnu.org
Subject: (slightly OT) Dynamic link w/o *.h [was: Guile questions]
Date: Fri, 27 Aug 2004 12:01:18 +0200	[thread overview]
Message-ID: <20040827100118.GA20107@www> (raw)
In-Reply-To: <3508.67.36.45.214.1093546146.squirrel@67.36.45.214>

On Thu, Aug 26, 2004 at 02:49:06PM -0400, Jim Norris wrote:
> Hi, I was working on a tool to let someone dynamically link to dlls in
> Windows at runtime when I saw Guile. I couldn't tell if Guile had the
> features I'm looking for. If it doesn't maybe I could help add them or
> find some other way to help out?
> 
> Could you guys answer some questions for me please?
> 
> Does Guile let you dynamically link to dlls / object library files at run
> time without the need for header (*.h) files, *.def files, or *.lib files?
> (or the Unix equivalent)

How do you want to accomplish this? Has a Windows DLL enough info
about how to call a function (i.e. which parameters to expect,
maybe the layout of structs and so on)?

The question might sound ironic. No, I'm genuinley curious. I'm
pondering for a while about `glueless bindings' myself (along the
lines: if gdb can do that... -- but gdb uses the source plus
debugging info: I'd be happy to get that, and you seem to be even
more ambitious).

Regards
-- tomás


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2004-08-27 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 18:49 Guile questions Jim Norris
2004-08-26 21:39 ` Stephen Compall
2004-08-27 10:01 ` tomas [this message]
2004-08-27 13:55   ` (slightly OT) Dynamic link w/o *.h [was: Guile questions] Linas Vepstas
2004-08-27 13:57     ` Linas Vepstas
2004-08-27 14:07       ` tomas

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20040827100118.GA20107@www \
    --to=tomas@fabula.de \
    --cc=guile-user@gnu.org \
    /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).