Refactoring #232
Refactoring #240: Renaming campaign
rename "min" and "max" in TRange, ...
| Status: | Archived | Start date: | 21 Mar 2013 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Sprint 18 |
Description
In my mind, "min" and "max" designate the lowest and highest value actually realized.
For the lowest and highest allowed value, I prefer "inf" and "sup" (infimum and supremum).
Btw: why is inRange(..) implemented assymmetrically? correct name would then be: inHalfOpenInterval(..).
Further name change proposal: getDifference() -> getSpan()
History
#1 Updated by wuttke over 7 years ago
Walter thinks, inf and sup are possibly confusing as well.
- compare stdlib
- prefer lower_bound, upper_bound ?
#2 Updated by wuttke over 7 years ago
- Parent task set to #240
#3 Updated by Anonymous almost 7 years ago
- Status changed from New to Backlog
- Assignee set to Anonymous
#4 Updated by Anonymous almost 7 years ago
- Status changed from Backlog to Sprint
- Target version set to Sprint 18
#5 Updated by Anonymous almost 7 years ago
- Status changed from Sprint to Resolved
#6 Updated by pospelov almost 7 years ago
- Status changed from Resolved to Archived