Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c++.moderated    |    Moderated discussion of C++ superhackery    |    33,346 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 31,957 of 33,346    |
|    =?ISO-8859-1?Q?Daniel_Kr=FCgler?= to All    |
|    Re: How many years of C++ experience is     |
|    29 Feb 12 03:53:10    |
      23fca627       From: daniel.kruegler@googlemail.com              Am 25.02.2012 22:52, schrieb P. Areias:       >> If you are stuck in a place where they still don't believe in templates and       the STL, 100 years of experience won't do any good.       >>       >       > Note that you are mixing, in one argument, the template       > parametrization mechanism with one of its applications (the Standard       > Library containers - or STL).              This is quite misleading. Even though STL is no official term of the       standard it is typically be translated as "Standard Template Library",       not "Standard Library Containers".              > The latter imposes an additional       > decision on what is now C++: the departure from object-oriented       > paradigm (for performance reasons). This is an issue.              C++ does not follow some special paradigm, and so does the library       reflect several paradigms - including object-oriented and functional. I       don't see how this is "an issue". It may be an issue, if you have very       special constraints on the types that you are using, maybe: All names       need to start with upper-case, all class types must have a virtual       destructor, among a lot of others. If the library would have required       virtual destructor for std::vector - just as an example, because you are       referring to containers - it would unnecessarily impose runtime       constraints on user code that would not take advantage of dynamic       polymorphism. If you need *additional* polymorphic containers, you can       build your own library (most parts in terms of non-polymorphic       containers like those from the Standard Library). If you think that your       polymorphic library is of interest for others as well, this could be a       very reasonable base for a corresponding proposal provided to the C++       Standard Committee.              Greetings from Bremen,              Daniel Krügler                            --        [ See http://www.gotw.ca/resources/clcm.htm for info about ]        [ comp.lang.c++.moderated. First time posters: Do this! ]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca