unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org, "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
Subject: Re: Passing C pointers through guile
Date: Fri, 11 Jul 2008 15:12:57 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807111507420.5259@ttleush> (raw)
In-Reply-To: <rmilk087er9.fsf@fnord.ir.bbn.com>



On Fri, 11 Jul 2008, Greg Troxel wrote:

> "Kjetil S. Matheussen" <k.s.matheussen@notam02.no> writes:
>
>> Also, various types of non-gc pointers are stored in integers in
>> all of the rt-*.scm files in http://snd.cvs.sourceforge.net/snd/cvs-snd/
>> and many others (xg.c, etc.). It would be horribly idiotic
>> to write smurf's for all of those, or at least a common smurf, when a
>> single integer is enough.
>
> What fraction of these uses are actually correct?  Have people run this
> code on Windows 64 (which is LLP64, but on which long is 32 bits),
> sparc64, and alpha.

All of them are correct. The alternative would be messier code.
The code in question doesn't run on those platforms anyway,
since there's a lot of strict linux stuff. However, I don't
the storage of pointers in unsigned longs (which is a perfectly
legal thing to do if done correctly), would pose any problem
for running it on other hardware.


>  I'm always worried when people store pointers in
> integers - it's IMHO basically a wrong thing to do.
>

In many situations, like the one above, it's a perfectly fine thing
to do, and also the only sane option. Of course, you must know what you 
are doing.




  reply	other threads:[~2008-07-11 13:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 20:09 Passing C pointers through guile Kjetil S. Matheussen
2008-07-09 20:43 ` Ludovic Courtès
2008-07-11 13:05 ` Greg Troxel
2008-07-11 13:12   ` Kjetil S. Matheussen [this message]
2008-07-11 14:42     ` Ludovic Courtès
     [not found] <cmu-lmtpd-26382-1215792388-9@mail-imap1.uio.no>
2008-07-11 17:22 ` Kjetil S. Matheussen
  -- strict thread matches above, loose matches on Subject: below --
2008-07-10 12:49 Kjetil S. Matheussen
2008-07-10 13:01 ` Ludovic Courtès
2008-07-09 19:58 Kjetil S. Matheussen
     [not found] <cmu-lmtpd-29205-1215446748-1@mail-imap1.uio.no>
2008-07-09 16:50 ` Kjetil S. Matheussen
2008-07-09 18:32   ` Kjetil S. Matheussen
2008-07-09 19:37     ` Ludovic Courtès
2008-07-09 19:35   ` Ludovic Courtès

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=Pine.LNX.4.64.0807111507420.5259@ttleush \
    --to=k.s.matheussen@notam02.no \
    --cc=gdt@ir.bbn.com \
    --cc=guile-devel@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).