Hi,
The user is making a mistake here. Yet I'm politely requesting for the
interpreter to continue, not terminate. Because of the uncaught thrown
exception at the C++ level, I'm presuming this condition was not considered
and so GNU APL robustness can be improved.
Step 1: Assure CONTINUE.xml does not exist in LIBREF-0. This is because
the failing testcase will need to create/overwrite CONTINUE.xml.
Step 2: create a little four line text file at /tmp/cc:
#!
∇f
1 →→
∇
Step 3: Under linux, run this pipeline:
echo ')continue' | apl -L /tmp/cc && apl
I get:
→→ without ←← (aka. IF without ENDIF). First observed on line [1], PC=1.
→→ without ←← (aka. IF without ENDIF). First observed on line [1], PC=1.
terminate called after throwing an instance of 'Error'
Abort
BTW, I find the diagnostic helpful (albeit twice). My only concern is the
Abort.
Thanks.
