From: Maciej Sobczak <see.my.homepage@gmail.com>
Subject: Re: C++ diaries...
Date: Fri, 7 Jun 2019 00:32:01 -0700 (PDT)
Date: 2019-06-07T00:32:01-07:00 [thread overview]
Message-ID: <60027108-2b92-417e-8083-eef19cc1e64a@googlegroups.com> (raw)
In-Reply-To: <c59e3544-9e72-42f6-b90b-5b03859c4e64@googlegroups.com>
> ... now changing my 'burning genuine enums' for new 'enum classes' is breaking old code at 52 spots (from that change uses of enums as integer based index becomes illegal and need to be 'static_casted' to work) ... so much for productivity.
You would be much more productive if you used non-clashing constant names. Actually, that would be even faster than writing these posts here. :-D
And you might be more likely to stay in line with those coding standards that actually forbid enumeration overloading.
Which brings another question: what is the problem, actually? The fact that old enums don't support overloading, the fact that transitioning to new language features requires changes in old code or the fact that there are two kinds of enums in the first place? I agree that this third fact is somewhat cumbersome, but since there is no obligation to use the new one, it should not be a show stopper.
--
Maciej Sobczak * http://www.inspirel.com
next prev parent reply other threads:[~2019-06-07 7:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 16:32 C++ diaries Olivier Henley
2019-06-06 16:54 ` Olivier Henley
2019-06-07 7:32 ` Maciej Sobczak [this message]
2019-06-07 17:55 ` Olivier Henley
2019-06-07 18:22 ` Keith Thompson
2019-06-07 23:04 ` Olivier Henley
2019-06-07 23:09 ` Keith Thompson
2019-06-07 18:29 ` Lucretia
2019-06-07 23:27 ` Olivier Henley
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox