Raul Miller wrote:
> https://github.com/jsoftware/jsource/commits/master might interest you...
Indeed, I have the repo cloned locally!
However, when digging through old bug reports, I find it quite challenging to
match up the "fixed" notices with the corresponding code commits. In cases with
a c
https://github.com/jsoftware/jsource/commits/master might interest you...
Thanks,
--
Raul
On Mon, Feb 1, 2021 at 6:08 PM ethiejiesa via Programming
wrote:
>
> Such a quick turnaround on bug reports, as always, Henry!
>
> I'm invariably interested in the code fixes themselves. Would it be a has
I’ve been impressed, too. This sort of bug really demands in-depth
knowledge far from what mortal J-land citizens like me have I guess.
There’s always a difference between finding some manifestation of,
and pinning down the actual source of a bug. That’s why there’s so
much patchwork code out there
Such a quick turnaround on bug reports, as always, Henry!
I'm invariably interested in the code fixes themselves. Would it be a hassle to
include some tidbit about how you solved the issue? Even just including the
`git log -p -` output (where the fix is spread over n commits) might be nice
for
This is funny... The bug afflicted for_xyz. loops over boxed iterands
where the loop exited because of an error. The (load) verb has such a
loop, so if you just typed
load 'misspelledname'
J would crash.
I guess that Mike and Bob did something like that & got a crash; then,
good citizens th
