Not sure that it's easy-to-fix kind of thing, but I just wanted to let you know. There's case when default Visual Studio "Go to Defintion" works better than VAX one.
It's happening in the case when enum values are generated through macro. As an example I use one from http://home.comcast.net/~tom_forsyth/blog.wiki.html
#define TrainState_XXYYTable \ XX(TrainState_Stuck) YY(=0), \ XX(TrainState_Going), \ XX(TrainState_Waiting), \ XX(TrainState_Stopped), \ XX(TrainState_count)
#define XX(x) x
#define YY(y) y
enum TrainState
{
TrainState_XXYYTable
};
#undef XX
#undef YY
#define XX(x) #x
#define YY(y)
const char *TrainState_Name[] =
{
TrainState_XXYYTable
};
#undef XX
#undef YY
With code like this after writing TrainState_Stuck in code VAX "go to defintion" refuses to go back to enum defintion.
Go to Defintion downside
Posted - Jul 04 2014 : 05:12:29 AM
