Add fparser_parse app

This is meant to be useful for debugging problems with fparser
strings, and right now it seems useful for debugging problems with
fparser...
Re-run bootstrap
Added interpolation points mesh getter in RBEIMEvaluation
Merge pull request #371 from danac/master

Interpolation points mesh getter in RBEIMEvaluation
Delete trailing whitespace from source.
Removing tabs for source and examples.
Use libmesh_error_msg where appropriate.
Guard use of exceptions with LIBMESH_ENABLE_EXCEPTIONS.
Regenerating the fpoptimizer.cc file after recent bugfixes by @dschwen.
Change libmesh_example_assert -> libmesh_example_requires
Merge pull request #372 from libMesh/rebuild_fpoptimizer

Regenerating the fpoptimizer.cc file after recent bugfixes by @dschwen
Merge pull request #366 from libMesh/fparser_parse

Fparser app
Use old file format in reference_elem.data for Pyramid13 and Pyramid14

Either read_ref_elem() and reference_elem.data need to be updated to
read the extra fields in 'contemporary' xda files, or the contents of
reference_elem.data need to conform to the read_ref_elem() implementation.
For now, I've chosen the latter.  This fixes the new subdomains_ex3
example for me.
In TBB mutex'es are no longer copy constructable.

I don't think these need to be, either, so long as a new object gets default-constructed that can be locked.

From, https://www.threadingbuildingblocks.org/sites/default/files/resources/CHANGES_0.txt

Changes affecting backward compatibility:

- For compatibility with C++11 standard, copy and move constructors and
    assignment operators are disabled for all mutex classes. To allow
    the old behavior, use TBB_DEPRECATED_MUTEX_COPYING macro.
barebones fix
Update traffic.
Update LOC count for October 2014.
Adding Garg, 2014.
Don't test for C++11 features when the compiler doesn't support it
(or the user has explicitly disabled it).

In the former case, it's usually a foregone conclusion that the tests
will fail, in the latter we have seen some compilers (Clang 3.5.0)
that still support certain C++11 features like std::shared_ptr even
when the user has not passed the -std=c++11 flag.  To avoid confusion,
it's best to enforce C++03 code where possible for such compilers.

Note that you must call AM_CONDITIONAL outside of conditionals...
i.e. outside of the 'if enablecxx11==yes' check. Hence all the
re-indenting.
Ran bootstrap.