[ale] Recent RTFM'ing and Questions and Answers

Mark Hurley debian4tux at telocity.com
Sun Nov 18 21:46:15 EST 2001


Thanks....I have been looking there and other places.  It's one of
those stories where I came across a very nice example with picture
representation of the classes in memory.

I will keep my eyes open.

Thank you!

Mark

On Tue, Nov 13, 2001 at 11:11:11AM +0000, Joseph A Knapka wrote:
> Mark Hurley wrote:
> > 
> > Great...and as Stephen points out...2AM ranting is allowed. ;)
> > 
> > Its great to see everyone has strong opinions on this.  But I'm sure a
> > lot of people in here can stump even the best of us.
> > 
> > BTW...I'm going to ask a question now... ;)
> > 
> > Does anyone have a good link pointing to a great explanation of memory
> > mgt. in C++? I'm not looking for HOWTO's on programming, that concept
> > is pretty set with me.
> > 
> > I'm looking more on the objects on the heap, and derived types
> > occupying bytes...etc. Objects being passed by by their super type,
> > yet able to explain how down casting is handled in the memory scope of
> > things. Maybe even a nice picture or two.
> 
> You've read the comp.lang.c++ FAQ, yes? (<URL: http://www.faqs.org/>
> and navigate to newsgroups->comp->comp.lang.c++)
> 
> Admittedly, that's a large document that's more or less
> concerned with memory management issues in a great many
> places. I know of no document that specifically deals
> with memory management in C++ as a topic. The
> best available pieces of writing on C++ in general
> are Scott Meyers' "Effective C++" books, which cover
> memory issues very clearly.
> 
> Personally, I think if you can explain why virtual
> destructors are necessary, you probably have a
> reasonable understanding of C++ memory management.
> 
> Cheers,
> 
> -- Joe
> # "You know how many remote castles there are along the
> #  gorges? You can't MOVE for remote castles!" - Lu Tze re. Uberwald
> # (Obsolete) Linux MM docs:
> http://home.earthlink.net/~jknapka/linux-mm/vmoutline.html
> 

---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.






More information about the Ale mailing list