Looks good, but one very small problem - when it reports the line number
with the error, it is off by one. In other words, line references in the
editor (and in APL) start at 0, but when it reports the error it reports
the line number as if they start at 1.
Thanks.
Blake
On Sat, Oct 4, 2014 at
Thanks, Blake. This is best fixed in libemacs.
Elias: The attached patch makes a failed function definition report an
origin-independent line number.
On Sun, 2014-10-05 at 07:29 -0500, Blake McBride wrote:
> Looks good, but one very small problem - when it reports the line
> number with the error
Thanks. I'll integrate it once I get home. Although you missed a +1 there.
The error is reported as a line number, not an APL jump index, which is
conceptually different thing.
Regards,
Elias
On 6 Oct 2014 01:05, "David B. Lamkins" wrote:
> Thanks, Blake. This is best fixed in libemacs.
>
> Elia
Conceptually different but significantly confusing if they are not
displayed as the same number.
On Sun, Oct 5, 2014 at 10:18 PM, Elias Mårtenson wrote:
> Thanks. I'll integrate it once I get home. Although you missed a +1 there.
> The error is reported as a line number, not an APL jump index, w
That's a display issue. ☺ I'm sure aplwrap can provide an option to display
it in that way for people who prefer that (most people probably don't care
since one never actually interacts with jump indexes very often directly)
What David's patch does is to harmonise the underlying wire protocol. It
