Skip to main content
Code Review

Return to Answer

Commonmark migration
Source Link

#Don’t write using namespace std;.

Don’t write using namespace std;.

#Don’t write using namespace std;.

Don’t write using namespace std;.

Punctuation fix
Source Link
Toby Speight
  • 87.7k
  • 14
  • 104
  • 325

You can, however, in a CPP file (not H file), or inside a function, put individual using using std::string; etc. (See SF.7.)

You can, however, in a CPP file (not H file) or inside a function put individual using std::string; etc. (See SF.7.)

You can, however, in a CPP file (not H file), or inside a function, put individual using std::string; etc. (See SF.7.)

deleted 1 character in body
Source Link
Daniel
  • 4.6k
  • 2
  • 18
  • 40

Don’t use the C NULL macro (ES.47). But, don’t write explicit tests against nullptr’. ([ES.87](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#es87-dont-add-redundant--or--to-conditions)) Use the contextual conversion to nullptrbool`. (ES.87 ) Use the contextual conversion to bool, which works efficiently for raw pointers and any kind of smart pointer instance.

Don’t use the C NULL macro (ES.47). But, don’t write explicit tests against nullptr’. ([ES.87](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#es87-dont-add-redundant--or--to-conditions)) Use the contextual conversion to bool`, which works efficiently for raw pointers and any kind of smart pointer instance.

Don’t use the C NULL macro (ES.47). But, don’t write explicit tests against nullptr. (ES.87 ) Use the contextual conversion to bool, which works efficiently for raw pointers and any kind of smart pointer instance.

add pointers to Standard Guidelines.
Source Link
JDługosz
  • 11.7k
  • 19
  • 40
Loading
added 692 characters in body
Source Link
JDługosz
  • 11.7k
  • 19
  • 40
Loading
Source Link
JDługosz
  • 11.7k
  • 19
  • 40
Loading
lang-cpp

AltStyle によって変換されたページ (->オリジナル) /