On 13 September 2017 at 22:13, Matt Turner wrote:
> On Mon, Aug 21, 2017 at 3:27 AM, Emil Velikov
> wrote:
>> From: Emil Velikov
>>
>> memmem() does not attribute what the character after the searched string
>> is. Thus it will flag even when haystack is "foobar" while we're looking
>> for "foo
On Mon, Aug 21, 2017 at 3:27 AM, Emil Velikov wrote:
> From: Emil Velikov
>
> memmem() does not attribute what the character after the searched string
> is. Thus it will flag even when haystack is "foobar" while we're looking
> for "foo".
>
> Pull a small helper (based on piglit) that correctly h
On 21/08/17 20:27, Emil Velikov wrote:
From: Emil Velikov
memmem() does not attribute what the character after the searched string
is. Thus it will flag even when haystack is "foobar" while we're looking
for "foo".
Pull a small helper (based on piglit) that correctly handles this and use
it.
On Monday, 2017-08-21 11:27:21 +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> memmem() does not attribute what the character after the searched string
> is. Thus it will flag even when haystack is "foobar" while we're looking
> for "foo".
>
> Pull a small helper (based on piglit) that corre
From: Emil Velikov
memmem() does not attribute what the character after the searched string
is. Thus it will flag even when haystack is "foobar" while we're looking
for "foo".
Pull a small helper (based on piglit) that correctly handles this and use
it.
Note: when parsing through the shader we
