C++ - Revision history

Yingzhu: Yingzhu moved page C++ Development to C++

2021-01-21T18:04:18Z

Yingzhu moved page C++ Development to C++

← Older revision	Revision as of 18:04, 21 January 2021
(No difference)

2021-01-21T18:03:55Z

← Older revision		Revision as of 18:03, 21 January 2021
Line 1:		Line 1:
	==Tips==		==C++ Development Tips==

	===Minimize includes in headers===		===Minimize includes in headers===

2010-09-20T18:31:03Z

Advanced Topics

← Older revision		Revision as of 18:31, 20 September 2010
Line 185:		Line 185:

	to do		to do

			===Getting a list of pre-defined macros for gcc===

			touch dummy.hxx
			cpp -dM ./dummy.hxx

2010-05-11T17:12:17Z

← Older revision		Revision as of 17:12, 11 May 2010
Line 77:		Line 77:

	Of course macros still do get used in C++ (for example, in debugging calls, because only macros can usefully use the compiler define __LINE__). But look hard for an alternative before resorting to a macro.		Of course macros still do get used in C++ (for example, in debugging calls, because only macros can usefully use the compiler define __LINE__). But look hard for an alternative before resorting to a macro.

			===Prefer std::string to char arrays===

			char arrays are terribly prone to buffer overruns and memory leaks. They are quite tricky to get exactly right, and the resulting code is often obtuse. Use std::string instead and let it manage the fiddly resource allocation issues for you.

	===Prefer iostreams to printf and scanf===		===Prefer iostreams to printf and scanf===

2010-04-12T19:09:15Z

Don't reinvent the wheel

← Older revision		Revision as of 19:09, 12 April 2010
Line 158:		Line 158:
	* platform-independent file path handling (use boost/filesystem)		* platform-independent file path handling (use boost/filesystem)
	* fixed-length integers (e.g 64 bit). See next section.		* fixed-length integers (e.g 64 bit). See next section.
	* parsing command line options and/or reading config files (use boost/program_options)		* parsing command line options and/or reading config files (use boost/program_options and/or boost/propertytree)

	===Fixed length integers===		===Fixed length integers===

2010-04-12T18:36:21Z

Don't reinvent the wheel

← Older revision		Revision as of 18:36, 12 April 2010
Line 156:		Line 156:
	Here are some areas where you should definitely NOT be writing you own custom tools:		Here are some areas where you should definitely NOT be writing you own custom tools:
	* string manipulation		* string manipulation
	* platform-independent file path handling		* platform-independent file path handling (use boost/filesystem)
	* fixed-length integers (e.g 64 bit). See next section.		* fixed-length integers (e.g 64 bit). See next section.
			* parsing command line options and/or reading config files (use boost/program_options)

	===Fixed length integers===		===Fixed length integers===

2010-03-02T17:37:44Z

← Older revision		Revision as of 17:37, 2 March 2010
Line 27:		Line 27:
	Now the header file using forward declarations instead of including another header file:		Now the header file using forward declarations instead of including another header file:

	// File "myClass.h" - example of using forward declaration.		<source lang=c>
	class vtkImage // Forward declaration		// File "myClass.h" - example of using forward declaration.
			class vtkImage // Forward declaration
	class myClass
	{		class myClass
	public:		{
	myClass(); // Constructor		public:
	~myClass(); // Destructor		myClass(); // Constructor
	protected:		~myClass(); // Destructor
	vtkImage* image; // An image object in our class		protected:
	};		vtkImage* image; // An image object in our class
			};
			</source>

	Note that now we have a pointer instead of an actual instance of vtkImage. A forward declaration allows you to use only pointers and references to the foward-declared objects. This is because the compiler does not yet know how large the object is, but it does know how large a pointer is.		Note that now we have a pointer instead of an actual instance of vtkImage. A forward declaration allows you to use only pointers and references to the foward-declared objects. This is because the compiler does not yet know how large the object is, but it does know how large a pointer is.

2010-02-03T18:00:19Z

Prefer iostreams to printf and scanf

← Older revision		Revision as of 18:00, 3 February 2010
Line 98:		Line 98:
	On the other hand, the standard C++ stream formatting modifiers like this example, although overloaded to correctly match the variable type, tend to be overly verbose to conveniently use.		On the other hand, the standard C++ stream formatting modifiers like this example, although overloaded to correctly match the variable type, tend to be overly verbose to conveniently use.

	I recommend therefore using boost::format where specific formatting is required. It is overloaded and will correctly match the variable type and length, but can be used with the familiar and concise POSIX ~~formatting~~ strings. boost::format has already been adopted in the next official C++ standard. Here is an example using boost::format:		I recommend therefore using boost::format where specific formatting is required. It is overloaded and will correctly match the variable type and length, but can be used with the familiar and concise POSIX format strings. boost::format has already been adopted in the next official C++ standard. Here is an example using boost::format:

	std::cout << format("The result is %.3f\n") % x;		std::cout << format("The result is %.3f\n") % x;

2010-02-03T17:59:41Z

Prefer iostreams to printf and scanf

← Older revision		Revision as of 17:59, 3 February 2010
Line 98:		Line 98:
	On the other hand, the standard C++ stream formatting modifiers like this example, although overloaded to correctly match the variable type, tend to be overly verbose to conveniently use.		On the other hand, the standard C++ stream formatting modifiers like this example, although overloaded to correctly match the variable type, tend to be overly verbose to conveniently use.

	I recommend therefore using boost::format where specific formatting is required. It is overloaded and will correctly match the variable type and length, but can be used with the familiar and concise POSIX formatting strings. ~~boost~~ boost::format has already been adopted in the next official C++ standard. Here is an example using boost::format:		I recommend therefore using boost::format where specific formatting is required. It is overloaded and will correctly match the variable type and length, but can be used with the familiar and concise POSIX formatting strings. boost::format has already been adopted in the next official C++ standard. Here is an example using boost::format:

	std::cout << format("The result is %.3f\n") % x;		std::cout << format("The result is %.3f\n") % x;

2010-02-03T17:58:23Z

Advanced Topics

← Older revision		Revision as of 17:58, 3 February 2010
Line 168:		Line 168:

	===Forcing a C++ header to use C calling convention===		===Forcing a C++ header to use C calling convention===

			to do

	===Careful of the library link order on Linux===		===Careful of the library link order on Linux===

			to do

	===Declaring functions for shared libraries on Windows===		===Declaring functions for shared libraries on Windows===

			to do