Sun Serega

@Perksey > try and establish a sane baseline [[1]](https://github.com/KhronosGroup/OpenGL-Registry/pull/543#issuecomment-1262540168) Ok, was mostly walking past this because I agree with: > Personally I do think that because the enum groupings are...

What about the XML? I guess the only change is that this: ``` ``` Should be: ``` ```

Well, if the parameter is consistently `target` now (tho in some places, like `glDisableClientState` - it's `array`) - then the group `EnableCap` should also get renamed...

I was thinking the same way, from `EnableCap` to `EnableTarget` - to use the same term.

> I would suggest reverting the group changes until https://github.com/KhronosGroup/OpenGL-Registry/issues/481 is in place. Wouldn't that be a time when improvements like these would be impossible for sure? And even if...

Fair enough... I have a lot of doubts about continuing things like #543 - having guidelines would solve that, one way or another. But as it is, I feel powerless...

Well, i'm okay with not fixing this for commands of deprecated extensions and such. But from what listed here - some are from relevant extensions. And some are from core....

I'm not saying they are required for C/C++ gl header generation. And so i'm not implying in any way that khronos needs to deal with this. Group are needed only...

> if it's too big of a job for us, it is too big It would clearly be less effort then when i parsed specs and manually created groups, being...

Updated. Sorry for not getting to this myself. I have a lot going on and spend rest time on pet projects. Though one of them is OpenGL bindings, so this...