3 ms·
There are codebases out there that don’t use a lot of TMP and prefer Java-like type management. To each their own, but yeah, your experience matches mine.
by stingraycharles 5mo ago
There are codebases out there that don’t use a lot of TMP and prefer Java-like type management.
To each their own, but yeah, your experience matches mine.
- pjmlp 5mo ago90's C++ you mean, a decade before Java came to be, and responsible for famous books like GoF.
- aardvark179 5mo agoThe GoF book came out in 94, and Java in 95.
- pjmlp 5mo agoYes, have I said otherwise? It is a book that plenty think it has Java in it, no it has Smalltalk and C++ and was published before Java came to be as you point out. The decade was about the book publishing date, rather all the C++ frameworks that came to the market since CFront 2.0 was made available in 1989, and yes it was exactly 7 years, if being pedantic.
- layer8 5mo ago90's C++ already had templates, so “Java-like” is a more succinct descriptor, it doesn’t imply the direction of historical ancestry.
- pjmlp 5mo agoYes, and? First of all they were extremely buggy back then, as anyone that actually used Stepanov's original implementation, from HP with docs hosted at SGI, will remember. Secondly, Turbo Vision, OWL, VCL, MacApp, PowerPlant, Tools.h++, RogueWave Collection Classes, MFC, wxWidgets, Gtkmm, Qt, PÖET, COM/OLE/ActiveX, CORBA, Copland, BeOS predate Java, not the other way around.
- layer8 5mo agoYou were criticizing the use of “Java-like”. IMO it gets the point across much better here than “90's C++”. It has nothing to do with what predates what.
- pjmlp 5mo agoYes, because it is completely wrong. It isn't writing C++ as Java, it is writing C++ as it was common between 1990 and 2011, before C++11 and other programming techniques took over in the C++ world, highly influenced by Andrei Alexandrescu's book "Modern C++ Design", published in 2001.
- deleted 5mo ago[deleted]