@int10h @whitequark 6.7.2.2¶4 "The choice of type is implementation-defined"
@ch3root @int10h @whitequark Formally, yes. In practice, not as long as you add at end & library is responsible for all allocation.
-
-
@RichFelker@int10h@whitequark So, either add INT_MIN into each external enum or use plain int for vars. -
@RichFelker@int10h@whitequark Hm, enums are permitted to be wider than int so only plain ints for ABIs. -
@ch3root@RichFelker@int10h typical C apologism. "Here are 10 things you need to safely use X; since I can list them X is actually good." -
@whitequark@RichFelker@int10h There are several constructs. They have their pros and cons. Saying that enums are evil because they use\ -
@whitequark@RichFelker@int10h impl.-defined type is as good as saying that defines are evil because they are not scoped. -
@whitequark@RichFelker@int10h And while at it: saying that C is evil bc it's not safe is as good as saying python is evil bc it's slow.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.