Arjun Bijanki: Making Sense of VC Intellisense

The Discussion

• 

  looks interesting but... 600MiB for 35 minutes? wtf
  

• 

  I'm processing a smaller download file now... Stay tuned.
  
  C
  
  EDIT: Done. See description for link or click here.

• 

  Charles wrote:

  I'm processing a smaller download file now... Stay tuned.
  
  C
  
  EDIT: Done. See description for link or click here.

  thanks
  

• 

  Charles wrote:

  so... why one language in MS stack [VB.NET] can do it [background compilation] and another language which is very very different [C++] cant or doesn't do it

  as for C# I think its more a "political" decision than a technical one, as for C++ its the compiler that compile the code and the C++ compiler does a lot more than C# or VB.NET compilers, its pretty obvious isnt?
  
  interesting how JavaScript intellisense works in VS 2008? there are so many issues with it 
  
  that parallelization feature built in C++ compiler, do we will see it in C# compiler? IIRC C# compiler doesn't have it, msbuild have it...
  

• 

  :Ointeresting how JavaScript intellisense works in VS 2008? there are so many issues with it 
  
  

• 

  Ion Todirel wrote:

  
  that parallelization feature built in C++ compiler, do we will see it in C# compiler? IIRC C# compiler doesn't have it, msbuild have it...
  

  
  
  Research into functional languages means that next generation JITs are doing this to a certain extent, but it's not statically compiled in like the C++ compiler.
  

• 

  Ion Todirel wrote:

  

  Charles wrote: so... why one language in MS stack [VB.NET] can do it [background compilation] and another language which is very very different [C++] cant or doesn't do it

  as for C# I think its more a "political" decision than a technical one, as for C++ its the compiler that compile the code and the C++ compiler does a lot more than C# or VB.NET compilers, its pretty obvious isnt?

  
  
  I don't think it is... The C++ compiler is a much more complex thing than the C# compiler. You have a lot more stuff that's going on and it takes also a lot longer to compile C++ code - compared to C# code.
  
  This video was very interesting and Dan asked some nice questions Especially the one about the AST! While I was watching the video that was actually one question that I would have asked

• 

  littleguru wrote:

  

  Ion Todirel wrote:  Charles wrote: so... why one language in MS stack [VB.NET] can do it [background compilation] and another language which is very very different [C++] cant or doesn't do it as for C# I think its more a "political" decision than a technical one, as for C++ its the compiler that compile the code and the C++ compiler does a lot more than C# or VB.NET compilers, its pretty obvious isnt?

  
  
  I don't think it is... The C++ compiler is a much more complex thing than the C# compiler. You have a lot more stuff that's going on and it takes also a lot longer to compile C++ code - compared to C# code.
  
  This video was very interesting and Dan asked some nice questions Especially the one about the AST! While I was watching the video that was actually one question that I would have asked

  
  
  Yep. Parsing C# is a walk-in-the-park compared to parsing C++. Just look at the respective size of standard for that (C++, C#). Don't forget that pasing a C# file might involve parsing say 5000 lines at most, whereas an expanded C++ file with the #includes can often be over 50,000 lines of code - windows.h is a good example of this.
  
  C# also reflects-in lots of it's information, whereas C++ has no such ability, so C# can get away with a tiny intellisense store, whereas C++ has an absolutely gigantuan database with a hundred different things reading and writing to it per second, which means it breaks.
  
  Microsoft last I heard was 100% committed to it's C++ customers, and for them to be crippling their own product in order to convert people to C#, which is a fundamentally different type of application for political reasons seems frankly ridiculous.
  

• 

  evildictaitor wrote:

  
  Yep. Parsing C# is a walk-in-the-park compared to parsing C++. Just look at the respective size of standard for that (C++, C#). Don't forget that pasing a C# file might involve parsing say 5000 lines at most, whereas an expanded C++ file with the #includes can often be over 50,000 lines of code - windows.h is a good example of this.
  
  C# also reflects-in lots of it's information, whereas C++ has no such ability, so C# can get away with a tiny intellisense store, whereas C++ has an absolutely gigantuan database with a hundred different things reading and writing to it per second, which means it breaks.
  
  Microsoft last I heard was 100% committed to it's C++ customers, and for them to be crippling their own product in order to convert people to C#, which is a fundamentally different type of application for political reasons seems frankly ridiculous.
  

  
  
  I don't have exact values, but there are a huge number of developers using VS for C++.  They're the entire focus of the team I work on, so we're definitely committed to them.
  
  Like I mention in the video, the next release for VS will offer a vastly improved Intellisense, Browsing and Navigation experience for these developers.  We realize this is painful today, we released some perf work, and we're going to do it much better in the future.
  
  Also, the VC++ libraries feature pack for VS 2008 is in Beta right now.  Give that a try!
  
  There's a lot of cool C++ stuff on the horizon.

• 

  Nice video! Thank you Charles and the rest of Channel 9 team for listening to my wishes (and a recent feedback message ) about the size of downloads and the bandwidth challenged/traffic limited viewers, - that's us Appreciating these low-res downloads.
  
  It took almost over a year for our main C++ developer to start using VS 2005, having moved away from VS 6. I think he should enjoy the changes in VS2008 for VC++.
  
  Regards