![]() ![]() Code which relies on POSIX APIs won't compile if that's not available (Windows supports some POSIX APIs, but far from all).Ĭ++ can mean a lot of different things. Code which uses the Win32 API won't compile on platforms where it's not available (anywhere other than Windows). The most obvious example is of course the OS APIs. That works great on a 32-bit machine, but on 64-bit, you end up trying to store 64 bits of data into a 32 bit wide object.Įven if your code is portable, your dependencies may not be. So if your code makes assumptions about implementation-defined behavior, it might not be portable (a classic example is code which assumes that a pointer can be stored into an Is 16 bits wide on Windows, but typically 32 bits on Linux. ![]() Is typically 64 bits wide on 64-bit Linux, but only 32-bit on 64-bit Windows. For example, the size of common data types can (and will) vary across different platforms. The C++ standard leaves many things implementation-defined, which means that it's up to the individual platform and compiler how it should behave. However, there are a few caveats to be aware of:īehavior might be different on different platforms. In theory, C++ source code can be compiled to run on any platform. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |