blocks|key|1027384|text|是的，尤其是如果你计划在多个平台上分发你的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1027385|但是，即使您不跨平台开发也是一种面向未来的形式；如果它现在运行在多个(不同的)平台上，那么它更有可能在未来的平台上运行，而不是被调优、that和专门用于供应商X的Q系列机器(补丁级别1452)的7.8.3版全新安装。|1027386|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|$]]

Yes, especially if you plan to distribute your code for multiple platforms.

But even if you don't cross platform development is a form of futureproofing; if it runs on multiple (diverse) platforms today, it's more likely to run on future platforms than something that was tuned, tweeked, and specialized to work on a version 7.8.3 clean install of vendor X's Q-series boxes (patch level 1452) and nothing else.

blocks|key|3167483|text|使用不同的编译器和不同的操作系统查找并简单地防止bug似乎是有好处的。不同的CPU可以提早确定字节顺序问题。如果您想在GUI级别停留在本机级别，那么这将是一个痛苦的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3167484|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There seems to be a benefit in finding and simply preventing bugs with a different compiler and a different OS. Different CPUs can pin down endian issues early. There is the pain at the GUI level if you want to stay native at that level.

blocks|key|3167492|text|简短的回答是:是的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3167493|除非克隆磁盘，否则几乎不可能使两个系统完全相同，因此您最终将在“不同的平台”上运行，无论您是否有意。通过专门面对和解决“如果系统A不像B那样做事情怎么办？”直面问题你更有可能找到你的代码所做的那些关键假设。|3167494|也就是说，我会说你应该让你的大量基础代码在系统A上工作，然后花一天(或者一周或者……)并让它在系统B上运行。它可以非常有教育意义。|3167495|我的教育回到了80年代，当时我将一个源代码C级调试器移植到了100多种风格的U*NX上。加克！|3167496|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Short answer: Yes.

Short of cloning a disk, it is almost impossible to make two systems exactly alike, so you are going to end up running on "different platforms" whether you meant to or not. By specifically confronting and solving the "what if system A doesn't do things like B?" problem head on you are much more likely to find those key assumptions your code makes.

That said, I would say you should get a good chunk of your base code working on system A, and then take a day (or a week or ...) and get it running on system B. It can be very educational.

My education came back in the 80's when I ported a source level C debugger to over 100 flavors of U*NX. Gack!

blocks|key|851594|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|851595|在两个或更多不同的平台上开发应用程序是否有好处？|blockquote|851596|851597|851598|如果这是生产软件，显而易见的原因是更大的客户群的诱惑。当客户听说你支持多个平台时，你的产品的吸引力就被放大了。请记住，大多数企业不使用单一操作系统，甚至不使用单一版本的操作系统。这是相当典型的找到一个部分使用Windows，另一个Mac和一个较小的版本一些风格的Linux。|851599|还可以看到，为单一平台定制产品通常比在多平台上运行要乏味得多。收益递减的规律甚至在你知道之前就开始了。|851600|当然，如果您正在为客户专有硬件的现有产品进行定制工作，那么所有这些都没有什么意义。但即便如此，也要密切关注客户的所有硬件--您永远不知道他什么时候会提出要求。|851601|851602|在相同的平台上使用不同的编译器有好处吗？|851603|851604|851605|是的，再来一次。不同的编译器实现不同的扩展。请确保您不依赖于特定编译器的特定版本。|851606|此外，编译器本身可能有一两个bug。使用多个编译器可以帮助解决这些问题。|851607|我还看到一些使用两种不同编译器的(跨平台)产品--一种是在那些需要非常高精度的浮点操作的模块中使用的。(有一段时间我听到其他人这么做了，但是...)|851608|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Z|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|11|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|12|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|13|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|14|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|M|3|N|4|C|6|16|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|18|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|19|7|@]|8|@]|9|$]]|$1|S|3|T|4|5|6|1A|7|@]|8|@]|9|$]]|$1|U|3|V|4|5|6|1B|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]]|X|$]]

<blockquote>
 Are there benefits to developing an application on two or more different platforms?
</blockquote>

If this is production software, the obvious reason is the lure of a larger client base. Your product's appeal is magnified the moment the client hears that you support multiple platforms. Remember, most enterprises do not use a single OS or even a single version of the OS. It is fairly typical to find a section using Windows, another Mac and a smaller version some flavor of Linux. 

It is also seen that customizing a product for a single platform is often far more tedious than to have it run on multi-platform. The law of diminishing returns kicks in even before you know.

Of course, all of this makes little sense, if you are doing customization work for an existing product for the client's proprietary hardware. But even then, keep an eye out for the entire range of hardware your client has in his repertoire -- you never know when he might ask for it.

<blockquote>
 Does using a different compiler on even the same platform have benefits?
</blockquote>

Yes, again. Different compilers implement different extensions. See to it that you are not dependent on a particular version of a particular compiler.

Further, there may be a bug or two in the compiler itself. Using multiple compilers helps sort these out.

I have further seen bits of a (cross-platform) product using two different compilers -- one was to used in those modules where floating point manipulation required a very high level of accuracy. (Been a while I've heard anyone else do that, but ...)

blocks|key|851638|text|我已经将一个最初是Win32的大型C%2B%2B程序移植到了Linux上。这并不是很难。主要是处理编译器的不兼容性，因为当时的MS+C%2B%2B编译器在各种方面都是不兼容的。我希望这个问题现在已经基本解决了(直到C%2B%2B0x特性开始逐渐出现)。还编写了一个简单的平台抽象库，将特定于平台的代码集中在一个地方。这取决于您在多大程度上依赖于操作系统中的服务，而这些服务在新平台上很难模仿。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|851639|您不必从头开始构建可移植性。这就是为什么“移植”经常被描述为在你最重要的平台上发布初始版本后，你可以一次完成的活动。你不需要从一开始就一直这样做。纯粹出于经济原因，如果你可以避免做可能永远不会有回报的工作，显然你应该这样做。后来，当确实需要移植时，移植的成本被证明并不是那么糟糕。|851640|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|$]]

I've ported a large C++ program, originally Win32, to Linux. It wasn't very difficult. Mostly dealing with compiler incompatibilities, because the MS C++ compiler at the time was non-compliant in various ways. I expect that problem has mostly gone now (until C++0x features start gradually appearing). Also writing a simple platform abstraction library to centralize the platform-specific code in one place. It depends to what extent you are dependent on services from the OS that would be hard to mimic on a new platform.

You don't have to build portability in from the ground up. That's why "porting" is often described as an activity you can perform in one shot after an initial release on your most important platform. You don't have to do it continuously from the very start. Purely for economic reasons, if you can avoid doing work that may never pay off, obviously you should. The cost of porting later on, when really necessary, turns out to be not that bad.

blocks|key|851684|text|大多数情况下，有一个现有的平台，应用程序是为其编写的(单个软件)。但是如果你决定提供一种独立的语言，你就会更多的开发人员(两个平台)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|851685|此外，面向中小企业的产品(标准软件、)如果在不同的平台上运行，可以更好地销售！您可以同时访问这两个市场，WIN&LINUX！(还有MacOSx等等……)|851686|大公司大多购买由产品供应商支持/认证的硬件，只是为了部署指定的产品。|851687|entityMap^0|R|4|0|D|5|V|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

Mostly, there is an existing platform where the application is written for (individual software). But you adress more developers (both platforms), if you decide to provide an independent language.

Also products (standard software) for SMEs can be sold better if they run on different platforms! You can gain access to both markets, WIN&amp;LINUX! (and MacOSx and so on...)

Big companies mostly buy hardware which is supported/certified by the product vendor only to deploy the specified product.

blocks|key|4635051|text|如果您同时在多个平台上进行开发，您将获得能够使用不同工具的优势。例如，我曾经有一次内存覆盖(我仍然发誓我不需要空字节的%2B1！)这会导致“自由”崩溃。我在Windows上提高了代码的速度，并且发现Rational+Purify在大约1分钟内就覆盖了代码。我在Linux下花了一周的时间才找到它(valgrind可能已经找到了……但我当时并不知道)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4635052|对我来说，在相同或不同平台上的不同编译器是必须的，因为每个编译器都会报告不同的事情，有时一个编译器关于错误的报告会是胡言乱语，但另一个编译器却非常清楚。|4635053|在开发时使用像多个数据库这样的东西意味着你不太可能将自己绑定到一个特定的数据库，这意味着如果有理由的话，你可以换出这个数据库。例如，如果您想要将使用Oracle的东西集成到使用SQL+Server的现有基础架构中，这将非常糟糕-如果Oracle或SQL+Server部分可以移动到其他系统，效果会更好(我知道有些地方的财务系统有3个不同的数据库……ick)。|4635054|一般来说，总是为两三件事开发意味着你发现错误的几率更高，系统更灵活的几率更高。|4635055|另一方面，所有这些都可能需要时间和精力，而这些时间和精力在眼下被视为不必要的费用。|4635056|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

If you develop on multiple platforms at the same time you get the advantage of being able to use different tools. For example I once had a memory overwrite (I still swear I didn't need the +1 for the null byte!) that cause "free" to crash. I brought the code up to speed on Windows and found the overwrite in about 1 minute with Rational Purify... it had taken me a week under Linux of chasing it (valgrind might have found it... but I didn't know about it at the time).

Different compilers on the same or different platforms is, to me, a must as each compiler will report different things, and sometimes the report from one compiler about an error will be gibberish but the other compiler makes it very clear.

Using things like multiple databases while developing means you are much less likely to tie yourself to a particular database which means you can swap out the database if there is a reason to do so. If you want to integrate something that uses Oracle into a existing infrastructure that uses SQL Server for example it can really suck - much better if the Oracle or SQL Server pieces can be moved to the other system (I know of some places that have 3 different databases for their financial systems... ick).

In general, always developing for two or three things means that the odds of you finding mistakes is better, and the odds of the system being more flexible is better.

On the other hand all of that can take time and effort that, at the immediate time, is seen as an unneeded expense.

blocks|key|3167514|text|有些平台的开发工具真的很糟糕。我曾经在一家IB工作过，在那里，人们用VC%2B%2B开发代码，然后移植到Solaris，而不是使用Sun的可怕的工具集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3167515|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Some platforms have really dreadful development tools. I once worked in an IB where rather than use Sun's ghastly toolset, peole developed code in VC++ and then ported to Solaris.

Are there benefits to developing an application on two or more different platforms? Does using a different compiler on even the same platform have benefits?

Benefits of cross-platform development?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在两个或更多不同的平台上开发应用程序是否有好处？在相同的平台上使用不同的编译器有好处吗？

问跨平台开发的好处？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问跨平台开发的好处？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问跨平台开发的好处？
EN