Re: [boost] [pimpl] Proposal. Determining interest.
An overwhelming :-) interest in the proposed Pimpl has certainly been overwhelming. LOL. The Pimpl idiom has certainly been beaten up and its complexity/importance is far from, say, a threading library. Havings said that I feel that the simple Pimpl deployment technique and the suggested Pimpl interface is simple, elegant and pleasant to use with no drawbacks that I can see so far. I've updated and uploaded (as Pimpl-02.zip) the pimpl interface that implements both value- and pointer-semantics. Any comments are most welcome. Best, Vladimir.
batov wrote:
An overwhelming :-) interest in the proposed Pimpl has certainly been overwhelming. LOL.
I've updated and uploaded (as Pimpl-02.zip) the pimpl interface that implements both value- and pointer-semantics. Any comments are most welcome.
I'm interested in trying it out. But where is it? (I tried to start at www.boost.org, clicked on "Vault", and then was unsuccessful in finding your file) Deane
batov wrote:
An overwhelming :-) interest in the proposed Pimpl has certainly been overwhelming. LOL.
The Pimpl idiom has certainly been beaten up and its complexity/importance is far from, say, a threading library. Havings said that I feel that the simple Pimpl deployment technique and the suggested Pimpl interface is simple, elegant and pleasant to use with no drawbacks that I can see so far.
I've updated and uploaded (as Pimpl-02.zip) the pimpl interface that implements both value- and pointer-semantics. Any comments are most welcome.
I've downloaded it, read the documentation, and I think it looks promising. To test it out I'm converting a pimpled class in my code base to use your library. This class is noncopyable and as such it isn't immediately obvious to me whether the class should be modeled using the pimpl's value semantics, pointer semantics, or some other semantic that doesn't yet exist. Thanks, Michael Marcin
On Monday 22 October 2007 09:37, batov wrote:
An overwhelming :-) interest in the proposed Pimpl has certainly been overwhelming. LOL.
The Pimpl idiom has certainly been beaten up and its complexity/importance is far from, say, a threading library. Havings said that I feel that the simple Pimpl deployment technique and the suggested Pimpl interface is simple, elegant and pleasant to use with no drawbacks that I can see so far.
I've updated and uploaded (as Pimpl-02.zip) the pimpl interface that implements both value- and pointer-semantics. Any comments are most welcome. <snip>
Inherited Pimpls
sdfsd
Polymorphic Implementations
sdfs
I'd very much like to see those sections, or even only how you'd go about re-using a pimpl_ptr from a base class, inheriting Derived::Impl from Base::Impl.? Thanks, Marc -- Marc Mutz -- marc@klaralvdalens-datakonsult.se, mutz@kde.org Klarälvdalens Datakonsult AB, Platform-independent software solutions
participants (4)
-
batov -
Deane Yang -
Marc Mutz -
Michael Marcin