- recovering from std::bad_alloc in std::string reserve - 9 Updates
- Niuce C++14-feature - 1 Update
| Paavo Helde <myfirstname@osa.pri.ee>: May 25 07:57PM +0300 >> contiguous address space and Bonita is right in pointing out this might > Why? Only the virtual memory address space needs to be contiguous, the > real memory pages storing the string could be all over the place. Exactly. And if the memory allocator cannot find a free range of contiguous 900M addresses, guess what happens. |
| Paavo Helde <myfirstname@osa.pri.ee>: May 25 08:04PM +0300 25.05.2021 19:21 Nikolaj Lazic kirjutas: >> a problem with the limited address space in 32-bit programs. > Win7 32bit cannot access 16G. Limit is 3.5G. > She needs 64bit Windows to use it. OP was a bit unclear in this point. But there would be no point to have a 32-bit Windows 7 on a machine with 16 GB RAM, so I hope he has got a 64-bit OS after all. |
| Lynn McGuire <lynnmcguire5@gmail.com>: May 25 12:20PM -0500 On 5/24/2021 11:47 PM, Paavo Helde wrote: > different OS-es. > It's also strange to base the program logic on the size of an *output* > file. But there are probably reasons. Thanks, that is a good idea to move to the 64 bit version of ftell. My 450,000 lines of C++ program is so tied to the Win32 API that it is not funny. My calculation engine is 850,000 lines of F77 and about 20,000 lines of C++ but it is still portable to the Unix boxen, probably mainframes too if any engineers ran them anymore. Lynn |
| Lynn McGuire <lynnmcguire5@gmail.com>: May 25 12:46PM -0500 On 5/25/2021 12:04 PM, Paavo Helde wrote: > OP was a bit unclear in this point. But there would be no point to have > a 32-bit Windows 7 on a machine with 16 GB RAM, so I hope he has got a > 64-bit OS after all. Yes, I have Windows 7 x64 Pro. I cannot convert to win64 at this time. When we do convert, it will be a steep hill as we started this code in Win16 in 1987. The Win32 port was a very steep hill in 2000. Lynn |
| Lynn McGuire <lynnmcguire5@gmail.com>: May 25 12:49PM -0500 On 5/25/2021 12:16 AM, Juha Nieminen wrote: > { > std::cout << "Unknown excpetion thrown while trying to read file\n"; > } Thanks, I did not know the code for catching the bad_alloc explicitly. Lynn |
| Paavo Helde <myfirstname@osa.pri.ee>: May 25 08:58PM +0300 25.05.2021 20:46 Lynn McGuire kirjutas: > Yes, I have Windows 7 x64 Pro. I cannot convert to win64 at this time. > When we do convert, it will be a steep hill as we started this code in > Win16 in 1987. The Win32 port was a very steep hill in 2000. Nowadays there are special compiler warnings for 64-bit porting issues. When porting, it would make sense to enable them all, turn them into errors instead of warnings, and fix them all. |
| Nikolaj Lazic <nlazicBEZ_OVOGA@mudrac.ffzg.hr>: May 25 06:23PM > Yes, I have Windows 7 x64 Pro. I cannot convert to win64 at this time. > When we do convert, it will be a steep hill as we started this code in > Win16 in 1987. The Win32 port was a very steep hill in 2000. Maybe this can help: https://stackoverflow.com/questions/639540/how-much-memory-can-a-32-bit-process-access-on-a-64-bit-operating-system |
| Lynn McGuire <lynnmcguire5@gmail.com>: May 25 01:48PM -0500 On 5/25/2021 12:58 PM, Paavo Helde wrote: > Nowadays there are special compiler warnings for 64-bit porting issues. > When porting, it would make sense to enable them all, turn them into > errors instead of warnings, and fix them all. Thanks ! Lynn |
| Lynn McGuire <lynnmcguire5@gmail.com>: May 25 01:49PM -0500 On 5/25/2021 1:23 PM, Nikolaj Lazic wrote: >> Win16 in 1987. The Win32 port was a very steep hill in 2000. > Maybe this can help: > https://stackoverflow.com/questions/639540/how-much-memory-can-a-32-bit-process-access-on-a-64-bit-operating-system Thanks ! I was aware of that but I had not tried it yet. Lynn |
| Manfred <noname@add.invalid>: May 25 04:22PM +0200 > some have gone back to multi process which also has the benefit of making > some kind of javascript hacks difficult if not impossible if each tab is a > seperate process. The current version of Firefox for Windows starts up with 5 (five!) processes, and then adds one more for each tab. However, what I was referring to above was some product where stability was much more critical than a web browser. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment