#225 closed defect (fixed)
SplineEval, PolyEval, argument order.
| Reported by: | Owned by: | eugene | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | IPP SDRS | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The following are example instances of these functions:
psPolynomial1DEval(x, myPoly);
psSpline1DEval(mySpline, x);
note how the order of the arguments differs. Should we correct this order?
Change History (3)
comment:1 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 22 years ago
| Keywords: | VERIFIED added |
|---|
Closing subsequent to release of SDRS-08, ADD-07.
comment:3 by , 22 years ago
| Keywords: | VERIFIED removed |
|---|
Note:
See TracTickets
for help on using tickets.

I've rationalized this by having all of these evaluation functions specify the
function to be evaluated first followed by the coordinate(s).
double psDPolynomial1DEval(const psDPolynomial1D *restrict f, double x);
psVector *psDPolynomial1DEvalVector(const psDPolynomial1D *f, const psVector *x);
psF64 psSpline1DEval(const psSpline1D *spline, float x);
psVector *psSpline1DEvalVector(const psSpline1D *spline, const psVector *x);