Opened 16 years ago
Closed 14 years ago
#128 closed request (fixed)
Averagers should have interface against iterators
Reported by: | Peter | Owned by: | Peter |
---|---|---|---|
Priority: | major | Milestone: | yat 0.4 |
Component: | statistics | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
I suggest we remove interface against all containers and only have doubles and ranges.
Change History (5)
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|---|
Milestone: | later → 0.4 |
Priority: | trivial → major |
Summary: | AveragerWeighted add with DataLookupWeighted1D → Averagers should have interface against iterators |
Version: | → trunk |
comment:2 Changed 14 years ago by
We have decided:
- Averager classes should support iterators and not containers.
- The add functions should be members.
comment:3 Changed 14 years ago by
I found an annoying thing:
If we make add a range function a member function it will look something like
template<typename T> add(T first, T last);
and also we have the normal add function
add(double, u_int n=1);
These are kind of in conflict beacause if you write add(3,5)
compiler will choose template function and it wont compile because u_int has no operator*.
Therefore I think we keep add range functions as free functions.
Note: See
TracTickets for help on using
tickets.
We now have iterators and should use them.