Not knowing much about the "benefits" of immutable arrays, it would not surprise me in the least if it turns out they they are a hack meant to fix another hack, like OO.
On Oct 1, 2016 1:15 PM, "Erling Hellenäs" <[email protected]> wrote: > I think non-mutable data is part of the solution to the locking problems > in object-oriented languages. It seems there must be a limit after which > even J has to use more than one thread? Is there a plan for how to handle > that? Or are we using several threads already? /Erling > > On 2016-10-01 21:56, Erling Hellenäs wrote: > >> On 2016-10-01 15:40, 'Pascal Jasmin' via Programming wrote: >> >>> Forcing immutable only arrays is not an option for this language if it >>> is to remain compatible with itself >>> >> >> Someone wants to give a more specific explanation to this? What in the >> language prevents immutable only arrays? >> >> /Erling >> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
