Large-file support: Difference between revisions

Revision as of 21:47, 24 February 2020

Revision as of 21:50, 19 March 2020

Line 25:

Except for [[embedded systems]] with their special programs, the consideration of varying large-file support becomes obsolete in program code after 2020.

== Related Problemsproblems ==

The [[year 2038 problem]] is well known for another case where a 32-bit "long" on 32-bit platforms will lead into problems. Just like the large-file limitation it will get obsolete when systems move to 64-bit only. In the meantime a 64-bit timestamp was introduced. In the Win32 API it is visible in functions having a "64" suffix along the earlier "32" suffix. When large-file support was added to the Win32 API it has lead to functions having an additional "i64" suffix which sometimes makes for four combinations.(findfirst32, findfirst64, findfirst32i64, findfirst64i32).<ref>{{cite web|url=https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/findfirst-functions?view=vs-2019|title=C Run-time library (CRT) reference : findfirst|publisher=Microsoft|accessdate=2020-02-17}}</ref> By comparison the UNIX98 API introduces functions with a "64" suffix when "_LARGEFILE64_SOURCE" is used.