The special code issue is real. The primitives addon achieves it by search and replace automation.
Conjugate =: + Conjugate Insert i.5 NB.unlikely to be meaningful 10 conjugate/ i.5 NB. what was actually written. +@]/ 4 seeing this result would reinforce that u in u/ is dyadic more quickly perhaps. Two basic ways of dealing with the special code issues: 1. Just use symbols for triggering SC 2. Shaddow adverb names for special code fl =: <.@ 10 timespacex '3 % fl~ i.10000' 9.1744e_5 264576 10 timespacex '3 <.@%~ i.10000' 9.2672e_5 264320 10 timespacex '3 floor@%~ i.10000' NB. :( 0.00449571 265344 ofraveled =: 1 : 'u ,' 20 timespacex '(i.20) { ofraveled i. 100 100 3' 6.0256e_5 528128 20 timespacex '(i.20) ({ ,) i. 100 100 3' 5.9056e_5 527104 timespacex '(i.20) { , i. 100 100 3' 0.00044384 788864 ----- Original Message ----- From: bill lam <bbill....@gmail.com> To: Programming forum <programm...@jsoftware.com> Sent: Thursday, November 26, 2015 6:55 PM Subject: Re: [Jprogramming] dyadic J I would like to point out there is negligible or no speed penalty when using names in the primitives addon. All names are translated into symbols during loading scripts, see documentation inside that addon. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm