Support Board

Date/Time: Thu, 09 May 2024 10:46:47 +0000

Post From: Visual C++ Compiler error with v1460 or above, but no problem with v1453

[2016-10-14 09:05:48] Link To Thread - Link To Post [Go To First Post]
bjohnson777 (Brett Johnson) - Posts: 284
Trying to get back into programming after a family emergency... the broken compiler in wine was most unpleasant. Reading other posts similar to this, M$VC++ should have been delayed until that remote compile thing can be deployed. Beating my win7 dual boot to also exist in a VM, I got it all installed. I had to install m$.net 4.6 at around 800 megs (win7 only comes with 3.5) just to run the M$VC++ installer. M$VC++ took another 4.2g for around 5g total. The previous compiler took around 250megs of disk space. From the commoner's point of view (who mostly write very little code or just compile someone else's), how is this an improvement??? A warning about versions and required disk space should also be posted. It is not surprising when using a different compiler, that code will not compile and requires some changes, usually improvements, in order to get it to compile. This is completely expected. This is a very important statement y'all made. Getting locked into a M$ specific compiler, even when writing ANSI compliant code, will make moving SC cross platform that much more difficult. M$ has a history of "doing their own thing" with long established standards. Please consider this very carefully.