Yes, I had to make node public but there's no public function that returns nodes(nor there's obviously any public variable), so having node public doesn't create any problem for the internal workings...
Type: Posts; User: MisterIO
Yes, I had to make node public but there's no public function that returns nodes(nor there's obviously any public variable), so having node public doesn't create any problem for the internal workings...
About the first statement: could you clarify? What would that change for my problem? I'd still have to make node public, wouldn't I?
About the second statement: frankly, from the messages i get...
I thought about doing this:
template<K> iterator_t{}
typedef iterator_t<node> iterator;
But it doesn't seem to work either, because the type isn't declared in the same context, so...
I'm creating a little container class, but I have a design doubt. I'll post here some example code:
template<T> class useful_class {
public:
void some_func()
{
node...