   VC++ 6.0  Just died...
  I was just using vc++ 6.0 to program my clickyizer program...It was working great when, all of a damn sudden, it started giving me "INTERNAL COMPILER ERROR" as the only error...I restarted the app but nothing.  I looked it up on msdn and it told me to use the /Bd compiler option to pin point the problem....That crashed the compiler (not ide).  What''s going on here? 
  I got that message before....but I forget what causes them...the compiler is not malfunctioning, but I think there is something with your code that it can''t compile. ;  VC++ 6.0 = erm...I''d recommend going to .NET 2002 or 2003 if you can afford it. You don''t have to use the .NET libraries if you don''t want to, and it''s a whole lot more standards complient. I haven''t had any troubles with 2003 so far, where before I could hardly get 6.0 to work 50% of the time. ;  Fixed...I just restarted my comp... ;quote:Original post by Raloth  VC++ 6.0 = erm...I''d recommend going to .NET 2002 or 2003 if you can afford it. You don''t have to use the .NET libraries if you don''t want to, and it''s a whole lot more standards complient. I haven''t had any troubles with 2003 so far, where before I could hardly get 6.0 to work 50% of the time.   I can get it at any time from my father''s work place...I just need to concentrate my energies for a second... ;quote:Original post by tHiSiSbOb  Fixed...I just restarted my comp...   lolI hate programs like that, for example I had a problem running DX5 programs so I restarted after a month of having my computer on and it worked fine ... damn those programs gave me days of problems.   Pumpkin Pieman - [Blogger]Go to war again, blood is freedom''s stain, But don''t you pray for my soul anymore. ;  "INTERNAL COMPILER ERROR" can mean your program is so fucked up that the compiler cannot make any sense out of it.Using language features at the border of what''s implemented in VC6 may also give you similar problems (e.g. partial template specialization, or VC being anal about where to put which declaration).Finally you''ll definitely get that error if you violate compiler hard-coded limitations (too many variables, too many levels of template recursion, too many levels of nesting ...)   “Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”    — Brian W. Kernighan (C programming language co-inventor);  My compiler has done that right after I''ve run it without a hitch a second before.  This happens more often when I''m using DirectX programs.  I too wonder, what could be the cause of this?   Charles Hwang    -aka Tazel[Maxedge My Site(UC)|E-mail|NeXe|NeHe|SDL][Google|Dev-C++|GDArticles|C++.com|MSDN];  I had one of these recently, when trying to use boost::tokenizer to seperate the command line into component arguments.Hopefully, the payment will have come through and my copy of VS.NET 2003 (Academic License) will be arriving sometime after the 22nd. Bye bye VC6... ;quote:Original post by superpig  I had one of these recently, when trying to use boost::tokenizer to seperate the command line into component arguments.Hopefully, the payment will have come through and my copy of VS.NET 2003 (Academic License) will be arriving sometime after the 22nd. Bye bye VC6...   I am using .NET ''03 and I have gotten that error before.  It happened when I accidentally but a semicolon after a #define.  It had my compiler completely confused.  