Slashdot Mirror

← Back to Stories (view on slashdot.org)

Downsides to the C++ STL?

Posted by Cliff on from the getting-the-whole-story dept.

craybob queries: "I'm a developer for a small software group that will soon migrate from using Rouge Wave to using the C++ STL. I just left the week-long Software Developers 2002 conference, where I heard the great minds in software tell us all of the best ways to take full advantage of the STL. (I just wanted to give a quick thanks to Stephen Dewhurst and Scott Meyers) From this I came away with the feeling that this is the Holy Grail of C++. I'm sure these guys are right and that it is great, but the truth is that I'm a skeptic, so what are the downsides to the STL?"

4 of 946 comments (clear)

  1. One Downside by jsonic · · Score: 5, Funny
    but the truth is that I'm a skeptic, so what are the downsides to the STL?

    It's written in C++? :)

  2. vector - vector<bool> by lkaos · · Score: 3, Funny

    Stupid HTML

    --
    int func(int a);
    func((b += 3, b));
  3. Re:Not many drawbacks by Viking+Coder · · Score: 4, Funny

    #define private public

    The one macro you'll ever need. Heh.

    --
    Education is the silver bullet.
  4. Re:* is faster than C (??) by Paul+Komarek · · Score: 3, Funny

    I thought you might be interested in some counterexamples. I don't think Intercal or Befunge advocates have ever claimed those languages were faster than C. In fact, I don't think they claimed Intercal or Befunge was better than any other language.

    -Paul Komarek