gast128 wrote:
Graham Reitz
writes: I have been finding that the boost::tuple library is so convenient that I am concerned I may be overusing it. For example, in situations where I might use a struct I am tend to prefer a tuple. Where is a good place to draw the line in situations like this? Or is this the intent to use it as often as possible? Thanks much,Graham
I tend to use it for q&&d passing of bundled properties. If this is more used, I make a full blown struct out of it.
Besides that it is a great library, I can think of three drawbacks: - hard to see its contents in a debugger (using Visual Studio)
Use fusion vector :-) It is a struct.
- bind expression with tuple becomes a nightmare
Why? Ah access to the members?
- default initialising of its members is m_member() (while sometimes we reserve -1 for uninitialised)
Dunno what you mean. Please elaborate. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net