Marc-André Lureau writes:
> Hi
>
> On Fri, Dec 8, 2017 at 8:50 AM, Markus Armbruster wrote:
>> Marc-André Lureau writes:
>>
>>> On Thu, Dec 7, 2017 at 5:23 PM, Markus Armbruster wrote:
Marc-André Lureau writes:
> The C standard has the initial value at 0 and the subsequent value
Hi
On Fri, Dec 8, 2017 at 8:50 AM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> On Thu, Dec 7, 2017 at 5:23 PM, Markus Armbruster wrote:
>>> Marc-André Lureau writes:
>>>
The C standard has the initial value at 0 and the subsequent values
incremented by 1. No need to set
Marc-André Lureau writes:
> On Thu, Dec 7, 2017 at 5:23 PM, Markus Armbruster wrote:
>> Marc-André Lureau writes:
>>
>>> The C standard has the initial value at 0 and the subsequent values
>>> incremented by 1. No need to set this explicitely.
>>>
>>> This will prevent from artificial "gaps" wh
On Thu, Dec 7, 2017 at 5:23 PM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> The C standard has the initial value at 0 and the subsequent values
>> incremented by 1. No need to set this explicitely.
>>
>> This will prevent from artificial "gaps" when compiling out some enum
>> values
Marc-André Lureau writes:
> The C standard has the initial value at 0 and the subsequent values
> incremented by 1. No need to set this explicitely.
>
> This will prevent from artificial "gaps" when compiling out some enum
> values and having unnecessarily large MAX values & enums arrays.
>
> Sig