blocks|key|29446|text|嗯，这是一个相当困难的问题。事实上，MSVC不支持最新的C标准，关于它的c%2B%2B遵从性，我可以告诉你任何事情。然而，MSVC和gcc都理解"windows“C，你就是不能指望另一种方式。例如，如果你使用美国国家标准协会的C99功能，那么你可能会很难从gcc“移植”到微软的to。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29447|但只要你尝试MSVC->+gcc的方式，你的机会就会更大。你唯一需要注意的是库。Windows上的大多数库都应该与MSVC一起工作，所以你需要一些额外的工具来使它们也能被gcc访问。|29448|LCC是一个相当老的系统，AFAIKT不太支持ANSI+C99，它也需要MSVC的工具才能正常工作。LCC“仅仅”是一个编译器。|29449|Win32是一个C开发系统，致力于兼容ANSI+C99。它与链接器、IDE等一起出现。|29450|我不能说出数字Mars的实施情况|29451|然后还有Pelles-C，它也是一个完全成熟的IDE。|29452|我们在OpenWatcom周围闲逛。这曾经是一个相当不错的系统，但我不能说它有多符合。|29453|总而言之，“最好的”你可以希望从MSVC+->其他系统更容易的方式，但它可能会更糟糕的另一种方式。|29454|问候弗里德里希|29455|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Well this is a quite difficult question. Fact is that MSVC does not support the newest
C standard, about it's c++ compliance I can tell you anyything. Howerver "windows" C is understand by both MSVC and gcc you just can not hope for the other way. E.g if you use ANSI C99 features then you might have a hard time "porting" from gcc to MSVC. 

But as long as you try the way MSVC-> gcc you chances will be better. The only point you have to be aware of is the libraries. Most of the libraries on Windows are supposed to work with MSVC and so you need some extra tools to make them accessible to gcc also.

LCC is a quite older system,which AFAIKT does not support much from ANSI C99, it also needs tools from MSVC to work properly. LCC is "just " a compiler. 

lcc-win32 is a C Development system striving to be ANSI C99 compliant. It comes along with linker, IDE etc. 

I can not tell about the state of Digital Mars implementation

Then there is also Pelles-C which is a fully fledged IDE also.

And we have hanging around OpenWatcom. Which once was quite a decent system but I can't tell how conformant it is.

All in all the "best" you can hope for the easier way from MSVC -> other system but it will probably be much worse the other way round.

Regards
Friedrich

blocks|key|878315|text|当尝试将为MSVC编写的代码编译到其他编译器时，首先要做的是在关闭Microsoft扩展的情况下编译它。(我想应该使用/Za标志)。这会让很多事情烟消云散，而GCC和其他编译器会抱怨这些事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878316|下一步是确保特定于Windows的API+(MFC、Win32等)被隔离在特定于windows的文件中，有效地将代码划分为“通用”和“特定于windows”的模块。|878317|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The first thing to do when trying to compile code written for MSVC to other compilers is to compile it with Microsoft-extensions switched off. (Use the /Za flag, I think). That will smoke out lots of things which GCC and other compilers will complain about.

The next step is to make sure that Windows-specific APIs (MFC, Win32, etc.) are isolated in Windows-specific files, effectively partioning your code into "generic" and "windows-specific" modules.

blocks|key|29538|text|还记得这样的争论吗?如果你想让你的网页在不同的浏览器上工作，那么你就应该编写符合标准的HTML。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29539|编译器也是如此。|29540|在语言层面，如果您的代码在使用-std=c89+(或C%2B%2B的-std=c%2B%2B98+)、-pedantic+-Wall和-Wextra的GCC平台上编译时没有任何警告，而且只要您没有使用过-pedantic允许的任何更明显的GNU扩展(这很难意外地做到)，那么它很有可能在大多数C89编译器上运行。C%2B%2B就不那么确定了，因为您可能依赖于目标编译器对该标准的支持程度。|29541|编写正确的C89有一定的限制(没有//注释，声明必须在一个块中的语句之前，没有inline关键字，没有stdint.h，因此没有64位类型，等等)，但一旦你习惯了，这并不是太糟糕。如果你只关心GCC和MSVC，你可以打开MSVC有的一些语言特性。否则，您可以编写自己的小“语言抽象”头文件。例如，在GCC和MSVC/C%2B%2B上将"inline“定义为"inline”，而在MSVC/C+%2B%2B上定义"__inline“，或者MSVC+stdint.h很容易找到或编写。|29542|我过去成功地写过可移植的代码--我主要是在一个平台上工作，使用的是一个特定产品的平台，使用的是GCC。我还编写了适用于所有平台的代码，包括Windows+XP和Mobile。在构建服务器上运行“测试构建”之前，我从未为这些平台编译过它，而且我很少遇到任何问题。我想我可能写了一两次触发64位兼容性警告的糟糕代码。|29543|Windows程序员走另一条路导致了偶尔的问题，主要是因为他们的编译器没有我们那么书呆子气，所以我们看到了他们不支持的警告，而不是GCC根本不支持的东西。但修复警告意味着，当代码稍后在具有更多原始编译器的系统上使用时，它仍然可以工作。|29544|在库级别，这要困难得多。如果你通过windows.h+#include和使用windows.h，那么很明显它不会在linux上工作，如果你和GCC一起使用KDE，然后尝试用MSVC编译，情况也是一样。|29545|严格地说，这是一个平台问题，而不是编译器问题，但它等同于同一件事。如果您想要编写可移植的代码，则需要一个操作系统抽象API，如POSIX+(或其子集)，所有目标都支持它，并且在编写它时，首先需要考虑“可移植性”。使用大量使用特定于windows的API的代码，并试图使其在GCC/linux上工作，基本上是完全重写AFIAK。使用WINE可能比尝试重新编译它更好。|29546|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

Remember the argument that if you want your web page to work on different browsers, then you should write standards-compliant HTML?

Same goes for compilers.

At the language level, if your code compiles without warnings on GCC with -std=c89 (or -std=c++98 for C++), -pedantic -Wall, plus -Wextra if you're feeling brave, and as long as you haven't used any of the more blatant GNU extensions permitted by -pedantic (which are hard to do accidentally) then it has a good chance of working on most C89 compilers. C++ is a bit less certain, as you're potentially relying on how complete the target compiler's support is for the standard.

Writing correct C89 is somewhat restrictive (no // comments, declarations must precede statements in a block, no inline keyword, no stdint.h and hence no 64bit types, etc), but it's not too bad once you get used to it. If all you care about is GCC and MSVC, you can switch on some language features you know MSVC has. Otherwise you can write little "language abstraction" headers of your own. For instance, one which defines "inline" as "inline" on GCC and MSVC/C++, but "__inline" for MSVC/C. Or a MSVC stdint.h is easy enough to find or write.

I've written portable code successfully in the past - I was working mostly on one platform for a particular product, using GCC. I also wrote code that was for use on all platforms, including Windows XP and Mobile. I never compiled it for those platforms prior to running a "test build" on the build server, and I very rarely had any problems. I think I might have written bad code that triggered the 64bit compatibility warning once or twice.

The Windows programmers going the other way caused the occasional problem, mostly because their compiler was less pedantic than ours, so we saw warnings they didn't, rather than things that GCC didn't support at all. But fixing the warnings meant that when the code was later used on systems with more primitive compilers, it still worked.

At the library level, it's much more difficult. If you #include and use Windows APIs via windows.h, then obviously it's not going to work on linux, and the same if you use KDE with GCC and then try to compile with MSVC. 

Strictly speaking that's a platform issue, not a compiler issue, but it amounts to the same thing. If you want to write portable code, you need an OS abstraction API, like POSIX (or a subset thereof) that all your targets support, and you need to be thinking "portable" when you write it in the first place. Taking code which makes heavy use of windows-specific APIs, and trying to get it to work on GCC/linux, is basically a complete rewrite AFIAK. You might be better off with WINE than trying to re-compile it.

blocks|key|3251603|text|你把“编译器”和"OSs“搞混了。不是MSVC+C编译器带来的东西:它是Windows+API的C特定实现。您可以从Visual+Studio独立获得它。任何其他Windows上的C编译器都可能提供它。例如，在Linux端，您可以使用、和其他工具。它们不是GCC的重要组成部分，任何其他为Linux编译的编译器都会提供它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3251604|所以你需要回答两个不同的问题:我如何才能以一种任何编译器都能接受的方式编写C代码？我如何隐藏我对操作系统的依赖关系？|3251605|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You're mixing up "compilers" and "OSs". &lt;windows.h&gt; is not something that MSVC C compiler brings to the table: it's C-specific embodiment of Windows API. You can get it independently from Visual Studio. Any other C compiler on Windows is likely to provide it. On the Linux side, for example, you have &lt;unistd.h&gt;, &lt;pthereads.h&gt; and others. They are not an essential part of GCC, and any other compiler that compiles for Linux would provide them.

So you need to answer two different questions: how can I code C in such a way that any compiler accepts it? And how do I hide my dependencies on OS?

blocks|key|878440|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|878441|用Visual+C/C%2B%2B+2005/2008编写的程序可能无法使用其他编译器(如GNU+C/C%2B%2B+)编译，反之亦然。|blockquote|878442|878443|878444|如果您(1)使用了某种在一个编译器中可用但在另一个编译器中不可用的扩展(例如，C%2B%2B标准在一些地方要求typename和template关键字，但许多编译器--包括Visual+C%2B%2B不强制执行这一点；gcc过去也不强制执行这一点，但是changed+in+3.4)或者(2)使用在一个编译器上实现但不在另一个编译器上实现的符合标准的行为(目前这种情况的典型代表是导出模板，但只有一两个编译器支持这一点，而Visual+C%2B%2B和gcc不在那个组中)，就是这样。|offset|length|style|CODE|878445|例如，当试图重用代码时，|878446|使用windows.h，为一个特定的编译器编写，|878447|878448|878449|我从来没有见过这样做的问题。我在使用微软的windows.h的时候发现了一个问题，就是在gcc。但是当我在gcc中使用gcc的windows.h，在Visual+C%2B%2B中使用微软的windows.h时，我可以访问所有文档中的函数。这毕竟是“实现的windows.h”的定义。|878450|878451|需要注意的区别是什么？|878452|878453|878454|我看到的主要问题是人们不知道上面提到的依赖template/typename的事情。我觉得有趣的是，许多人认为gcc不够聪明，不能做Visual+C%2B%2B所做的事情，而实际上，gcc首先拥有这个功能，然后以符合标准的名义决定删除它。|878455|在不久的将来，您将在使用C%2B%2B0x功能时遇到问题。但是，在该标准中，gcc和Visual+C%2B%2B都实现了更简单的东西。|878456|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/gcc/bugs.html#new34^0|0|0|0|0|1F|8|1O|8|3A|E|0|0|0|0|0|0|0|0|0|0|0|L|8|U|8|0|0^^$0|@$1|2|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1B|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|1E|7|@$H|1F|I|1G|J|K]|$H|1H|I|1I|J|K]]|8|@$H|1J|I|1K|1|1L]]|9|$]]|$1|L|3|M|4|5|6|1M|7|@]|8|@]|9|$]]|$1|N|3|O|4|C|6|1N|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|1O|7|@]|8|@]|9|$]]|$1|Q|3|-4|4|5|6|1P|7|@]|8|@]|9|$]]|$1|R|3|S|4|5|6|1Q|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|1R|7|@]|8|@]|9|$]]|$1|U|3|V|4|C|6|1S|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|1T|7|@]|8|@]|9|$]]|$1|X|3|-4|4|5|6|1U|7|@]|8|@]|9|$]]|$1|Y|3|Z|4|5|6|1V|7|@$H|1W|I|1X|J|K]|$H|1Y|I|1Z|J|K]]|8|@]|9|$]]|$1|10|3|11|4|5|6|20|7|@]|8|@]|9|$]]|$1|12|3|-4|4|5|6|21|7|@]|8|@]|9|$]]]|13|$14|$4|15|16|17|9|$18|19]]]]

<blockquote>
 A program written in Visual C/C++ 2005/2008 might not compile with another compiler such as GNU C/C++ or vice-versa.
</blockquote>

This is true if you either (1) use some sort of extension available in one compiler but not another (the C++ standard, for instance requires the <code>typename</code> and <code>template</code> keywords in a few places but many compilers -- including Visual C++ don't enforce this; gcc used to not enforce this either, but <a href="http://www.gnu.org/software/gcc/bugs.html#new34" rel="nofollow noreferrer">changed in 3.4</a>) or (2) use some standard compliant behavior implemented on one compiler but not another (right now the poster boy for this is exported templates, but only one or two compilers support this, and Visual C++ and gcc are not in that group).

<blockquote>
 For example when trying to reuse code, which uses windows.h, written for a particular compiler with another,
</blockquote>

I've never seen a problem doing this. I have seen a problem using Microsoft's windows.h in gcc. But when I use gcc's windows.h in gcc and Microsoft's windows.h in Visual C++ I have access to all of the documented functions. That's the definitions of "implemented windows.h" after all.

<blockquote>
 what are the differences to be aware of?
</blockquote>

The main one I've seen is people not knowing about the dependent <code>template</code>/<code>typename</code> thing mentioned above. I find it funny that a number of people think gcc is not smart enough to do what Visual C++ does, when in reality gcc had the feature first and then decided to remove it in the name of standards compliance.

In the near future you will run into problems using C++0x features. But both gcc and Visual C++ have implemented the easier things in that standard.

blocks|key|29822|text|正如您可以从不同的答案中看出的那样，这个主题相当复杂。考虑到这一点，这里是我最近将一些代码移植到三个平台(MSVC8/Windows4.2/Linux，gcc+3.4/嵌入式ARM9处理器)时遇到的一些问题。它最初只在Visual+Studio2005下编译。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29823|a)在Windows平台上编写的许多代码都使用windows.h中定义的类型。我不得不创建一个包含以下内容的"windows_types.h“文件：|29824|#ifndef+_WIN32
++++typedef+short++++++++++++++INT16;
++++typedef+unsigned+short+++++UINT16;
++++typedef+int++++++++++++++++INT32;
++++typedef+unsigned+int+++++++UINT32;
++++typedef+unsigned+char++++++UCHAR;
++++typedef+unsigned+long+long+UINT64;
++++typedef+long+long++++++++++INT64;
++++typedef+unsigned+char++++++BYTE;
++++typedef+unsigned+short+++++WORD;
++++typedef+unsigned+long++++++DWORD;
++++typedef+void+*+++++++++++++HANDLE;
++++typedef+long+++++++++++++++LONG;
#endif|code-block|syntax|javascript|29825|虽然很难看，但比起修改以前只针对Windows的代码要容易得多。|29826|b)在模板代码中声明类型时不需要typename关键字。MSVC在这方面是松懈的(尽管我假设某些编译器开关会生成一个警告)。我不得不在很多地方添加它。|29827|c)简单，但耗时:+Windows不区分大小写，许多#included文件被指定为不正确的大小写，导致在Linux下出现问题。|29828|d)有相当多的代码使用Windows+API来做很多事情。CRITICAL_SECTIONS和INTERLOCKED_INCREMENT就是一个例子。我们使用了尽可能多的boost库来替换这些问题，但是重新编写代码非常耗时。|29829|e)很多代码都依赖于包含在预编译头中的头。我们在gcc3.4上使用pch时遇到了问题，所以我们必须确保所有的.h/cpp文件都正确地包含了它们的所有依赖项(正如它们一开始就应该包含的那样)。|29830|f)+VS2005有两个令人讨厌的bug。允许将auto_ptr's+can+be+assigned+to+anything和临时变量传递给引用参数。两者都无法编译(谢天谢地！)在gcc的指导下，但需要返工。|offset|length|29831|g)奇怪的是，我们的模板代码试图显式地专门化类模板函数。不允许。gcc再一次拒绝，VS+2005放手一旦了解了问题，就可以很容易地将其返工为常规的重载。|29832|h)在VS+2005+std::exception下，允许使用字符串构造异常。在gcc或标准下是不允许的。重新编写代码，以便首选使用其中一个派生的异常类。|29833|希望这就是你想要的信息！|29834|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/270347/replacing-autoptr-in-vc-8^0|0|0|0|0|0|0|0|0|O|12|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@]|9|@$U|1J|V|1K|1|1L]]|A|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1O|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

As you can tell from the diverse answers, this topic is fairly involved. Bearing that in mind here are some of the issues I faced when recently porting some code to target three platforms (msvc 8/Windows, gcc 4.2/Linux, gcc 3.4/embedded ARM9 processor). It was originally only compiling under Visual Studio 2005.

a) Much code that's written on the Windows platforms uses types defined in windows.h. I've had to create a "windows_types.h" file with the following in it:

<pre><code>#ifndef _WIN32
 typedef short INT16;
 typedef unsigned short UINT16;
 typedef int INT32;
 typedef unsigned int UINT32;
 typedef unsigned char UCHAR;
 typedef unsigned long long UINT64;
 typedef long long INT64;
 typedef unsigned char BYTE;
 typedef unsigned short WORD;
 typedef unsigned long DWORD;
 typedef void * HANDLE;
 typedef long LONG;
#endif
</code></pre>

Ugly, but much easier than modifying the code that, previously, was only targeting Windows.

b) The typename keyword was not required in templated code to declare types. MSVC is lax in this regard (though I assume certain compiler switches would have generated a warning). Had to add it in a number of places.

c) Simple, but time-consuming: Windows is not case sensitive and many #included files were specified with incorrect case causing problems under Linux.

d) There was a fair chunk of code using the Windows API for many things. An example was for CRITICAL_SECTIONS and INTERLOCKED_INCREMENT. We used the boost libraries as much as possible to replace these issues but reworking code is time-consuming. 

e) A lot of the code relied on headers being included in precompiled headers. We had issues with using pch on gcc3.4 so we had to ensure that all .h/cpp files correctly included all their dependencies (as they should have in the first place).

f) VS 2005 has two nasty bugs. <a href="https://stackoverflow.com/questions/270347/replacing-autoptr-in-vc-8">auto_ptr's can be assigned to anything</a> and temporary variables are allowed to be passed to reference parameters. Both fail to compile (thankfully!) under gcc but rework is required.

g) Bizarrely, we had template code that was trying to explicitly specialise class template functions. Not allowed. Again gcc refused, VS 2005 let it go. Easy enough to rework into regular overloads once the problem is understood.

h) Under VS 2005 std::exception is allowed to be constructed with a string. Not allowed under gcc or the standard. Rework your code to prefer to use one of the derived exception classes.

Hopefully that's the kind of information you were looking for!

blocks|key|3251834|text|与2005年相比，vs2008更符合标准。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3251835|相反，我遇到了更多的问题，特别是gcc的“特性”，它允许你在运行时分配一个大小可变的数组"int+arrayvariable“，这是纯粹的邪恶。|3251836|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

vs2008 is a lot more standards compliant than 2005. 
I have had more problems going the other way, especially the 'feature' of gcc that lets you allocate an array with a variable size at run time "int array[variable]" which is just pure evil.

A program written in Visual C/C++ 2005/2008 might not compile with another compiler such as GNU C/C++ or vice-versa. For example when trying to reuse code, which uses windows.h, written for a particular compiler with another, what are the differences to be aware of?

Is there any information about how to produce code which is compatible with either one compiler or another e.g. with either GC/C++ or MSVC/C++? What problems will attempting to do this cause?

What about other compilers, such as LCC and Digital Mars?

What are the practical differences between C compilers on Windows?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

用Visual C/C++ 2005/2008编写的程序可能无法使用其他编译器(如GNU C/C++ )编译，反之亦然。例如，当试图重用使用windows.h的代码时，这些代码是为一个特定编译器编写的，需要注意哪些区别？有没有关于如何生成与一个或另一个编译器兼容的代码的信息，例如，GC/C++或MSVC/C++？尝试这...

问Windows上的C编译器之间的实际区别是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Windows上的C编译器之间的实际区别是什么？EN