|
|
Ger wrote:
> This is most likely due to limits inside the application, not the OS
Errr, no. It's because a 32-bit address can only address 4G. What would
you have malloc() return for the fifth gig of memory? The "limit inside
the application" would be one of not manually implementing
bigger-than-32-bit pointers and its own swap space.
Most people who went from 16-bit 32-bit processors stopped worrying
about implementing more per-process storage than available address
space. Of course, it was all the rage being able to edit a file bigger
than 64K back in 8080 days. :-)
--
Darren New / San Diego, CA, USA (PST)
"I think these anchovies are spoiled.
They're not flat."
Post a reply to this message
|
|