That's a reasonable idea. We could add a subargument to the ASSERT that
detects the error, to qualify it. You would have to add each subcode to
the Wiki documentation.
There are 1847 ASSERTs in the JE, plus ~100 errors detected without ASSERT.
On the other hand, you could argue that the spacing of the error message
shows exactly where the error is, namely domain error on an assignment;
and the only domain error that applies to assignment is publicly
assigning a private name; and the current Wiki page explains that.
I wonder: could the JE format the error message in such a way that
clicking on the 'domain error' in Jqt would bring up the error-messages
page? That would help a lot, I bet.
Henry Rich
On 6/15/2020 10:38 PM, bill lam wrote:
IMO localization error still gives little hint to un-initiated users.Better
it keeps the domain error and can provide a secondary explanation message,
eg Public assignment to a name that has been privately assigned is an error
without the need of consulting the manual. The interpreter should know
exactly the detailed reason for failure.
On Tue, Jun 16, 2020 at 12:23 AM Arthur Anger <[email protected]> wrote:
I recently spent some time puzzling over a syntax error in an "obviously"
correct phrase. It took some time to recognize that the error lay in
attempting Global assignment to a Local variable.
It's not only for newcomers that it would be helpful to have that
discrepancy reported specifically as a Localization error. I suppose that
there may also be some conditions meriting a Locale error, dealing with
mis-specification or mis-application of locale, a mostly invisible aspect
of execution.
--AA
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
