Note that there are some explanatory texts on larger screens.

plurals
  1. POGood Idea / Bad Idea Should I Reimplement Most Of C++?
    primarykey
    data
    text
    <p>Recently, I've got a dangerous idea into my head after reading <a href="http://www.codinghorror.com/blog/archives/001145.html" rel="noreferrer" title="Don&#39;t Reinvent The Wheel, Unless You Plan on Learning More About Wheels">this</a> blog post. That idea can be expressed like this:</p> <p>I don't need most of what the C++ standard library offers. So, why don't I implement a less general, but easier to use version?</p> <p>As an example, using the STL spits out reams of incomprehensible and mangled compiler errors. But, I don't care about allocators, iterators and the like. So why don't I take a couple of hours and implement an easy to use linked list class, for example?</p> <p>What I'd like to know from the StackOverflow community is this: what are the dangers, possible disadvantages and possible advantages to "rolling my own" for most of the existing functionality in C++?</p> <p><strong>Edit:</strong> I feel that people have misunderstood me about this idea. The idea was to understand whether I could implement a <strong>very</strong> small set of STL functionality that is greatly simplified - more as a project to teach me about data structures and the like. I don't propose re-inventing the entire wheel from the ground up, just the part that I need and want to learn about. <strong>I suppose what I wanted to figure out is whether the complexity of using the STL warrants the creation of smaller, simpler version of itself.</strong></p> <p><strong>Re-using boost or similiar.</strong></p> <p>Most of what I code is for University and we're not allowed to use external libraries. So it's either the C++ standard library, or my own classes.</p> <p><strong>Objectivity of this question.</strong></p> <p>This question is <strong>not</strong> subjective. Nor should it be community Wiki, since it's not a poll. I want concrete arguments that highlight one advantage or one disadvantage that could <strong>possibly</strong> occur with my approach. Contrary to popular belief, this is not opinion, but based on experience or good logical arguments.</p> <p><strong>Format.</strong></p> <p>Please post only one disadvantage <strong>or</strong> one advantage per answer. This will allow people to evaluate individual ideas instead of all your ideas at once.</p> <p><strong>And please...</strong></p> <p>No religious wars. I'm not a fan boy of any language. I use whatever's applicable. For graphics and data compression (what I'm working on at the moment) that seems to be C++. Please constrain your answers to the question or they will be downvoted.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload