4 ms·
The author seems to focus a lot on having 64 bit versions of the editors. I'm wondering what's the downside of using a 32 bits in the case of a console text ed
by Renaud 6y ago
The author seems to focus a lot on having 64 bit versions of the editors.
I'm wondering what's the downside of using a 32 bits in the case of a console text editor? I doubt that it's because you could theoretically need to load 4GB+ text files in memory.
Is there a good reason to want a 64 bit version of an editor to the point of excluding it if there isn't one?
- Hello71 6y ago> I also cry a lot about 64-bit Windows builds because I work a lot in WinPE and other environments where syswow64 is not available.
- jussij 6y agoOn Windows the executable will most likely only have access to 2 GB of memory. The Windows PE header contains the LARGEADDRESSAWARE flag which controls the memory available to the executable. When that flag is off (i.e. the Microsoft recommended default value) the executable only has access to 2 GB of memory. To access more memory that LARGEADDRESSAWARE PE flag set to on: https://docs.microsoft.com/en-us/cpp/build/reference/largeaddressaware-handle-large-addresses?redirectedfrom=MSDN&view=vs-2019 https://docs.microsoft.com/en-us/cpp/build/reference/largead... But in any case, you would think 2 GB is more than enough RAM for most text handling scenarios.