I've noticed that in VC++ the intellisense doesn't fire up for instances of classes or structs defined locally inside a function. Is there some reasoning behind this or is it just a shortcoming of VC++?
I've noticed that in VC++ the intellisense doesn't fire up for instances of classes or structs defined locally inside a function. Is there some reasoning behind this or is it just a shortcoming of VC++?
Probably a shortcoming, that is my guess. The default IntelliSense can be rather poor.
If you have to burn (and I mean a lot >_<), then I would suggest Visual Assist X.
Originally Posted by Adak
I wonder about the appropriateness of defining function-local data types. Why are you doing this?
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
And if a struct is defined locally in a function, do you really need the IDE to tell you the names of members?
Steady on guys, I'm just exploring the language!
Actually I noticed this in the course of going through one of the many exercises at the end of each chapter of Bruce Eckel's "Thinking in C++." He has you doing all sorts of things...define this class here, define this struct there, create an instance of this class in this function....see what the compiler tells you....define this globally instead and see what the compiler tells you now....
Etc.
And in the process I noticed that Intellisense doesn't work when you define a type in a function and since I'm a beginner with a naturally curious outlook, I wondered whether there was some reasoning behind this or whether it was just a bug. As it happens I've since come across a bug report for this very issue on the Microsoft site. It was reported in 2006 and the response was that they don't have the time or resources to fix it.
You're not having a problem with the language, but with an IDE. Intellisense has nothing to do with the C++ language.Steady on guys, I'm just exploring the language!
Not very perceptive are you? When I pointed out that I was exploring the language it was in response to the replies which questioned why I was defining a type to be local to a function.
My question was about why you needed Intellisense for this. You probably missed it, though, in your rush to point out my lack of perception.
There it goes again! I said nothing to even insinuate that I was using Intellisense to explore the language. I made it very clear that I was curious about something I had discovered about Intellisense in the course of exploring the language.
Cripes, I'd hate to have to debug one of YOUR programs
Faster typing out members, among other things?
Okay guys... I think we've reached a conclusion here. Intellisense has trouble with function-local data types.
I was curious why you were doing this, because it's pretty unorthodox. "Exploring the language" is as good a reason as any.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
If you already know what member you want, Intellisense gets in the way.
Last edited by medievalelks; 05-18-2009 at 11:07 AM.
It takes literally no time to fire up. It comes up automatically and blazingly fast.
And no, to some, IntelliSense does not get in the way.
Every now and then it'll annoy me by hiding something I want to glance at while I'm typing. For instance, a line of code below the one I'm working on. But the pros outweigh the cons. It's actually a great learning tool for a beginner because, for instance, it indicates when you've passed an argument correctly into a function. However every now and then I find it doesn't work first time for some reason....then I'll go back and delete the object name and type it again and it does work.
If it does hide something, I just hit Esc to dismiss it,
And if I find it doesn't want to show something, then usually I compile the code and get rid of any compile errors IntelliSense might be hung up upon. Then it usually works.
