Re:Overview of cross-architecture portability problems
by johnklos on Wednesday September 25, 2024 @04:44PM
(#41651666)
Who said anything about asserting that your code is actually portable?
There are two extremes here, and not being one doesn't mean the other:
1) Writing code with bad coding practices where alignment, endianness, word size, platform assumptions, et cetera, are all baked in unapologetically, saying that doing anything else would incur financial cost
2) Writing code that's as portable as possible, setting up CI and testing on multiple platforms and architectures, and asserting that said code is actually portable
One can simply write code that's as portable as possible and let others test and/or say when there's an issue. That's quite common.
As someone who compiles software on architectures that a good number of people don't even know exist, I think it's absolutely ridiculous to suggest that portability awareness without multi-platform and multi-architecture CI and testing isn't worthwhile.
There are two extremes here, and not being one doesn't mean the other:
1) Writing code with bad coding practices where alignment, endianness, word size, platform assumptions, et cetera, are all baked in unapologetically, saying that doing anything else would incur financial cost
2) Writing code that's as portable as possible, setting up CI and testing on multiple platforms and architectures, and asserting that said code is actually portable
One can simply write code that's as portable as possible and let others test and/or say when there's an issue. That's quite common.
As someone who compiles software on architectures that a good number of people don't even know exist, I think it's absolutely ridiculous to suggest that portability awareness without multi-platform and multi-architecture CI and testing isn't worthwhile.