inconsistent handling of dimensioned types

In fixedPressureCompressibleDensityFvPatchScalarField, for example, it grabs values from the thermodynamicProperties dictionary:

const scalar rholSat = dimensionedScalar(thermoProps.lookup("rholSat")).value();

The dimensioned(Istream&) constructor forwards to read(Istream&) which requires name, dimensions, value. In other locations (including in a tutorial example), these quantities are treated as if name, dimensions are optional.