Back to Arangodb

Naming Conventions

3rdParty/boost/1.78.0/libs/gil/doc/html/naming.html

3.12.9.11.4 KB
Original Source

Naming Conventions

Description of established naming conventions used in source code of GIL, tests and examples.

Concrete Types

Concrete (non-generic) GIL types follow this naming convention:

ColorSpace+BitDepth+[f|s]+[c]+[\_planar]+[\_step]+ClassType+\_t

where:

  • ColorSpace indicates layout and ordering of components. For example, rgb, bgr, cmyk, rgba.
  • BitDepth indicates the bit depth of the color channel. For example, 8,16,32.
  • By default, type of channel is unsigned integral. The s tag indicates signed integral. The f tag indicates a floating point type, which is always signed.
  • By default, objects operate on mutable pixels. The c tag indicates object operating over immutable pixels.
  • _planar indicates planar organization (as opposed to interleaved).
  • _step indicates special image views, locators and iterators which traverse the data in non-trivial way. For example, backwards or every other pixel.
  • ClassType is _image (image), _view (image view), _loc (pixel 2D locator) _ptr (pixel iterator), _ref (pixel reference), _pixel (pixel value).
  • _t suffix indicaes it is a name of a type.

For example:

bgr8\_image\_ta;// 8-bit interleaved BGR imagecmyk16\_pixel\_tb;// 16-bit CMYK pixel value;cmyk16c\_planar\_ref\_tc(b);// const reference to a 16-bit planar CMYK pixel.rgb32f\_planar\_step\_ptr\_td;// step pointer to a 32-bit planar RGB pixel.