Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Thiago Adams <thiago.adams@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: enum sets
Date: Thu, 29 Aug 2024 08:38:56 -0300
Organization: A noiseless patient Spider
Lines: 42
Message-ID: <vapmkg$3ullf$4@dont-email.me>
References: <vaoclb$3lfbf$1@dont-email.me>
 <vapbid$3tb2u$1@raubtier-asyl.eternal-september.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 29 Aug 2024 13:38:56 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f80b8b85f3cf443035f3bd640f6489b4";
	logging-data="4150959"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX180MB3Db20LrL2IiiYx80z3KCBzHgbDYm4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:cYwpRyWlUt0LPVltlmIn6CHo3mk=
In-Reply-To: <vapbid$3tb2u$1@raubtier-asyl.eternal-september.org>
Content-Language: en-US
Bytes: 2020

On 29/08/2024 05:30, Bonita Montero wrote:
> Am 29.08.2024 um 01:42 schrieb Thiago Adams:
>> I am wondering how useful would be to have enum sets.
>>
>> Let´s say you have a function that accepts only monospaced fonts.Then 
>> you can use enum monospaced_font_type. Or a switch case where you need 
>> to check all and only monospaced_font_type.
>>
>> But at same type you can store at same object monospaced_font_type or 
>> font_type.
>>
>> enum font_type
>> {
>>      enum monospaced_font_type
>>      {
>>          CASCADIA_FONT,
>>      },
>>      ARIAL_FONT
>> };
>>
>> This could be arranged in any way.
>>
>>
> 
> Use C++:
> 
> struct font_type
> {
>      struct monospaced_font_type
>      {
>          static constexpr int CASCADIA_FONT = 123;
>      };
>      static constexpr int ARIAL_FONT = 456;
> 
> };
> 
> 

It would not help the switch case warnings.