[vwrap] Python integer types, again (was: The <embed> tag... is the group still interested in LLSD or DSD?)

Boroondas Gupte <sllists@boroon.dasgupta.ch> Sat, 07 May 2011 15:49 UTC

Return-Path: <sllists@boroon.dasgupta.ch>
X-Original-To: vwrap@ietfa.amsl.com
Delivered-To: vwrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC57FE06BB for <vwrap@ietfa.amsl.com>; Sat, 7 May 2011 08:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.687
X-Spam-Level:
X-Spam-Status: No, score=-1.687 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zx0qeQHnxg9o for <vwrap@ietfa.amsl.com>; Sat, 7 May 2011 08:49:17 -0700 (PDT)
Received: from datendelphin.net (india288.server4you.de [85.25.150.202]) by ietfa.amsl.com (Postfix) with ESMTP id E8370E0682 for <vwrap@ietf.org>; Sat, 7 May 2011 08:49:16 -0700 (PDT)
Received: from [192.168.1.107] (adsl-89-217-134-70.adslplus.ch [89.217.134.70]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by datendelphin.net (Postfix) with ESMTPSA id B0F622E045 for <vwrap@ietf.org>; Sat, 7 May 2011 17:52:44 +0200 (CEST)
Message-ID: <4DC569FB.90608@boroon.dasgupta.ch>
Date: Sat, 07 May 2011 17:49:15 +0200
From: Boroondas Gupte <sllists@boroon.dasgupta.ch>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b3pre Thunderbird/3.1.10
MIME-Version: 1.0
To: vwrap@ietf.org
References: <BANLkTi=g9T5q5bVgytpxRxuE=Oc9iG2F9w@mail.gmail.com> <4DC15504.3090503@gmail.com> <BANLkTikay4xhQoZs2L0uRLSXgUMfCE9yfA@mail.gmail.com> <4DC160F0.1030201@gmail.com> <BANLkTikTYpLHM=GAeGAVfufqZ5XT0FSAzw@mail.gmail.com> <BANLkTi=kjBSuMjPcgfXTUvZ3iwmS1bN50Q@mail.gmail.com> <4DC17704.3020201@gmail.com> <BANLkTimpGpNrkE3WUdurduqrVumocDRwfQ@mail.gmail.com> <4DC1824B.6040609@gmail.com> <BANLkTi=hhsiDs=fdZRsthp_+5Hs+pR4L6A@mail.gmail.com> <4DC1956A.5020204@gmail.com> <BANLkTik8rnsKP4xq+Gj5G4dsG=UOVnkNSQ@mail.gmail.com> <4DC1A8C9.9090406@gmail.com> <BANLkTikkOS34CC+ML0JNJgHDoRqbs9rY9w@mail.gmail.com> <4DC1D165.7010705@gmail.com> <4DC1D5FC.6040608@gmail.com> <BANLkTik81Eht3NTdLXXmgqOWvjc2s_KBnw@mail.gmail.com> <BANLkTi=-heHa35w43te0ba8NufkT+MP+CQ@mail.gmail.com> <BANLkTin6ExR7+xpodbtoTAS_4WyhUXL92Q@mail.gmail.com> <BANLkTikjKib79_rLR_s2X=X-ss-+V_yw+w@mail.gmail.com> <BANLkTim4aY7oNALbOfZ2V-htivVmQJZDiA@mail.gmail.com> <BANLkTimZZj3F0V4Li33WLYDby7n8M3A56w@mail.gmail.com>
In-Reply-To: <BANLkTimZZj3F0V4Li33WLYDby7n8M3A56w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------020903010305000909000401"
Subject: [vwrap] Python integer types, again (was: The <embed> tag... is the group still interested in LLSD or DSD?)
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 May 2011 15:49:18 -0000

On 05/07/2011 05:19 PM, Meadhbh Hamrick wrote:
> Josh, it's even worse than that.
>
> Python inherits the integer size from the compiler that generated it.
> So, if you compile python on a system with a 16 bit int (which used to
> be pretty common in some embedded systems) you get a version of python
> that uses 16 bit ints.
Fortunately, it's not as bad as /that/. While it's true that python
inherits the integer size from the compiler, it doesn't use C's int to
implements python ints, but C's long and thus can guarantee a precision
of at least 32 bits. Also, due to seamless conversion (see my other post
<http://www.ietf.org/mail-archive/web/vwrap/current/msg00862.html>) to
python's (unlimited precision) long, the actual size of python's int (or
the implementation dependence of that size) can probably be ignored most
of the time, except maybe for performance considerations.

Cheers,
Boroondas