On Fri, Jan 6, 2012 at 11:36 AM, Blake McBride <bl...@mcbride.name> wrote: > Yes, I am picking that up. > > One important take-away to this is that in J, when doing indexed > assignments, one should put that code on its own, separate line of > code. One shouldn't create a "one-liner" by combining it with other > code. Using indexed assignments in the middle of a "one-liner" causes > a copy. > > Does that statement sound right?
I would phrase your last sentence differently: "Using breaking up an index assignment with a "one-liner" causes a copy". Consider this case as an example of an indexed assignment in the middle of a one-liner: B=: C=: 0 A=: 2 32 64 32 (A=: B C} A) | _1 _1 31 63 31 That said, note that quite often, when building an application, there are alternatives which will be significantly faster than indexed assignment. But others have already treated this issue. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm