"weird" variable initialization

Question

What is meant by:

GLuint bindingPoint = 1, buffer, blockIndex;

I found this in one tutorial which I need, and I have never seen such a variable initialization before.

Does this line mean

GLuint bindingPoint = 1; GLuint bindingPoint = buffer; GLuint bindingPoint = blockIndex;

?

init-declarator-list

genpfault
– genpfault

2016-12-21 21:33:00 +00:00
Commented Dec 21, 2016 at 21:33 — genpfault
– genpfault, Commented Dec 21, 2016 at 21:33

StoryTeller - Unslander Monica · Accepted Answer · 2016-12-21 21:17:22Z

7

The line GLuint bindingPoint = 1, buffer, blockIndex; is equivalent to the following three:

GLuint bindingPoint = 1; GLuint buffer; GLuint blockIndex;

Both versions define the variables bindingPoint, buffer, blockIndex. With bindingPoint initialized to 1.

answered Dec 21, 2016 at 21:17

StoryTeller - Unslander Monica

172k22 gold badges401 silver badges481 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Martin Bonner supports Monica Over a year ago

The other option (which would only be legal if buffer and blockIndex had been declared already) would be GLuint bindingPoint = (1, buffer, blockIndex); which would mean "evaluate 1 and throw the result away, evaluate buffer and throw the result away, evaluate blockIndex and use it to initialize a new variable bindingPoint of type `GLuint.

Martin Bonner supports Monica Over a year ago

To be clear: that is not an alternative reading of the original statement. The statement unambigiously means what StoryTeller has written. It is what a similar looking statement would mean.

Collectives™ on Stack Overflow

"weird" variable initialization

1 Answer 1

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Related