No problem, I'd like to fix up the failing MOOSE tests (if any), and then
I'll force push that change to retest


On Mon, Apr 21, 2014 at 1:17 PM, jwpeterson <notifications@github.com>wrote:

> In include/numerics/parsed_function.h:
>
> > @@ -115,7 +115,11 @@ class ParsedFunction : public FunctionBase<Output>
> >          FunctionParserBase<Output> fp;
> >          fp.AddConstant("pi", std::acos(Real(-1)));
> >          fp.AddConstant("e", std::exp(Real(1)));
> > -        fp.Parse(subexpression, variables);
> > +        if (fp.Parse(subexpression, variables) != -1) // -1 for success
> > +        {
> > +          libMesh::err << "ERROR: FunctionParser is unable to parse expression: " << subexpression << '\n';
> > +          libmesh_error();
>
> Can you use
>
> libmesh_error_msg("ERROR: FunctionParser is unable to parse expression: " << subexpression << '\n');
>
> here instead? I'd like to start doing this everywhere eventually...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/libMesh/libmesh/pull/227/files#r11821572>
> .
>