programming design (another thread)

[l2u]

Hello

I have another programming design question..
Lets say I have 3 classes like below:

class parser {
};

class user {
};

class session {
public:
	std::list<user> m_list;
};

Session class is a 'main class' where most of the work is being done (in loop/s)..
It has a list of user objects, where each user needs access to 1 particular parser object (parser class).

I dont want each user to have its own parser object since that would be unneccessary..

I wonder what is the best approach to make class user (user objects) be able to access data in one parser object?
I know most of you would just pass parser object's reference to user class constructor, and then access data this way.

Is there any better way/design pattern to achieve that?
Maybe I shouldn't bother because this might be the best/easiest way?
Or is there more 'professional' way?

Another thing I'm unsure about..

In case passing reference of parser object to user objects is the best way, where would you guys define parser object?

Does this seem okay:

class session {
public:
	std::list<user> m_list;
	parser m_parser;
};

Thanks for help
Regards

[Daved]

Is there one parser per session? Does the parser need to remain alive through multiple calls of session's functions? How many user functions require the parser? Does those functions require the same parser through different invocations?

You could make the parser local to the session function that uses it if you only need it for that small lifetime.

You could pass the parser by reference to the user functions instead of the class itself, if the user only needs it for certain functions.

[AverageSoftware]

How about giving the user class a static parser object?

class user
{
private:
    static parser yournamehere;
};