C + + Programming specification (constantly updated)

This article summarizes some of the lessons learned to make the compiled code more robust. 1. Do not conflict with system functions when defining classes/structs (especially when porting between different systems/platforms)

Sometimes it's okay to compile under windows, but not on Linux, because Linux has the same name function.

A little bit better the compiler will prompt: Must use ' class/struct ' tag to refer-type ' XXX ' in the this scope; an almost-perfect compiler can't find a type and throws a bunch of errors, which makes people feel confused.

There are two solutions at this time, one that you define yourself as a class or struct (which can be mixed) when you use it, and another way to get rid of the class name/struct name you define.

C + + Programming specification (constantly updated)