What do you think?
Rate this book
C++ Core Guidelines
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
December 16, 2017
Определено я четох на доста ранен етап от развитието на документа. Както и пише в началото, той е все още непълен и неточен. Макар и да има определени интересни напътствия, прилича повече на записки от университета с около 1/3 пропуснати лекции - има дупки в номерацията на точките, има празни точки, има точки, описани само с въпросителни (!?). Може би, когато документът бъде завършен, би бил добро ръководство, но има доста време дотогава.
January 5, 2019
Very useful especially with the Microsoft Guideline Support Library (https://github.com/Microsoft/GSL), which I now use in my projects.
Only reason this isn’t 5 stars is the guidelines aren’t complete as of this review, and the Microsoft GSL has some quirks.
Only reason this isn’t 5 stars is the guidelines aren’t complete as of this review, and the Microsoft GSL has some quirks.
May 10, 2017
As a book –in terms of formatting, arrangement of sections, etc...– these guidelines are in a very early stage. They contain typos and mistakes (as they clearly advertise in the opening paragraph) and repeated content. Besides that, they are not really meant to be read as a book, but rather as the foundations to write tools to enforce good C++ code.
However, the guidelines themselves are really useful and valuable. Some of them might be initially surprising (like recommending to use naked pointers instead of smart pointers as input arguments when ownership is not transferred), but after a while one realises that it is all for readability: the idea is that by looking at a function signature, one can guess what the implications are. If you pass in a shared_ptr, you are implying that the receiving function "participates" in the lifetime of that object. If you pass a naked pointer (maybe annotated with not_null), you simply say that this function will use the object.
If you are into (modern) C++, this is a very useful resource. In its current shape this isn't the most entertaining thing to read, but I wouldn't be surprised if some authors end up writing proper technical books with excerpts and selections of this materials.
However, the guidelines themselves are really useful and valuable. Some of them might be initially surprising (like recommending to use naked pointers instead of smart pointers as input arguments when ownership is not transferred), but after a while one realises that it is all for readability: the idea is that by looking at a function signature, one can guess what the implications are. If you pass in a shared_ptr, you are implying that the receiving function "participates" in the lifetime of that object. If you pass a naked pointer (maybe annotated with not_null), you simply say that this function will use the object.
If you are into (modern) C++, this is a very useful resource. In its current shape this isn't the most entertaining thing to read, but I wouldn't be surprised if some authors end up writing proper technical books with excerpts and selections of this materials.
February 5, 2017
Not great, to be honest. There shouldn't be so much to remember. Also, as it is an unfinished work, there are a number of things not explained at all.
Displaying 1 - 4 of 4 reviews