strange problem passing a vector

[mickey]

Usually it is better to declare elements on stack rather that heap but it does depend on how you use it in you application.
[/CODE]

What do you mean? What's the reason lead me to allocate the vecNode(in the main) in on the stack or on heap?

[Gopala Krishna]

What do you mean? What's the reason lead me to allocate the vecNode(in the main) in on the stack or on heap?

I mean dont create the vecNode using new. that is, dont use

vector<Node> *listNode = new vector<Node>;

vector<Node> *listNode = new vector<Node>;

To copy to clipboard, switch view to plain text mode 

Instead use

vector<Node> listNode;

vector<Node> listNode;

To copy to clipboard, switch view to plain text mode 

This removes explicit new and delete operations and simplifies code in many places. Ofcourse this is not mandatory, you might find the first solution suitable in your case.

@Wysota: Yeah, that is the reason i told it is unconventional. But it is not "unmaintainable" - atleast in a group of experienced c++ programmers.

[mickey]

Ofcourse this is not mandatory, you might find the first solution suitable in your case.

when can it be suitable? Any examples? (for me there's no difference)...

[Gopala Krishna]

when can it be suitable? Any examples? (for me there's no difference)...

It might be usable when you have to share one vector amongst many instances of same or different objects. Instead of holding many copies you will be holding pointers to vectors.

But you may note that qt's collection classes are implicitly shared and are more easier to use than stl classes. stl classes are powerful only if you know how to extract maximum from them. Otherwise qt's collection classes should suffice for most cases.