[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost
Subject:    Re: [boost] [pimpl] Proposal. Determining interest.
From:       "Vladimir Batov" <batov () people ! net ! au>
Date:       2007-11-04 4:06:25
Message-ID: 002601c81e98$11ed3640$0201a8c0 () irsa ! railad ! com
[Download RAW message or body]

> You consider pimpl part of the interface? Interesting... I've always
> thought of it as an implementation detail to build compiler firewalls.
> I.E. any class I've made using the pimpl idiom I could have built the
> same interface with more external dependencies and heavier compile times.

If your question was about pimpl<> itself, then I misunderstood your 
question. Although given pimpl<> provides at least some of the public 
interface it could be considered as such. Although I probably tend to 
consider it an implementation glue between interface and implementation. To 
figure out why I inherit publicly from pimpl<> you might like to try 
inheriting privately (which I never do. I use aggregation insted) and see 
what functionality becomes unavailable.

Best,
V. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[prev in list] [next in list] [prev in thread] [next in thread]