Apart from some unbearable situations I, like others, have been following the 
advice,

"I suggest that as usual, you should write the expression in the 'best' way, 
and then wait for the implementation to catch up." 

even before it was given.  Generally, and particularly regarding recursion, the 
catch is (of course) that the implementation may not catch up.  Thus, when 
writing production code I have avoided recursion (for the same reasons that Dan 
does).  In addition, I almost always avoid ^:_ , or equivalent, because one can 
(a point that Raul has made several times before).

Regarding the never-ending tacit vs. explicit (hybrid) programming controversy, 
I was recently amazed while searching the forum archive (I am not subscribed to 
the Chat forum) and I saw a comment by Matthew Brand ( 
http://www.jsoftware.com/pipermail/chat/2009-December/002670.html ),

"If the rest of the world does not use J then perhaps so much the better - it 
yeilds those who do a competitive advantage."

because I had made a very similar remark verbally at a recent NYCJUG 
meeting and I also made a refinement by replacing 'J' by 'full tacit J.'  (I 
have amused myself mischievously for years by browsing many forum posts, 
particularly, after major J releases with no worries.)
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to