Problem with expression evaluation should contain expression in question

[PK1A]

Consider this example: {myCollection | myFilter}. It might happen that the filtering expression (myFilter) is neither a function nor an object containing the apply function. In this case the error thrown will be:

[error] [function expression] Object is not a function:

Unfortunately this gives very little context about what is actually wrong. IN the ideal world a message could read like this:

error evaluating expression "myFilter": Object is not a function in "/template/name.hsp"

Otherwise it is rather hard to figure out what is going on in a more complex page.

Related to #234 but this issue specifically asks to have info about an expression being evaluated.

[PK1A]

This got fixed with the migration to the Pratt's parser. For example using an invalid expression with the pipe operator will result in this message:

Error evaluating expression 'name | foo': Pipe expression is neither a function nor an object with the apply() method

See: http://plnkr.co/edit/ln7Gsinhf0gPCS1I2Roc?p=preview