Re: flyweights, nested flyweights and shared libraries

From: Andreas Buykx (A.Buykx_at_[hidden])
Date: 2021-02-25 13:20:54

From: Boost-users <boost-users-bounces_at_[hidden]> On Behalf Of Joaquin M López Muñoz via Boost-users
Sent: donderdag 25 februari 2021 13:52
...

El 25/02/2021 a las 12:44, Andreas Buykx via Boost-users escribió:
From: Boost-users <boost-users-bounces_at_[hidden]><mailto:boost-users-bounces_at_[hidden]> On Behalf Of Joaquin M López Muñoz via Boost-users
Sent: zaterdag 20 februari 2021 16:22

...

El 19/02/2021 a las 16:54, Andreas Buykx via Boost-users escribió:
...
Also, is it possible to have nested flyweights (when they are wrapped by accessor classes)?
And would that cause any additional problems in the above scenario?

I don't see any problem with that.

[Andreas Buykx]

One thing to be aware of though is that boost::flyweight<nested>::init() must be called before creating the first nesting flyweight. This way you make sure that at program exit the nesting flyweight's static data structures are destroyed before the nested flyweight's static data structures.

Yes, exactly. Did this solve your problem?

[Andreas Buykx] Yes it did. Thanks a lot for your help.