On 4 November 2012 09:55, Eric Anholt wrote:
> Kenneth Graunke writes:
>
> > On 11/02/2012 05:13 PM, Ian Romanick wrote:
> >> On 11/02/2012 03:01 PM, Paul Berry wrote:
> >>> On 2 November 2012 14:11, Ian Romanick >>> Oh yuck! Why not just fix the names of the Mesa functions? That
> >>>
Kenneth Graunke writes:
> On 11/02/2012 05:13 PM, Ian Romanick wrote:
>> On 11/02/2012 03:01 PM, Paul Berry wrote:
>>> On 2 November 2012 14:11, Ian Romanick >> Oh yuck! Why not just fix the names of the Mesa functions? That
>>> seems much better than carrying the work-around in the cod
On 11/02/2012 05:13 PM, Ian Romanick wrote:
On 11/02/2012 03:01 PM, Paul Berry wrote:
On 2 November 2012 14:11, Ian Romanick mailto:i...@freedesktop.org>> wrote:
On 11/01/2012 03:19 PM, Paul Berry wrote:
When the XML lists one or more GL api functions as aliases for
another
On 11/02/2012 03:01 PM, Paul Berry wrote:
On 2 November 2012 14:11, Ian Romanick mailto:i...@freedesktop.org>> wrote:
On 11/01/2012 03:19 PM, Paul Berry wrote:
When the XML lists one or more GL api functions as aliases for
another
GL function, the mesa function that
On 2 November 2012 14:11, Ian Romanick wrote:
> On 11/01/2012 03:19 PM, Paul Berry wrote:
>
>> When the XML lists one or more GL api functions as aliases for another
>> GL function, the mesa function that implements the functionality is
>> usually named after the canonical version of the function
On 11/01/2012 03:19 PM, Paul Berry wrote:
When the XML lists one or more GL api functions as aliases for another
GL function, the mesa function that implements the functionality is
usually named after the canonical version of the function (the one
that is the target of the aliases). For example,
When the XML lists one or more GL api functions as aliases for another
GL function, the mesa function that implements the functionality is
usually named after the canonical version of the function (the one
that is the target of the aliases). For example, FogCoordd is listed
as an alias of FogCoord