On 04/22/2024 07:59 AM, Stefan Ram wrote:
How many of you have read through the C++ spec, like, all the
way through?
Have you guys checked out the latest version of the C++ spec yet?
I was just browsing around and I stumbled upon this little
guide in the WHATWG HTML spec on how to properly read through
these kinds of technical specifications!
|1.9.1 How to read this specification
|
|This specification should be read like all other
|specifications. First, it should be read cover-to-cover,
|multiple times. Then, it should be read backwards at least
|once. Then it should be read by picking random sections from
|the contents list and following all the crossreferences.
|
HTML Living Standard - Last Updated 9 April 2024
That's great.
I got a lot out of reading "the book", Stroustrup's, then
it reminds me of Harbison and Steele C/C++, and Schildt, the
"Effective C++", some good code with smart pointers,
the I/O streams book or Langer and Kreft, bunch of
Win32 then into COM/DCOM if because, then sort of
about m4 and C/C++ then getting into when .h went to .hpp
then there's much to learn about copy and move and the
in-place and a bunch of sorts great things.
(I'm still sort of learning C99 and C++ 98.)
That's great, though, at least "it should be read".
On 04/22/2024 07:59 AM, Stefan Ram wrote:
How many of you have read through the C++ spec, like, all the
way through?
Have you guys checked out the latest version of the C++ spec yet?
I was just browsing around and I stumbled upon this little
guide in the WHATWG HTML spec on how to properly read through
these kinds of technical specifications!
|1.9.1 How to read this specification
|
|This specification should be read like all other
|specifications. First, it should be read cover-to-cover,
|multiple times. Then, it should be read backwards at least
|once. Then it should be read by picking random sections from
|the contents list and following all the crossreferences.
|
HTML Living Standard - Last Updated 9 April 2024
That's great.
I got a lot out of reading "the book", Stroustrup's, then
it reminds me of Harbison and Steele C/C++, and Schildt, the
"Effective C++", some good code with smart pointers,
the I/O streams book or Langer and Kreft, bunch of
Win32 then into COM/DCOM if because, then sort of
about m4 and C/C++ then getting into when .h went to .hpp
then there's much to learn about copy and move and the
in-place and a bunch of sorts great things.
(I'm still sort of learning C99 and C++ 98.)
On 04/23/2024 12:54 AM, David Brown wrote:
On 23/04/2024 04:18, Ross Finlayson wrote:
On 04/22/2024 07:59 AM, Stefan Ram wrote:
How many of you have read through the C++ spec, like, all the
way through?
Have you guys checked out the latest version of the C++ spec yet? >>>>
I was just browsing around and I stumbled upon this little
guide in the WHATWG HTML spec on how to properly read through
these kinds of technical specifications!
|1.9.1 How to read this specification
|
|This specification should be read like all other
|specifications. First, it should be read cover-to-cover,
|multiple times. Then, it should be read backwards at least
|once. Then it should be read by picking random sections from
|the contents list and following all the crossreferences.
|
HTML Living Standard - Last Updated 9 April 2024
A much better choice than reading the C++ standards, for most purposes,
is the web site <https://en.cppreference.com/w/>. It is strongly
associated with the ISO working group for C++, and about as close to an
official reference site for C and C++ (core languages and standard
libraries) as you can get. But it is organised as a reference site, not
as a standards document. The site is not a C++ tutorial or something to
read from start to finish, but it is the best place to look things up.
That's great.
I got a lot out of reading "the book", Stroustrup's, then
it reminds me of Harbison and Steele C/C++, and Schildt, the
"Effective C++", some good code with smart pointers,
the I/O streams book or Langer and Kreft, bunch of
Win32 then into COM/DCOM if because, then sort of
about m4 and C/C++ then getting into when .h went to .hpp
then there's much to learn about copy and move and the
in-place and a bunch of sorts great things.
(I'm still sort of learning C99 and C++ 98.)
Don't bother. That's like saying you want to learn to drive a car, but
are still getting the hang of a horse and cart.
The current C standard is C17, which is just a minor tweak on C11. If
you want to learn C, target C11 - it turned C into a language with
support for multiple threads. Most of the language is the same as C99,
however. (C23 is not yet officially published, AFAIK, even though it
can be considered functionally complete. Compiler support is not
finished yet.)
For C++, things changed so dramatically with C++11 that it is often
considered a new language, and there have been significant improvments
in the language since then. Well-written modern C++ looks as different
from C++98 as it does from C. If you are looking for some kind of
tutorial book, make sure it is based on at least C++17 (and by "based
on", I mean that's the language taught in the book - not just a "What's
new in C++17" appendix add-on).
When cppreference arrived it was a great thing,
cross-referenced hyper-linked language, library,
and language level coverage.
I derived value and some entertainment from
Stroustrup's and Sutter's C++ guidelines,
moreso than the Google C++ guidelines.
These days it does look like C++ 11 would be about
the way of things, for somebody last familiar with
"MSVC6 SP3/SP6", though it was great for the Windows
side when they released a C++ compiler, to complement
things like Djgpp, Mingw64, Navia's lcc, and these
kinds of things, vis-a-vis Borland, about a world
where gcc/g++/gpp is a great thing.
How many of you have read through the C++ spec, like, all the
way through?
Have you guys checked out the latest version of the C++ spec yet?
I was just browsing around and I stumbled upon this little
guide in the WHATWG HTML spec on how to properly read through
these kinds of technical specifications!
|1.9.1 How to read this specification
|
|This specification should be read like all other
|specifications. First, it should be read cover-to-cover,
|multiple times. Then, it should be read backwards at least
|once. Then it should be read by picking random sections from
|the contents list and following all the crossreferences.
|
HTML Living Standard - Last Updated 9 April 2024
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 489 |
Nodes: | 16 (2 / 14) |
Uptime: | 57:03:04 |
Calls: | 9,673 |
Calls today: | 4 |
Files: | 13,719 |
Messages: | 6,171,089 |