Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Elvis Stansvik
Den sön 22 jan. 2023 kl 23:08 skrev Elvis Stansvik : > > > MSVC not-the-latest: are you using it? why? > > Yes, using VS 2019. > > I can only speak for us, but we simply haven't had any really > compelling reason to upgrade our compiler. > > Turning the question around: If you have no need for the

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Elvis Stansvik
> MSVC not-the-latest: are you using it? why? Yes, using VS 2019. I can only speak for us, but we simply haven't had any really compelling reason to upgrade our compiler. Turning the question around: If you have no need for the features/improvements that a newer compiler would bring, why would y

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Thiago Macieira
On Sunday, 22 January 2023 08:33:43 PST coroberti wrote: > On some update of MSVC-2017 to their next minor release, we got their > optimization bug. > It was a waste of time to understand what happened and to work-around it. That just means you had to downgrade to the previous minor version of 201

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Lisandro Damián Nicanor Pérez Meyer
Hi, On Sun, 22 Jan 2023 at 14:28, Philippe wrote: > > > Medical devices/software would need to go through a whole set of > > revalidation if the compiler changes > > This is understandable, but then logic would like it to be the same for > the use of any new version of the Qt framework. That's a

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Philippe
> Medical devices/software would need to go through a whole set of > revalidation if the compiler changes This is understandable, but then logic would like it to be the same for the use of any new version of the Qt framework. Personnaly, I find more bugs in Qt releases than in the compiler releas

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Lisandro Damián Nicanor Pérez Meyer
On Sun, 22 Jan 2023 at 13:18, Thiago Macieira wrote: > > In this case, MSVC 2019, which is still supported. > > I'm trying to understand why people don't upgrade their Visual Studios. In the > past, they used to use different and binary-incompatible VC runtimes, so large > projects often needed to

Re: [Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread coroberti
Hi Thiago, On some update of MSVC-2017 to their next minor release, we got their optimization bug. It was a waste of time to understand what happened and to work-around it. jm2c Kind regards, Robert On Sun, Jan 22, 2023 at 6:19 PM Thiago Macieira wrote: > > In this case, MSVC 2019, which is sti

[Interest] MSVC not-the-latest: are you using it? why?

2023-01-22 Thread Thiago Macieira
In this case, MSVC 2019, which is still supported. I'm trying to understand why people don't upgrade their Visual Studios. In the past, they used to use different and binary-incompatible VC runtimes, so large projects often needed to stick to a single version because of different teams needing