By Musser D.R., Derge G.J., Saini A.
Average Template Libraries (STL) have been created to supply C++ programmers with a set of rusable courses, or strains of code, which may be utilized by every body to extend programming productiveness and caliber. This publication is the definitive reference on C++ programming utilizing STL, because it used to be written by way of the group that created the library.
Read Online or Download C++ Programming with the Standard Template Library PDF
Best programming: programming languages books
- AntMe! Spielend programmieren lernen mit Visual Basic und den Ameisen
- Realisez vos bagues en perles de cristal
- Das Excel-VBA Premium Codebook
- Programmieren in C++: Einführung in den Sprachstandard C++
- Datenbanken in vernetzen Systemen mit PHP3 und mySQL
Additional resources for C++ Programming with the Standard Template Library
Bug Tracker One important tool, which we have used for SharpDevelop, is the bug tracker. It is an online application to which every team member can submit bugs: 39 Chapter 2 Whenever we had some spare time, these bugs were then resolved. The bug tracker is a tool that only team members can access. Prior to the bug tracker era, the bugs were filed on paper, but paper always tends to get lost. This application version of bug tracking is much more robust than the paper version. It also takes too much time to put all submitted bugs on paper.
The AddIn tree solved this problem and much more. The AddIn tree is capable of defining add-ins using an XML format as glue code, which might be placed almost anywhere using a path model. Once we started using this structure development sped up. We could safely add new extendable components, without breaking other parts of the source code. We could throw away bad components without harming the project. The XML definition of our AddIn tree was also inspired by Eclipse, it has a similar definition but eclipse works differently from the way SharpDevelop does.
With a bug tracker, one can just cut and copy the submitted bugs to a centralized database. We can even attach images, and track the bug's history. Before each release, it is our goal to fix as many bugs from the tracker, as we can manage. Let's now discuss the testing strategies that we used during the development of SharpDevelop. Unit Tests For a GUI application, it is more difficult to apply unit tests, but they too profit from unit testing. One important lesson we had to learn during the SharpDevelop project was that code should be written with tests in mind.