This is a short of http:\/\/www.stroustrup.com\/Myths-final.pdf<\/p>\n
Myth 1: \u201cTo understand C++, you must first learn C\u201d<\/strong><\/p>\n C is almost a subset of C++, but it is not the best subset to learn first because C lacks the notational Busted!<\/p>\n Myth 2: \u201cC++ is an Object-Oriented Language\u201d<\/strong><\/p>\n 3. Myth 2: \u201cC++ is an Object-Oriented Language\u201d Busted!<\/p>\n Myth 3: \u201cFor reliable software, you need Garbage Collection\u201d<\/strong> If you have to pass an object around, don't use raw pointer<\/strong>. If it is possible, don't use pointer at all<\/strong>. If there exist only one owner at a time, use the move magic with rvalue reverences<\/strong>. If the object is shared by more than one owner, use std::shared_pointer<\/strong> to store a pointer. It implements a reference counting and deletes the object of nobody owns them anymore. Use auto<\/strong> and make_shared<><\/strong> for syntactic sugar.<\/p>\n Naked deletes<\/strong> are dangerous \u2013 and unnecessary in general\/user code. Leave deletes<\/strong> For resource management, I consider garbage collection a last choice, rather than \u201cthe solution\u201d or an ideal: Busted!<\/p>\n Myth 4: \u201cFor efficiency, you must write low-level code\u201d<\/strong><\/p>\n I have seen sort<\/strong> run 10 times faster than qsort<\/strong>. How come? The C++ standard-library sort is Generality and high-level code can beat low-level code. It doesn\u2019t always, of course, but the sort\/qsort<\/strong> comparison is not an isolated example. Always start out with a higher-level, precise, and type safe version of the solution. Optimize (only) if needed.\n<\/p><\/blockquote>\n Busted!<\/p>\n Myth 5: \u201cC++ is for large, complicated, programs only\u201d<\/strong><\/p>\n C++ is a big language. The size of its definition is very similar to those of C# and Java. But that does not After all, C++ is designed for flexibility and generality, but not every Busted!<\/p>\n Read the paper for detailed examples. This is a short of http:\/\/www.stroustrup.com\/Myths-final.pdf Myth 1: \u201cTo understand C++, you must first learn C\u201d C is almost a subset of C++, but it is not the best subset to learn first because C lacks the notational support, the type safety, and the easier-to-use standard library offered by C++ to simplify simple tasks. Consider […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[17,31],"class_list":["post-2158","post","type-post","status-publish","format-standard","hentry","category-allgemein","tag-cpp","tag-faster-code"],"_links":{"self":[{"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/posts\/2158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2158"}],"version-history":[{"count":3,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/posts\/2158\/revisions"}],"predecessor-version":[{"id":2161,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=\/wp\/v2\/posts\/2158\/revisions\/2161"}],"wp:attachment":[{"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2158"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/roboblog.fatal-fury.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nsupport, the type safety, and the easier-to-use standard library offered by C++ to simplify simple tasks<\/strong>.
\nConsider a trivial function to compose an email address:\n<\/p><\/blockquote>\n
\nC++ supports OOP and other programming styles<\/strong>, but is deliberately not limited to any narrow view
\nof \u201cObject Oriented.\u201d It supports a synthesis of programming techniques including object-oriented and
\ngeneric programming<\/strong>. More often than not, the best solution to a problem involves more than one style
\n(\u201cparadigm\u201d). By \u201cbest,\u201d I mean shortest, most comprehensible, most efficient, most maintainable, etc.\n<\/p><\/blockquote>\n
\nIn short:
\nNever use new or delete<\/strong>. Use some classes which does the memory management for you, e.g. std::vector<\/strong>. For short living object, create them on the stack<\/strong>, Instead on the heap with new. Use destructor<\/strong> to clean up memory (and other resources like file handles) if the lifetime of an object comes to an end.<\/p>\n
\ninside resource management classes, such as string, ostream, thread, unique_ptr<\/strong>, and shared_ptr.<\/p><\/blockquote>\n
\n1.Use appropriate abstractions that recursively and implicitly handle their own resources. Prefer such objects to be scoped variables.
\n2. When you need pointer\/reference semantics, use \u201csmart pointers\u201d such as unique_ptr<\/strong> and
\nshared_ptr<\/strong> to represent ownership.
\n3. If everything else fails (e.g., because your code is part of a program using a mess of pointers
\nwithout a language supported strategy for resource management and error handling), try to
\nhandle non-memory resources \u201cby hand\u201d and plug in a conservative garbage collector to handle
\nthe almost inevitable memory leaks. <\/p><\/blockquote>\n
\nclearly at a higher level than qsort<\/strong> as well as more general and flexible<\/strong>. It is type safe<\/strong> and parameterized
\nover the storage type<\/strong>, element type<\/strong>, and sorting criteria<\/strong>. There isn\u2019t a pointer, cast, size, or a byte in
\nsight<\/strong>. The C++ standard library STL, of which sort is a part, tries very hard not to throw away information<\/strong>. This makes for excellent inlining and good optimizations<\/strong>.\n<\/p><\/blockquote>\n
\nimply that you have to know every detail to use it or use every feature directly in every program. <\/p><\/blockquote>\n
\nprogram has to be a complete library or application framework.<\/p><\/blockquote>\n
\nBusted!!<\/p>\n","protected":false},"excerpt":{"rendered":"