- first version. Only uses simple hex shapes for the blocks.

- expose point field throughout

- make output less verbose, but can switch on/off with verbose() static method

- Unless the points(), cells(), patches() methods are called, the classes
  should know maintain a lightweight representation for as long as possible.

- bugfix: old-code used xferMove() instead of xferCopy() when creating the
  topology mesh - causing const pointField& to break if the code order was
  changed

- relocate blockMesh from src/meshing -> src/mesh

- read ~OpenFOAM/foamCopySettings.rc file for an extra rsync options
  for example, to ignore post-processing or sampling directories

- avoid other degenerate sequences from being treated as a scalar
  eg, '1-e', '1e+', '1e.2'

- for alphanumeric sequences (optionally with [-+.]) that don't look
  like a float or int -> return as a word

  This means that '0patch' now looks like a <word> (not <label>)
  and '1.end' looks like a <word> and not <scalar>

  Something like '1-e' still does get treated as a bad <scalar> though

- require a digit somewhere. This traps '.' or '.+E' type of sequences
  instead of returning them as 0

- avoid buffer overruns on really long sequences

- should we be considering strtod() as an alternative to atof() and checking
  the errno?
  The same might be true for using strtoul() or strtol() instead of atol()

- solves problems that can occur when checking $PWD and links are involved

- it looks okay to include: same copyrights as the other ensight headers

- still using the same version of the reader API (2.03)

- this seems to solve strange issues with genericPatchField symbols,
  but it still doesn't get the reader module working.

- added in the release information (the build string)

- also have it use LIB_LIBS to always load finiteVolume

which need this functionality.  Solvers will now check the correctness of the BCs on
read.