Murray Cumming Comneon com wrote:
I have added some comments to the public access specifiers regarding this. I am not overly concerned with having these nested typedef's public. It's not like they grant access to anything that should be protected (no pun intended). It does, unfortunately, make the public interface slightly wider. However, if you want to make a serious improvement to the sequence implementation code, I think the way to go is to merge all the differing kinds of sequence into a single implementation that uses template parameters to implement all the special cases. That way you only ever have to fix stuff in one place.Do remember that these access problems are a gcc bug, not a bug in orbitcpp code [1], so you should probably #ifdef any workaround, or at least add a comment saying that stuff is public for that reason.
-- Bowie Owens CSIRO Mathematical & Information Sciences phone : +61 3 9545 8055 fax : +61 3 9545 8080 mobile : 0425 729 875 email : Bowie Owens csiro au