Re: Differentiating pimpl idiom cl***** in c++

On Apr 18, 3:03 am, Fejimush <grahamre...@[EMAIL PROTECTED]
> wrote:
> 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.

The pimpl idiom could be used but is orthogonal to solving your stated
issue.  To do what you want, you should write some code to choose
which shared object / dynamically linked library (terminology varies
with OS) to load.  For example, you would use the dlopen / dlsym
functions on Linux/UNIX.  The question actually has nothing to do with
C++ specifically - these are standard C routines provided by the
Operating System.

Tony

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