[cadcdev-tiki] Re: Making m_txr protected vs private so Texture can be extended and m_txr

[Dan P. <ba...@al...>]

On Jan 1, 2006, at 10:52 AM, cadcdev-svn- 
co...@li... wrote:

> Making m_txr protected vs private so Texture can be extended and  
> m_txr accessed.

Speaking of this, am I the only one who wished they'd put an  
access_cast in C++? I think the protected/private stuff is a good  
guideline to follow (and when it really needs to be changed, like the  
above, it should change), but sometimes you just need to be naughty  
and you know it and don't care. :) For example at work I was trying  
to augment the stupid MS STL iostream classes to allow 64-bit file  
pointers, but it turned out that the only way I could get at the  
underlying file descriptor reliably was to modify their STL code. I  
couldn't even use offsetof() to cheat. I would've had to make a copy  
of half their STL library and modify that one class to have public  
instead of private, even to do that. >_<