public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, osde@linux.microsoft.com, afish@apple.com,
	ehaouas@noos.fr
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH] Use C99 flexible arrays
Date: Thu, 24 Aug 2023 15:01:23 -0600	[thread overview]
Message-ID: <37b87f01-1acf-a048-058e-3acaa78fe623@bsdio.com> (raw)
In-Reply-To: <18c7835a-b271-459a-86a1-0f67042ddbeb@linux.microsoft.com>

I'd support that. That would leave us with VS2017, VS2019 and VS2022.


-- 

Rebecca Cran


On 8/24/23 09:19, Oliver Smith-Denny wrote:
> On 8/23/2023 2:41 PM, Rebecca Cran wrote:
>> With Visual Studio 2019 adding C11 and C17 support as first-class 
>> features, I think we should be safe nowadays to rely on them. But we 
>> should check if older versions that we still support (VS 2015 etc.) 
>> support them too.
>>
>> https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/ 
>>
>>
>>
>
> Perhaps this is a worthwhile time to drop VS 2015 and support VS 2022?
>
> Oliver
>
>
> 
>
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108022): https://edk2.groups.io/g/devel/message/108022
Mute This Topic: https://groups.io/mt/100861513/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-08-24 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 16:56 [edk2-devel] [PATCH] Use C99 flexible arrays ehaouas
2023-08-22 15:28 ` Andrew Fish via groups.io
2023-08-23 21:41   ` Rebecca Cran
2023-08-24  0:36     ` Pedro Falcato
2023-08-24 21:03       ` Rebecca Cran
2023-08-24 15:19     ` Oliver Smith-Denny
2023-08-24 21:01       ` Rebecca Cran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-20 11:07 Elyes Haouas
2023-08-21 14:32 ` Yao, Jiewen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37b87f01-1acf-a048-058e-3acaa78fe623@bsdio.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox