Further to the answers already posted, my way of thinking
tacitly is to try to feed the incoming arguments into their
functions without having to do so explicitly.
This can't always be done, so you use the "functions/verbs"
[ and ] to specify when you can't imply. Also, there's [: to
block arguments when this is needed, though I try to avoid
this on aesthetic grounds, but it does often save parentheses.
You can also imply the use of operands when defining
operators (adverbs and conjunctions) tacitly, but this gets
very awkward. Tragically, you can't use [. and ]. to specify
operand use the way [ and ] specify argument use. Thus
a conjunction like [.&{. ]. [.&{: cannot be clearly defined.
Still, tacit coding is a joy when you get the hang of it.
I haven't had to code explicitly since I started coding tacitly,
even when I needed to simulate von Neuman's IAS machine
for my students to use.
> Date: Fri, 14 Sep 2007 08:14:49 -0700 (PDT)
> From: Ed Keith <[EMAIL PROTECTED]>
>
> I'm coming to J from a C++ background. While much of J
> requires a new mind set, I think I am getting most of
> it, but I'm just not getting tacit programming. I
> cannot figure out anything that is not trivial.
>
> . . .
>
> How would this be written tacitly? I'm not so much
> interested in how to write this verb, but how to think
> through the creation of a tacit verb.
Neville Holmes, P.O.Box 404, Mowbray 7248, Tasmania
Normal e-mail: [EMAIL PROTECTED]
____________________________________________________________________________________
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
