I was wondering if anybody noticed the new error messages. I'm happy
that you did.
I number global variables among the works of the Devil. They make it
impossible to tell exactly what a function is doing: when it modifies a
global, who knows what that might engender?
When I use them, I sup with a long spoon: copious commentary, and with
the rule that only one function may modify them.
You can see that with this bias I think that having to write an explicit
global assignment is much preferable to any construct that would
proliferate globals unwittingly.
Henry Rich
On 12/18/2022 7:13 PM, David Lambert wrote:
Global iteration variables would save me a bit of time debugging.
Work-around
for_local. array do.
global=: local NB. this I write with great hindsight.
end.
And thank you muchly for the enhanced error messages. Dave
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
