It's the odd name and the fact that a domain error doesn't arise if you
just run the phrase.
For the sake of this reply, I've just opened up a new JQt session, and
a new script,
pasting in the defs I'd listed earlier, then loading and running as
described below.
Here's the script, with the
I don't know about the domain error. I can explain the name, though
perhaps not justify it in this case:
Only named entities can be debugged line-by-line. If you have a verb like
unnamed =: 3 : 0"0
text
)
it doesn't play well with the debugger, because the inner verb has no
name (the verb '
Based on your report (very complete, thanks) I can make a guess at the
source of the domain error.
It looks like fastincl, which was defined as
fastincl =: cmp 1 : 0
text
)
was replaced by
fastincl =: cmp fastincld4B7g0
fastincld4B7g0 =: 1 : 0
text
)
Unfortunately, the replacement was done i
Thanks, Henry. As I suspected, this is a feature which you need to know about.
I wasn’t desperately worried about the application in question, just wondering
how Louis’ solution worked!
Good luck debugging the debugger, should you decide to do so,
Cheers,
Mike
Sent from my iPad
> On 10 Ju
