[Boost-users] [signals] slot_call_iterator caching bug?

From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2007-02-16 11:48:18

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems to me the purpose of the cache in the slot_call_iterator is to 
prevent the slot from being run multiple times if the combiner does 
multiple dereferences on an iterator.  However, since the cache is shared, 
if a copy of an already dereferenced iterator is made and incremented, 
then the original iterator will run the slot a second time when 
dereferenced.  So is this a bug, or is it just unspecified what will 
happen if you dereference a slot iterator more than once?

- -- 
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFF1eBV5vihyNWuA4URAiOHAKDIqGjobUlH40+TIZ6pmD3s7E4aSgCfRIEZ
+R0rr1t3upDKhxVPdy9x0uo=
=jELp
-----END PGP SIGNATURE-----