Feature #517
Check GammaLib for C++ slicing
| Status: | Closed | Start date: | 09/21/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assigned To: | % Done: | 100% | ||
| Category: | - | |||
| Target version: | 00-08-00 | |||
| Duration: |
Description
The phenomenon of C++ slicing only occurred to me now (see Bug #516). It happened in the GModel access operator of the GModels class, which was finally resolved by using pointers.
The GammaLib interface should be screened for analogous problems. In particular the container classes may be subject to C++ slicing.
Recurrence
No recurrence.
History
#1
Updated by Knödlseder Jürgen almost 14 years ago
- Subject changed from Check GammaLib for C++ splitting to Check GammaLib for C++ slicing
- Description updated (diff)
#2
Updated by Knödlseder Jürgen almost 14 years ago
- Target version deleted (
00-07-00)
#3
Updated by Knödlseder Jürgen over 13 years ago
- Target version set to 00-08-00
#4
Updated by Knödlseder Jürgen over 13 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
A review of the code slicing has been started in view of the global code review (see #692).
Code slicing should primary occur in container classes, and I started to correct the GModels and GObservations classes for code slicing.
#5
Updated by Knödlseder Jürgen almost 13 years ago
- Status changed from In Progress to Closed
- Assigned To set to Knödlseder Jürgen
- % Done changed from 10 to 100
As the code review is now finished I hope that I also catched all code slicing problems.