cpp: test: Allow stream operators to be found by ADL
cpp: test: Use constants of correct type in equality comparison
cpp: test: Only run death tests if supported by the platform
cpp: test: Remove unused variable in variantpixelbuffer
Fix empty string error
Update auto-generated documentation

Repository: snoopycrimecop/bioformats

Generated by BIOFORMATS-5.1-merge-docs-autogen#24 (http://ci.openmicroscopy.org/job/BIOFORMATS-5.1-merge-docs-autogen/24/)
Add branch-specific link for downloading the JAR file if unfound
cpp: test: Split pixelbuffer into multiple translation units

This instantiates the templated tests for one pixel type
per unit.  This is to work around travis failures due to
this file failing to build due to an internal compiler
error and/or memory problems on the build node.  The tests
run are unchanged.
Correct timebase for picoQuant .bin files.
Also modify link in bf.bat
Handle Java string comaparison properly
Handle Java string comaparison properly 2
Merge pull request #1297 from sbesson/rebased/develop/picoquant_doc

Add documentation for PicoQuant .bin format (rebased onto develop)
PrairieMetadata: keep reference to element parents

Specifically, each <File> now knows its <Frame>, and each <Frame> now
knows its <Sequence>. This will useful for handling the more compact XML
structure of PrairieView 5.x, in which parameter values are inherited
from parent elements where feasible.
PrairieReader: avoid NPE when CFG file is missing
PrairieMetadata: add an attribute accessor method

This returns null when the attribute is not present, rather than the
empty string. It also makes the code slightly shorter.
PrairieMetadata: add data structure for key/values

The key/value pair structure got more complex in PrairieView 5.2. Now
each key can point at either a single string item, or at a table of
values, which can themselves point at sub-tables.

This data structure is intended to facilitate easy management of the
new structure, while still supporting the old structure, too.
PrairieMetadata: add helpful helper methods

These are useful when dealing with possible null values.
PrairieMetadata: use ValueTable as appropriate
PrairieMetadata: parse old-style keys into tables

As of PrairieView 5.2, the key/value pair structure is more
hierarchical, with value tables able to contain sub-tables.

Let's parse the old-style keys in the same way, so that regardless of
which version of PrairieView wrote the data, it can be consumed in the
same way after parsing.