From jan@swi.psy.uva.nl  Fri Sep  8 14:36:53 2000
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id OAA18187;
	Fri, 8 Sep 2000 14:36:52 +0200 (MET DST)
Received: from localhost (localhost [[UNIX: localhost]])
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id OAA05257;
	Fri, 8 Sep 2000 14:37:03 +0200
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Organization: SWI, University of Amsterdam
To: Paul Singleton <p.singleton@keele.ac.uk>,
        SWI Prolog <prolog@swi.psy.uva.nl>
Subject: Re: foreign functions and 64-bit hosts
Date: Fri, 8 Sep 2000 14:31:37 +0200
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <39B7D934.39288128@keele.ac.uk>
In-Reply-To: <39B7D934.39288128@keele.ac.uk>
MIME-Version: 1.0
Message-Id: <00090814370201.03427@gollem>
Content-Transfer-Encoding: 8bit

On Thu, 07 Sep 2000, Paul Singleton wrote:
>What's involved in writing foreign code that's portable to 64-bit platforms?
>
>(including the obvious, whatever that is :-)

As far as I know only the obvious.  If you write new code, be careful
about the sizes of the various integer types and if you port old code
and used to be lazy and assumed silently that int's and long's are about
the same, at least get yourself a compiler that warns you.

The foreign interface itself shouldn't pose any problems.  It is a 
bit sloppy on lengths of strings and atoms but nowadays atoms are
rarely longer then 2GB :-)

	Cheers --- Jan

