This time lets briefly look at three structural idioms discussed in Coplien's book, Advanced C++ programming styles and idioms.
Handle and Body: Handle and body are logically one entity but physically two. This separation allows handle to be much smaller in size than the body. Handle and body are both classes. Because they are logically same entity, there are several consequences: handle can be passed instead of body wherever body is required (efficient). To be logically same, handle and body needs to have exactly same interface. Any addition to body class interface needs a change in the handle class (maintenance). Handle class delegates all function calls to the body. (extra function call). Handle manages memory and the body manages the abstraction. This type of structure is typically used in reference counting. Though hidden from the client, body class pollutes the global namespace. Important thing to note here is that though, both the classes are in global namespace the instance of the body class is only accesible from within the handle class. body class is all private and handle is a friend of body. Note that both handle and body need to be classes.
Then why put the body class in the global namespace? Lets put it inside the handle class. Call this type of structure Envelope/Letter class idiom.
e.g.
class String_Reprentation { char str[5000]; long count; } (Body)
class String { String_Reprentation *rep; } (Handle)
The problem of mirroring interfaces in the handle and body classes mentioned above can be solved using a cool C++ feature: operator ->. Define an overloaded dereference operator (arrow operator) in the handle class which returns a pointer to body.
String_Representation * String::operator -> ();
Note that most new string operations can be implemented as String_Representation member functions: the handle class String gets these operations automatically throught overloaded arrow operator. Add reference counting to it for more flavor. Call it Counted Pointer idiom! Also note that String_Representation interface can't be private.
More info: http://users.rcn.com/jcoplien/Patterns/C++Idioms/EuroPLoP98.html
Handle and Body: Handle and body are logically one entity but physically two. This separation allows handle to be much smaller in size than the body. Handle and body are both classes. Because they are logically same entity, there are several consequences: handle can be passed instead of body wherever body is required (efficient). To be logically same, handle and body needs to have exactly same interface. Any addition to body class interface needs a change in the handle class (maintenance). Handle class delegates all function calls to the body. (extra function call). Handle manages memory and the body manages the abstraction. This type of structure is typically used in reference counting. Though hidden from the client, body class pollutes the global namespace. Important thing to note here is that though, both the classes are in global namespace the instance of the body class is only accesible from within the handle class. body class is all private and handle is a friend of body. Note that both handle and body need to be classes.
Then why put the body class in the global namespace? Lets put it inside the handle class. Call this type of structure Envelope/Letter class idiom.
e.g.
class String_Reprentation { char str[5000]; long count; } (Body)
class String { String_Reprentation *rep; } (Handle)
The problem of mirroring interfaces in the handle and body classes mentioned above can be solved using a cool C++ feature: operator ->. Define an overloaded dereference operator (arrow operator) in the handle class which returns a pointer to body.
String_Representation * String::operator -> ();
Note that most new string operations can be implemented as String_Representation member functions: the handle class String gets these operations automatically throught overloaded arrow operator. Add reference counting to it for more flavor. Call it Counted Pointer idiom! Also note that String_Representation interface can't be private.
More info: http://users.rcn.com/jcoplien/Patterns/C++Idioms/EuroPLoP98.html
Comments
looking for great blogs such as yours. I treasure this
site and will go back!
I want you to look for my 1800contacts coupon blog.
and we had to go back to it! Every chance I get on the
net I search for blogs just like your site.
If your look to uncover information, please visit my blog
this site again. I just worship the site its comes
from! Believe me in my extra time I'm consistently
looking up blogs like this.
You got me! I will check out your coupon 1800contacts blog a.s.a.p!
back once again to view it! I use much of my spare
time searching for blogs like yours.
Please proceed to my 1800contacts web coupon code blog when you find the time.
will go back again! I like surfing the net for blogs
as good as yours.
Oh please, check for the blog site with my coupon 1800contacts!
the internet, when I have the time. I'm going to go
back to it!
Check out the blog site with my disapointments plastic surgery in it!
will go back again! I like surfing the net for blogs
as good as yours.
Want to see top notch work, peep my ear plastic surgery blog site for the bomb work!
type of blogs that you do. It had me on the edge of my
seat and I kept going back to again and again!
Stop by and visiit my bad celebrity plastic surgery blog!
that I want to visit it more each day! I like
searching for blogs that have the same content like
this one!
Search for my plastic surgery specialist blog, it will leave you speechless.
when time allows me to. I enjoyed the site and I'll
check it next time!
Look who checking out my plastic surgery minneapolis blog?
back again! I never get tired of looking for blogs
just like this one.
Stop by and visiit my plastic surgery georgia blog!