class _Run;
    typedef boost::shared_ptr<my_namespace::_Run> Run;
    typedef boost::shared_ptr<my_namespace::_Run const> RunConst;

quote:

---

Originally posted by accord


Currently, you have two alternatives:
1. You move the caret over "_Run" and press alt+g again (I do this in similar cases) so VA will travel you to the right file

---

quote:

---

>It also turned out to be practical to have the shared pointer definitions in a file that is separate from the definition of _Run,
>so Alt-G jumps to the wrong file.

Just to clear up: I guess you mean "not the sensible file" by "wrong file"

---

namespace my_namespace
{
	class _Run
	{

	};

}

typedef boost::shared_ptr<my_namespace::_Run> Run; // step 2: press alt+g over _Run
typedef boost::shared_ptr<my_namespace::_Run const> RunConst;

void testfunction()
{
	Run obj; // step 1: press alt+g over "Run"

}

• It's 3 actions instead of one: Alt-G, choose template type, Alt-G again. For an action that is performed with a very high frequency that's annoying.


• The second issue is a sideeffect of our project structure, which proved to be highly efficient otherwise: Have one header for each component that contains all classes as forward definitions, and all shared pointer typedefs. This allows other components to include only this definitions file and be able to reference all types from this component, without any problems of circular header inclusions.
  
  Now a problem when working with large solution is that the workspace is often cluttered with too many files. It's a constant struggle to have the files you are working on visible in the IDE. Now, assume that you are working on 3-4 components at a time (not unusual) and all are split in interface and implementation, then you'll have 6-8 header containing these shared pointer definitions. So each Alt-G will open one of these headers and add it to the list of open files.
  

quote:

---

Originally posted by accord
Anyway, personally I don't prefer using typedefs. I rather write down the pointer definition and avoid namespaces when it is possible, i.e. a generally used smartptr shouldn't be in a namespace and it's name shouldn't contain an underscore But it is my personal opinion. I know that company policies don't always allow to do things simple.

---