[Alephmodular-devel] What's up...

[Br'fin <br...@ma...>]

Still debating about what to do for Display Abstraction and bitmap 
abstraction and the like. Hard time trying to juggle wants and 
perceived needs there. Though in poking around I did find another site 
with good C++ articles.
Herb Sutter - Publications (http://www.gotw.ca/publications/index.htm)

So I finally figured out just what an auto_ptr is and how to use it. 
Also some other details such as why you might want to go with a 
non-volatile-interface on a class. Which I liked.

Consequently, I reworked CFileTypes and CFileDescs to use these new 
approaches, and in general I liked how they turned out. The interface 
in the primary class seems much more detailed to me. And I feel that 
the use of auto_ptrs generally feels right.

the only sticky spot resulted in things like

IFileRefPtr (std::auto_ptr<std::istream>) and 
IFileRef(std::auto_ptr<std::istream>&) where IFileRef is used 
throughout the code when passing the argument around. But IFileRefPtr 
is used when actual ownership of the auto_ptr wants to be managed.

In accompaniment, I did update CFileDesign.txt

-Jeremy Parsons