Re: orbitcpp/orb-cpp/*_seq.h member typedefs access control probl em
- From: Bowie Owens <bowie owens csiro au>
- To: Murray Cumming Comneon com
- Cc: bland mail ru, orbitcpp-list gnome org
- Subject: Re: orbitcpp/orb-cpp/*_seq.h member typedefs access control probl em
- Date: Wed, 27 Aug 2003 09:25:45 +1000
Murray Cumming Comneon com wrote:
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.
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.
--
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
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]