Re: Differentiating pimpl idiom classes in c++

Thanks for the help, although I didn't do a good job articulating my
initial question.  My first sentence was completely mis-stated
(sorry).  Let me try again.

We are working with an embedded device where only one implementation
of the driver needs to be in memory at any moment in time.  The
implementation may vary due to variations in the hardware (this must
be a common issue).  The pimpl idiom seemed to fit the bill.

My question is, what strategies can we use to get the correct
implementation at load (link) time (not run time or compile time) to
select the desired implementation?

There are several variations of the handle body idiom, including the
bridge pattern and pimpl patterns which may work.   We didn't find any
clear examples of the pimpl idiom showing how and when to choose an
implementation.

thanks,
graham

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]