On Thu, Sep 10, 2009 at 10:01 AM, Dos-Man 64 <[email protected]> wrote: > > On Sep 10, 11:42 am, Ryan Graham <[email protected]> wrote: >> On Thu, Sep 10, 2009 at 9:26 AM, Dos-Man 64 <[email protected]> wrote: >> >> > I have a C++ string class that I am finishing up work on. I intend to >> > use this in my applications (whatever they may be.) I am just trying >> > to determine a bit more about the underlying architecture and how it >> > deals with memory segments. >> >> My gut instinct says you are over thinking this. I've never had to >> deal with anything like this in C/C++, on Linux, in the last 8 years. >> It's possible I just don't understand what you are trying to find out. >> > > Well, I am coming from a different platform. Actually 2 different > platforms. MS-DOS used segmented memory. It is common to allocate > memory in 64k chunks or segments. Windows did away with the need to > do this, but you use FAR pointers (long pointers or LPSTRs). > > It is for this reason that multiline edit controls were limited to 64K > on earlier windows versions. For example, the notepad that comes with > windows 98 cannot open text files that are larger than 64k. It instead > refers you to wordpad which uses a richedit control.
Ah, ok.. wasn't sure if you were actually referring to segmentation or just using a different word for pages. Linux was 32-bit from the start, so it uses a flat memory space and never really made developers deal with segmentation. A pointer is a pointer, as it should be! ~Ryan -- http://rmgraham.blogspot.com http://twitter.com/rmgraham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
