Use parallel_for instead of a pipeline in implementation3 of WorkStream.
Merge pull request #298 from Rombur/workstream

Use parallel_for instead of a pipeline in implementation3 of WorkStream.
Add another testcase.

This is for the same problem as reported by Krishna Garikipati
on the mailing list this week. He verified that this used to fail
and works now, so I would like to add it to the testsuite to make
sure we don't regress in this functionality.
Merge pull request #299 from bangerth/add-test-2

Add another testcase.
Reorganize code a bit.

Change the code so that checking whether a function parser object
has already been created now happens at the place where we use
the object, rather than as an early exit in the init_muparser()
function. I find that this makes the code easier to read.

This also allows us to remove the creation of a parser object on the
thread where the object is actually created. In many (most) cases,
we will simply create the parser later on anyway, but not necessarily.
Clean up documentation a bit.
Make an error message easier to read.

Enclose strings in <...> so that one can more easily see if there happen
to be spaces in untoward places.
Merge pull request #301 from bangerth/muparser-cleanups

Muparser cleanups
reindent dof_handler.h, doxygen fixups
Run wrapcomments.py, release step 0c
manually fix up @ref statements
Bugfix: Fix typo so that our step-graph gets build again...
Update blurbb for petsc and trilinos
update changes.h and tags for release
sort output of arpack/step-36_ar
Update codim_01.mpirun=3.debug.output
normalize parameter_handler_write_json.output for different boost versions
Merge pull request #342 from tamiko/doxygen_fixups_and_reindent

Release steps 0a 0b 0c 0d
Merge pull request #343 from tamiko/changes_and_doc_update

Release steps 0e 1 1a
Merge pull request #344 from tamiko/fix_some_tests

Fix a bunch of tests for simserv