I don’t really mind format since “pixel format” is pretty common. I would strongly prefer datatype over dtype though for clarity’s sake.
On Thu, 30 Dec 2021 at 09:41, Larry Gritz <l...@larrygritz.com> wrote: > Early on (and probably borrowing from prior software), I used > ImageSpec.format as the field describing the data type of the pixel values. > > I've long though that this was an unfortunate mistake, primarily because > it causes endless confusion about the difference between "data format" and > "file format", and awkward phrasing in the documentation. > > Question 1: Does anybody else care? Or is it fine? > > Question 2: If you care, would you like to see me slowly and deliberately > migrate to different terminology, both in the docs and what things are > called in code (functions, struct fields, named parameters, etc.)? Or is > the pain of any changes that would require client code to be edited worse > than the forever-tax of having chosen a confusing name? > > Question 3: If you think we should make changes, what is a more > appropriate name to use? NumPy (which I think is widely used by our > constituency) uses "dtype", so I believe that's a strong contender because > of its existing familiarity, relative clarity, lack of conflict with any > other names or concepts we use, and short name. Or "datatype"? Or something > else? (Suggestions welcome.) > > > -- > Larry Gritz > l...@larrygritz.com > > > > > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
