Microsoft Visual Studio 2022 (C++) buggy as hell

[Mr Flibble]

Hi,

It is my unhappy task to report that Microsoft Visual Studio 2022 (C++) is
not fit for purpose (i.e. buggy as hell): I had to downgrade to VS2019
just to get a working debugger. Also experienced ICEs with VS2022.

/Flibble

[JiiPee]

can u give one example of a bug? I use it in my work but did not find
anything major yet.

[Chris M. Thomasson]

I found some oddities in 17.4.1 wrt the IDE, but nothing major.

[Mr Flibble]

Well I would classify a non-working debugger and ICEs are pretty fucking
major.

/Flibble

[Mr Flibble]

I don't have the time to create a test case.

/Flibble

[Öö Tiib]

You are lucky to have vs 22 ... i have only vs 19 ... perhaps because my
own policy to ignore tools and technologies younger than 2 years old
with excuse of immaturity.

[Bonita Montero]

Am 27.11.2022 um 00:30 schrieb Mr Flibble:

> On Sun, 27 Nov 2022 00:33:32 +0200, JiiPee wrote:

>> On 27/11/2022 00:23, Mr Flibble wrote:

>>> Hi,

>>> It is my unhappy task to report that Microsoft Visual Studio 2022 (C++)
>>> is not fit for purpose (i.e. buggy as hell): I had to downgrade to
>>> VS2019 just to get a working debugger. Also experienced ICEs with
>>> VS2022.

>> can u give one example of a bug? I use it in my work but did not find
>> anything major yet.

> I don't have the time to create a test case.

LOL !

[JiiPee]

haha

[Mr Flibble]

What's so funny? It is not my job to fix Visual Studio, I have created
Visual Studio bug reports in the past and, yes, I did create test cases
for those bug reports.

/Flibble

[Bonita Montero]

Am 27.11.2022 um 11:14 schrieb Mr Flibble:

> What's so funny? It is not my job to fix Visual Studio, I have created
> Visual Studio bug reports in the past and, yes, I did create test cases
> for those bug reports.

VC++ bug reports are public. Show me the links.

[Mr Flibble]

I believe I made myself clear that I haven't created a bug report for
VS2022 issues.

/Flibble

[Bonita Montero]

I referred to you past filed bugs.

[Mr Flibble]

Why do you want to view those?

/Flibble

[Bonita Montero]

You don't have filed any bug.

[Mr Flibble]

You are a child if you think saying that will force me to dig up my past
bug reports just to satisfy your curiosity. I don't have to prove myself
to you.

/Flibble

[Bonita Montero]

Am 27.11.2022 um 18:32 schrieb Mr Flibble:

> You are a child if you think saying that will force me to dig up my past
> bug reports just to satisfy your curiosity. I don't have to prove myself
> to you.

You're a liar.

[Mr Flibble]

You're an idiot.

/Flibble

[Bonita Montero]

That's ok if I'm an idiot for you.
But I'm not a liar !

[Mr Flibble]

Neither am I, dear.

/Flibble

[Vir Campestris]

I don't always agree with Bonita, but this time I do.

You're telling us it's so full of bugs you can't use it, but you haven't
filed any reports nor can you tell us what any of them are.

Andy

[Mr Flibble]

As I have said already I don't have the time to create test cases. Do you
even know what a test case is? It is the *least* amount of compilable
code that reproduces the problem. It is not always easy to pare down an
existing codebase into a test case for a bug report especially in the case
of internal compiler errors (ICEs).

Also, as with Bonita, I couldn't give one iota of a fuck as to whether you
believe me or not.

/Flibble

[Vir Campestris]

On 27/11/2022 22:36, Mr Flibble wrote:
> As I have said already I don't have the time to create test cases. Do you

> even know what a test case is? It is the*least* amount of compilable

> code that reproduces the problem. It is not always easy to pare down an
> existing codebase into a test case for a bug report especially in the case
> of internal compiler errors (ICEs).
>

After a career of over 40 years as a professional software engineer -
yes, I have some idea of what a test case is. I think you haven't been
doing this quite so long.

And there are tools which will automate the process. Such as

<https://embed.cs.utah.edu/creduce/>

> Also, as with Bonita, I couldn't give one iota of a fuck as to whether you
> believe me or not.

Ah, perhaps something we can agree on. Except perhaps in the sign?

Andy

[Chris M. Thomasson]

On 11/26/2022 2:23 PM, Mr Flibble wrote:

Ahhh, programming raw opengl is fun! ;^)

https://i.ibb.co/JkL25Nj/ct-work.png

Yes, this is in msvc:

https://i.ibb.co/WpZMSzW/image.png

;^)

[Lynn McGuire]

So VS 2022 worked ok for you ?

Lynn

[Chris M. Thomasson]

So far, so good... Some odd things occurred. For instance if I hit the
'/' character on the keyboard three times in a row fast, it would insert
some, what looked like meta data. Then I deleted it, and hit the '/' key
three times again. It did not insert anything. For some reason, it kind
of seems as if the IDE is using some AI to do some things, automatic
formatting, and shit like that. I went into settings and turned as much
off as I could.

[Chris M. Thomasson]

On 11/28/2022 8:23 PM, Lynn McGuire wrote:

Fwiw, I have a long history with MSVC. 6.0 was pretty interesting, C++
not up to par. But I mainly used it for C. Back on Solaris under
ultrasparcs, I remember using NetBeans.

[Chris M. Thomasson]

On 11/28/2022 8:23 PM, Lynn McGuire wrote:

Another thing that works pretty darn good in MSVC is vcpkg:

https://vcpkg.io/

I was able to just build everything I needed to get modern OpenGL up and
running.

[Lynn McGuire]

My first C compiler was Turbo C from Borland in 1987. Version 1.01 was
great. The IDE was awesome since it used the IDE from Turbo Pascal.

I started using MSVC in 1992 ??? Don't remember what version it was but
it only produced Dos16 and Win16 EXEs and DLLs. Jumped to MSVC6 in 1993
??? to build 32 bit on Windows 93 XX 94 XX 95 (I was an alpha tester).
Jumped to MSVS 2005 in 2005 and MSVS 2015 in 2015 where we are now.

Lynn

[Michael S]

MSVC6 released 1998-09-02
Windows 93 ? Windows 94 ? What are those things?

The first 32-bit Microsoft compiler was indeed released in 1993. It was called Visual C++ 1.0.
It generated code for Windows NT and Win32s. The later was a runtime environment running
on top of Windows 3.1 and 3.11.

[Lynn McGuire]

Windows 93 and 94 were the precursors for Windows 95 which was over two
years late. I got my first diskettes for Windows 93 in 1992.

I guess I got MSVC 1.0 in 1993. I remember Win32s very well.

Lynn

[Mr Flibble]

There was no such thing as Windows 93.

/Flibble

[Lynn McGuire]

I could take a picture of the diskettes but I threw them away years ago.
I got diskettes from MS at least once a month. They were desperately
trying to create more window handles without killing all of the Win16
software out there like mine. Unfortunately, they gave up after a year
or so and shipped Windows 95.

Lynn

[Öö Tiib]

I remember 95 ... it was like 2 boxes of floppies. We installed it on
some computers and experience was rather bad compared to
Windows 3.11 and Windows NT 3.5 that we had used before. During
few months we decided that perhaps it is time to switch mostly to
NT and keep 3.11 and 95 only for testing/debugging of compatibility.
In few years customers also all migrated to NT 3.5 and NT 4 and so
the 95 line did die off.

[Chris M. Thomasson]

On 11/26/2022 3:29 PM, Mr Flibble wrote:

> On Sat, 26 Nov 2022 14:47:44 -0800, Chris M. Thomasson wrote:
>
>> On 11/26/2022 2:23 PM, Mr Flibble wrote:
>>> Hi,
>>>
>>> It is my unhappy task to report that Microsoft Visual Studio 2022 (C++)
>>> is not fit for purpose (i.e. buggy as hell): I had to downgrade to
>>> VS2019 just to get a working debugger. Also experienced ICEs with
>>> VS2022.
>>

>> I found some oddities in 17.4.1 wrt the IDE, but nothing major.
>
> Well I would classify a non-working debugger and ICEs are pretty fucking
> major.

Nothing bad in the debugger, yet. So far so good for my current use cases.