作为程序员,迁移到 64 位 Windows 时需要担心什么? [英] As a programmer, what do I need to worry about when moving to 64-bit windows?
问题描述
我最近的大部分编程都是在使用 C/C++/C#/VB6 的 32 位 Windows 上进行的.最近,我的客户询问我的代码是否可以在 64 位 Windows 上运行.
我想知道我可能使用的哪些旧功能会在 64 位 Windows 上失效?我需要考虑和担心哪些现实问题?
显然,我将在 64 位操作系统上测试我的代码,但我想知道要查找哪些常见问题.我更关心现有的二进制文件,但我愿意就重新编译时需要担心的问题发表评论(如果可能).
这是一个 不错的 64 位移植错误列表.
文章:
64 位、Wp64、Visual Studio 2008、Viva64 和所有其他...
将 C 和 C++ 代码迁移到 64 位 Windows 期间的陷阱检测
和
Viva64 工具 - 用于检查 64 位程序:
Most of my recent programming has been on 32-bit Windows using C/C++/C#/VB6 . Lately, my customers are asking if my code will run on 64-bit Windows.
I'm wondering what legacy features I might be using that will break on 64-bit Windows? What are some real-world issues I need to think about and worry about?
Obviously, I will test my code on the 64-bit OS, but I'd like to know what common issues to look for. I more concerned with the existing binaries, but I am open to comments about what to worry about when recompiling (where possible).
EDIT: Here is a nice list of 64-bit porting bugs.
Articles:
20 issues of porting C++ code on the 64-bit platform
The forgotten problems of 64-bit programs development
64 bits, Wp64, Visual Studio 2008, Viva64 and all the rest...
Traps detection during migration of C and C++ code to 64-bit Windows
And
Viva64 tool - for check 64-bit programs:
Viva64: what is it and for whom is it meant?
这篇关于作为程序员,迁移到 64 位 Windows 时需要担心什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!