From: Robert Marlow <bobstopper@australispro.com.au>
Subject: A couple of general-ish questions
Date: 18 Apr 2003 22:02:46 +0800 [thread overview]
Message-ID: <1050674570.613.9.camel@zuul> (raw)
Hi all
I just have a couple of questions
Firstly, I'm starting out writing guile bindings to LDAP and was wanting
to check if anybody was already working on this before I duplicate their
effort.
Secondly, I've been trying to do this with g-wrap but I'm completely new
to g-wrap. Specifically, LDAP has some struct types containing structs
(containing structs etc etc) and I was unsure how I should represent
such a nested type using g-wrap (see the LDAP struct typedef for
example). Does anyone have a clean solution to this?
Or should I not use g-wrap and instead use something else (eg ffcall)?
--
Regards,
Robert Marlow
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2003-04-18 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 14:02 Robert Marlow [this message]
2003-04-23 6:26 ` A couple of general-ish questions Rob Browning
2003-04-23 8:08 ` Matthias Koeppe
2003-04-23 20:12 ` Clinton Ebadi
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=1050674570.613.9.camel@zuul \
--to=bobstopper@australispro.com.au \
/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).