Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Programming IT Technology

Visual C++ and C++ Standard 31

Screaming Lunatic writes: "There is an interview over at codeproject about the future of C++ and .NET. Since I don't really care about .NET, the interesting part of the article is about the quest to standarize Visual C++. If you're going to code for Windows, Visual C++ is one of your few choices for a IDE/compiler combo. (Even though, if I'm not mistaken, you can hook gcc up to the IDE.) M$ seems somewhat in favor of conforming to the C++ standard, which is surprising. They talk about pushing forward with template compliance. I'm still waiting for them to get the variable declarations in for-loops right. They also claim to beat several popular compilers in compliance tests."
This discussion has been archived. No new comments can be posted.

Visual C++ and C++ Standard

Comments Filter:
  • by Mik!tAAt ( 217976 ) on Thursday November 15, 2001 @02:50AM (#2567689) Homepage
    Microsoft's goal is to have a 'competitively compliant' compiler - meaning it won't be 100% compliant. There are a couple of features of the ANSI/ISO standard (for instance the 'export' keyword as applied to template classes) that won't be implemented because they are considered by Microsoft to be obscure and, at this stage, theoretical.

    Somebody please explain to me why would somebody consider export templates to be 'obscure' and 'theoretical'? If export templates aren't available, you have to put most of your code in header files (or at least use your .cpp files as header files), and that IMHO is just plain stupid.

    On the other hand, aiming for STL, Boost, Blitz and Loki compliance is a Really Good Thing.
    • > Somebody please explain to me why would
      > somebody consider export templates to
      > be 'obscure' and 'theoretical'?

      Even though its part of the standard, I'm
      not aware of any compiler that currently
      implements the 'export' keyword.

      Are you aware of any? Doesn't that pretty much
      make it 'obscure' & 'theoretical'?

      Kinda reminds me of the Knuth qoute:
      "Beware of the above code. I have only proven it correct, not tested it."
    • by devphil ( 51341 ) on Thursday November 15, 2001 @02:32PM (#2570412) Homepage


      Microsoft is definitely full of shit when they consider 'export' to be "theoretical" only. But implementing export is hard; witness the number of compilers that have managed to do it so far. I don't blame MS for putting it off; I blame MS for lying about their reasons for doing so. (If they'd just said, "Implementing this is a freakload of work and we'd rather point our engineers in a more revenue-profitable direction," then I could accept that, too.)

      The for-loop scoping bug has a command-line switch to toggle correct behavior. Unfortunately, with it on, large chunks of their own MFC code will no longer compile.

      Dinkumware [dinkumware.com] was contracted to provide the library for VC++. They have released their own patches (freely downloadable) to the library headers. With those patches applied, your library is as ISO-compliant as it can be given the (immense) deficiencies of the compiler itself.

      For me the big killer is templates -- lots of failures in things like partial specialization.

      My recommendation to others who have to work under Wintel: there are plenty of good compilers out there, and they're ALL better than VC++. Comeau, IBM, EDG, KAI, you name it...


      • The for-loop scoping bug has a command-line switch to toggle correct behavior. Unfortunately, with it on, large chunks of their own MFC code will no longer compile.

        That is currently the case with VC++ 6 (and always will be) but I believe that issue has been resolved in VC++ 7.
      • Being a developer who sits in editors all day
        I was absolutely amazed when a workmate said to
        me that I should perhaps code my for loops differently to allow for "microsoft shitness" in the scoping of variables. Like all software this is a bug and therefore excusable. What is NOT correct in my opinion is then coding LARGE well used libraries to rely on this bug to then compile thus locking people into using an incorrect scoping method.

        This is just plain wrong imho !!

        Rod
      • by UnknownSoldier ( 67820 ) on Friday November 16, 2001 @04:18PM (#2576499)
        > For me the big killer is templates -- lots of failures in things like partial specialization.

        Yeah, the lack of C++ conformance in MS VC is a real pita.

        However, Modern C++ Design: Generic Programming and Design Patterns Applied [amazon.com] by Andrei Alexandrescu has a clever sizeof() hack to work around this in VC6.

        Modern C++ Design is the most advanced C++ book out there, and EVERY C++ programmer should have this masterpiece. The perfect blend of generic programming and object orientation programming is just beautiful. (The multiparadigm support of C++ is what makes it so powerfull.)
  • for-loop variables (Score:2, Informative)

    by RupW ( 515653 )
    I'm still waiting for them to get the variable declarations in for-loops right.

    If you compile with the 'disable extensions' flag, /Za, then they already do.

    Even with extensions enabled, VC++ 7 will warn when there's a conflict between extended and correct behaviours:

    forvar.cpp(4) : warning C4288: nonstandard extension used : 'i' : loop control variable declared in the for-loop is used outside the for-loop scope; it conflicts with the declaration in the outer scope
  • for loop fix (Score:3, Informative)

    by cfreeze ( 146454 ) on Thursday November 15, 2001 @08:36AM (#2568252) Homepage
    I've dug through MSDN a while back and found this to work..

    #pragma warning(disable:4127) //Work around for broken for-scoping in VC++ 6
    • Are you absolutely sure that worked for you? How does disabling a compiler warning affect the for loop scoping issue?

      When I looked it up in MSDN I get the following:

      #pragma warning(disable:4127) // conditional expression is constant
  • IMHO, the C++ compiler part of Visual C++ is one of the few things that Microsoft didn't totally screw up. Unfortunately it is all the other junk, like MFC and the crummy code that the IDE's wizards produce, that ruin the development environment.

  • That wasn't an interview. That was Stanley's pet sycophant putting words into his mouth. ("Yessss, my preciousssss... The Stroustrapses is wanting to take away our language, preciousss...")

    I would really have liked to get a real straight answer as to VC++'s role in Microsplat's future. As it is, I'm just as confused as ever. Vague promises that it will be the power language of choice for .NET? But what is it now?

    I'll tell you what it is: it's the arcane black magic that the entire .NET system is built on! .NET is all about protecting the programmers from C++. Duh.

    I really would like to see a real interview with this guy--when he gets a grip on his task. For now, Stanley appears as confused as the rest of us.

    • As to the future of C++ in MS' plans, C++ is the only low-level language Microsoft has left. Although it is pretty much useless in the .NET-Web-Service world, there are still a few people writing traditional software left... such as Quake and Office for example...

      Giving up C++ would be pretty much equivalent to giving up all future development on Office and Windows, so I bet C++ will last a long long while in the Microsoft toolbox.
      • I pretty much agree apart from one thing:

        pretty much useless in the .NET-Web-Service world

        Not so sure myself. I was working on a plan for a SOAP type web service which does a shedload of complex calculations then throws the answer back. The only way I could see to get the performance was C++. OK, in VB/C# etc. 7 there is finally some control over things like threads, but the performance isn't there.For this sort of job, I like to be able to control exactly what the machine is doing (do you believe in the Windows task scheduler?) so I can adjust for amounts of memory, number of processors etc. Whilst this isn't impossible in other languages, it is damn hard.

        Admittedly, this is an obscure example, but I'm sure there are others. If you want the performance and features of C++, then the language you want is probably ... well ... C++. Put the features into VB and all you do is make is as complex as C++ - which is not what you want for a moron's dev tool. Horses for courses.

        Oh yeah, and if anyone says that performance doesn't matter - just wait for the hardware to get faster, well you obviously don't work with actuaries. The complexity of calculations they want to do moves a lot faster than Moore's Law.
  • I'd recommend Delphi 6. Its a very nice IDE and anything you develop can be easily ported to LINUX using KYLIX..

    GO BORLAND.

    PS. I don't develop for windows anymore but I used to. I've now moved on the much lusher pastures of OS X.
  • Right now I'm not using Microsoft Visual C++. I can't afford it. I do, however, want it. I really, really want it. Right now I'm using Dev C++ 4 from Bloodshed. It's open-source and free, but it can't do code completion like Microsoft can. It doesn't have those cool drop-down menus that offer you a list of all the functions in the class you just selected.


    Does anyone know of any free software that does code-completion and other time-saving features? I'd really appreciate a link, or even just a name. But I have looked, and I haven't been able to find an IDE that matched the apparent ease of MSVC. For now, I look upon my friends in envy.

  • You know, this is a really stupid article. slashdot's really starting to go downhill posting crap like this. And as for this screaming lunatic fellow, what kind of drugs are you on man?

A Fortran compiler is the hobgoblin of little minis.

Working...