Tim Atherton

Awesome, thanks @joshichaitanya3, I'll investigate this!

Is this still a problem @joshichaitanya3 ?

Can you provide a minimal example, @ancaandrei? This would really help us understand the bug.

I think what would be a great idea here is if the resource finder locates a "nearby" resource, we could offer an error: Module 'MeshGen' not found; did you mean...

This should throw undefined forward reference. Forward references MUST be resolved in the same scope.

I can see what's going on here. The compiler is catching the forward reference to mobiusfn inside the anonymous function, and so allocates a register in mobius which is supposed...

Currently forward references are really intended primarily to implement mutual recursive functions. The current limitation is that they have to be resolved in the scope in which they occur, i.e....

I just checked and this edge case is still active in 0.6.1 — this is a compiler bug todo with register allocation.

Fixed by #276 (and possibly earlier). * The supplied program now generates "Expression expected" error. * Added a test class/syntax_error_in_constructor.morpho to check this works correctly. Thankyou @ConduitDan for this report;...

@joshichaitanya3 I fixed this and updated the PR. There was an issue in how the sparse matrix addition was being performed.