id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
46	psImageClip/psImageClipNaN use of float parameters	robert.desonia@…	eugene	"psImageClip/psImageClipNaN uses floats for such parameters as min,max,vmin,vmax,
 and value.

The problem is that this function is to support a slew of datatypes, including
complex, double-precision float, and integers.

psC32/psC64: should I compare the absolute value of the complex pixel value to
the float?  Should I then just set the complex number to the given float (i.e.,
a zero imaginary component)? 

psC64/psF64: the value I'm comparing to and possible setting to is less
precision than the pixel values; is that really fine?

Maybe the better thing to do is make things like min/max/vmin/vmax/value (or at
least vmin/vmax/value) to be void*, which points to the same datatype as the
image pixels.  That should fix the precision/complex problems above.  Another
option is to reevaluate the need for these functions for things like complex
imagery."	defect	closed	high		PSLib SDRS	unspecified	normal	fixed