unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Exposing common type wrapping/unwrapping methods
Date: Mon, 04 Apr 2005 16:37:34 +0200	[thread overview]
Message-ID: <87oecutxox.fsf@laas.fr> (raw)

Hi,

Most type wrapping/unwrapping methods that are used within Guile are not
exposed to the user, which is a pity.  For example, `scm_addr_vector'
(in socket.c) which converts a `sockaddr' structure to its Scheme
representation (a vector) is defined as `static'.  This leaves the C
programmer with the following alternative:

* use, e.g., `scm_connect ()' instead of `connect ()' in its C code;

* define a new SMOB (or other representation) for `sockaddr' that may be
  incompatible with Guile's representation of this C type;

* copy/paste Guile's conversion methods, hoping that they're going to
  remain valid.


Obviously, the best solution would be to expose the relevant functions
to the user.  :-)

What do you think?

Thanks,
Ludovic.


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


             reply	other threads:[~2005-04-04 14:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 14:37 Ludovic Courtès [this message]
2005-05-24 17:53 ` Exposing common type wrapping/unwrapping methods Marius Vollmer
2005-06-14 16:38   ` Ludovic Courtès
2005-08-19  7:57     ` Ludovic Courtès
2005-08-20  6:01       ` Ken Raeburn
2005-08-20 12:40         ` Marius Vollmer
2005-08-20 13:53           ` Ken Raeburn
2005-09-04 22:17             ` Marius Vollmer
2005-09-07  4:17               ` Rob Browning
2005-09-04 22:09     ` Marius Vollmer
2005-09-07  9:49       ` Ludovic Courtès
2005-09-21  9:16         ` Ludovic Courtès
2005-09-22  0:14           ` Kevin Ryde
2005-09-22 13:46             ` Ludovic Courtès
2005-09-22 21:30               ` Kevin Ryde
2005-09-26  9:37                 ` Ludovic Courtès
2005-09-28 21:30               ` Kevin Ryde
2005-10-04 14:08                 ` Socket API improvement, patch #6 Ludovic Courtès
2005-10-17 10:55                   ` Ludovic Courtès
2005-10-17 21:43                     ` Kevin Ryde
2005-10-18  7:45                       ` Ludovic Courtès
2005-10-18 20:17                         ` Marius Vollmer
2005-10-24 11:35                           ` Ludovic Courtès
2005-10-24 21:42                             ` Kevin Ryde
2005-10-25 21:24                               ` Marius Vollmer
2005-10-27  1:06                                 ` Kevin Ryde
2005-10-27  8:49                                   ` Ludovic Courtès
2005-10-28 23:00                                     ` Kevin Ryde
2005-10-29 17:45                                       ` Marius Vollmer

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=87oecutxox.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    /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).