[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] maximum length of identifiers in WebGL GLSL
- To: "Gregg Tavares (wrk)" <email@example.com>
- Subject: Re: [Public WebGL] maximum length of identifiers in WebGL GLSL
- From: Cedric Vivier <firstname.lastname@example.org>
- Date: Fri, 30 Jul 2010 16:51:45 +0800
- Cc: public webgl <email@example.com>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=S6QUtQ56Szd53W42CQbBRkLntrZmCC+VJKcXFC8d2xw=; b=Tgz5fW/thimPCLGD1tgkSkwi9gSKeEE54KD5ed0jrfjPV3HJ2O5S8+D1alSe9/y+UT DcPdWT5URDIAMLypA8RfyXl1YH1Hygp+BeMn38H6nmC1xMXwaHwwAi7Zp+eochiDQznI k3nX0ZUsXdFQ3s789ZTzJVBMxnwPYRT+vd6iU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=cOjpHd1mycMg/TYGc/N1K5lxijnxUANoVQL05LIakMKr2JtuZD9R20MtREDzPC/RWM myUugwFjEioAuAEDdy/eDJM+nNV9ZhfK41mHLS4N0Io2f//degtQqjRDt4u/UuA31pki aIEgr1vogBCSrjVn8W6qiBqkI1rV4TdphjoNk=
- In-reply-to: <AANLkTinPwuNQZnCXAkSJO5SFhf1bueO2bdpnV3FNSGHC@mail.gmail.com>
- References: <AANLkTinPwuNQZnCXAkSJO5SFhf1bueO2bdpnV3FNSGHC@mail.gmail.com>
- Sender: firstname.lastname@example.org
On Fri, Jul 30, 2010 at 06:11, Gregg Tavares (wrk) <email@example.com>
I didn't see one in the GLSL spec. ÂI was going to write a test with really long identifiers (4meg) to see if I could find some drivers that had problems with them but it might be better to just require WebGL to enforce some maximum length. Â64 chars? 128 chars? 256 chars which will make shaders less likely to fail on some drivers.
The results of the test you were going to write would be great to decide if and how big the limit should be I guess ;-)
Coincidently I was going to post a similar question with regards toÂgl_MaxVertexUniformVectors, gl_MaxFragmentUniformVectors and gl_MaxVaryingVectors ; they do not exist on GL desktop so I guess a GLSL ES to GLSL validator/translator needs to do something here.
Should the translator replace references to those with a literal value as in ES 2.0 spec (ie. 256, 256 and 15 respectively) or use a calculated value using the desktop's gl_Max**Components* with some formula to find the **Vector* equivalent ?