https://bugs.freedesktop.org/show_bug.cgi?id=71870
--- Comment #41 from Thomas Rohloff <v10la...@myway.de> ---
(In reply to comment #40)
> I'm not an expert on GLSL, but forbidding identifiers that contain '__'
> *anywhere* seems stupid to me. I'm not aware of any other programming
> language that imposes such a limitation on identifiers. What's the reason
> for this?
"All macro names containing two consecutive underscores ( __ ) are
reserved for future use as predefined macro names. All macro
names prefixed with “GL_” (“GL” followed by a single underscore)
are also reserved."
(source: Comment 33)
In other words: When you have a macro called "MY__SUPER_COOL_MACRO" Khronos
could step up telling "MY__SUPER_COOL_MACRO" is now a predefined macro and as
such your program is incompatible. I just fail to see why this is needed for
already finished specifications.
Anyway in that example Mesa could just disallow "MY__SUPER_COOL_MACRO" (expose
the internal macro instead) and not everything. Also I don't think the
specification says you're not allowed to use "MY__SUPER_COOL_MACRO", it just
tells you that it's a bad idea, so mesa is overstrict here.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
