[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Typed WebGLArray sequence parameter types
- To: Vladimir Vukicevic <email@example.com>
- Subject: Re: [Public WebGL] Typed WebGLArray sequence parameter types
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Tue, 22 Dec 2009 09:28:18 -0800
- Cc: email@example.com
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1261502901; bh=PuDMsrkhfS0ZspL84pzWop1wz8E=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=ss/N0MxcbR3WT8m+7MrDRPpISffkfA0NIqypKS3POrl1a+ur6l86wJOBBBA9qUGQC bx+SJ3emu9TLdLIgdJrpw==
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=Slyqo6YsJsM2ncipQgUyBsCMP4DlqaWM+C1JmxaTbN8lBbRm8TQlwN58i3+z1z5cI Zvk7WiuN5Ci+QXFsMegQQ==
- In-reply-to: <4B3068B2.firstname.lastname@example.org>
- References: <email@example.com> <4B3068B2.firstname.lastname@example.org>
- Sender: email@example.com
On Mon, Dec 21, 2009 at 10:35 PM, Vladimir Vukicevic
> On 12/21/2009 8:38 PM, Shiki Okasaka wrote:
>> Is this possible to modify typed WebGLArray sequence parameter types
>> in the IDL definitions as below?
>> * WebGLByteArray:
>> sequence<long> -> sequence<octet>
>> * WebGLUnsignedByteArray:
>> sequence<unsigned long> -> sequence<octet>
>> * WebGLShortArray:
>> sequence<long> -> sequence<short>
>> * WebGLUnsignedShortArray:
>> sequence<unsigned long> -> sequence<unsigned short>
>> This change would make the generated interfaces for statically typed
>> languages (e.g. Java) more useful.
>> Note currently Web IDL does not have a primitive type for 8-bit signed
>> integer values. If it is useful for WebGL, maybe we can propose an
>> addition of it to Web IDL as Geolocation WG requested to add 'double'
>> in addition to 'float' .
> Yep, that's the main reason why long/unsigned long are used instead of octet
> -- if octet was used, then it becomes impossible to actually specify signed
> 8-bit integers. For short, we decided to follow the same convention.
> However, maybe a workaround would be to add a typedef somewhere for our own
> signed_octet type, by default typedef'd to unsigned long, but with a
> statement in the spec saying that this should be a signed 8 bit type if the
> language supports it?
Sounds like a good workaround.
You are currently subscribe to firstname.lastname@example.org.
To unsubscribe, send an email to email@example.com with
the following command in the body of your email: