Feature #692
Perform an extensive interface review of all classes
Status: | Closed | Start date: | 01/12/2013 | |
---|---|---|---|---|
Priority: | Urgent | Due date: | ||
Assigned To: | Knödlseder Jürgen | % Done: | 100% | |
Category: | - | Estimated time: | 204.00 hours | |
Target version: | 00-08-00 | |||
Duration: |
Description
We should review the interfaces of all classes to make sure that all interfaces are homogeneous and also complete. This is an important step towards the first stable release which will enter under interface control.
Here a couple of principles that should be respected during interface review:
- Each class should have a constructor that allows one-line construction of a meaningful objects.
This makes programming much easier, and prevents the need for a two step process for object creation (allocation and setting). The object constructor should take the most relevant parameters as arguments. Specific attributes can always be set using additional methods.
- If a class has an assignment method that assigns
n
elements of a given type (such as the std::vector.assign() method), the first argument is the number of elementsn
, followed by the element.
Recurrence
No recurrence.
Subtasks
Related issues
History
#1 Updated by Knödlseder Jürgen almost 12 years ago
- Target version set to 00-08-00
#2 Updated by Knödlseder Jürgen almost 12 years ago
- Status changed from New to In Progress
#3 Updated by Knödlseder Jürgen almost 12 years ago
- Assigned To set to Knödlseder Jürgen
#4 Updated by Knödlseder Jürgen almost 12 years ago
- Description updated (diff)
#5 Updated by Knödlseder Jürgen about 11 years ago
- Status changed from In Progress to Closed