On Fri, Jul 27, 2012 at 6:20 PM, Dan Bron wrote:
> Raul wrote:
>> Anyways, the definition which is relevant when cap is the left tine of
>> a fork is a passive definition, and not an imperative definition. And
>> making this distinction -- that it's being used passively -- seems
>> worthwhile
aterdag 28 juli 2012 2:19
> Aan: programm...@jsoftware.com
> Onderwerp: Re: [Jprogramming] cap
>
> Raul wrote:
> > Anyways, the definition which is relevant when cap is the left tine of
> > a fork is a passive definition, and not an imperative definition. And
> &
Raul wrote:
> Anyways, the definition which is relevant when cap is the left tine of
> a fork is a passive definition, and not an imperative definition. And
> making this distinction -- that it's being used passively -- seems
> worthwhile.
I responded:
> There are several issues with this i
Raul wrote:
> Anyways, the definition which is relevant when cap is the left tine of
> a fork is a passive definition, and not an imperative definition. And
> making this distinction -- that it's being used passively -- seems
> worthwhile.
There are several issues with this interpretation.
I like to think of Cap [: as a left identity element for the tree
representation of a fork.
f g h is
g
f h
and [: g h is
g
h
Sent from my iPad
On Jul 27, 2012, at 8:10 AM, Raul Miller wrote:
> On Thu, Jul 26, 2012 at 7:43 PM, Dan Bron wrote:
>> In a draft, I had originally written
On Thu, Jul 26, 2012 at 7:43 PM, Dan Bron wrote:
> In a draft, I had originally written "Meaning its definition is irrelevant".
> I think that sums it up.
Change "definition" to "imperative definition" and that seems reasonable.
Mostly we think of using J verbs using their imperative tense.
Geru
I wrote:
> Note the left tine of the capped fork was called literally zero times.
> Meaning its definition is not used.
Raul responded:
> I would phrase this as "Meaning the implementation is not used".
> Or, even better "Meaning the implementation is not executed".
In a draft, I had origin
On Thu, Jul 26, 2012 at 5:58 PM, Dan Bron wrote:
> Note the left tine of the capped fork was called literally zero times.
> Meaning its definition is not used.
I would phrase this as "Meaning the implementation is not used". Or,
even better "Meaning the implementation is not executed".
The word
Raul wrote:
> Grammatical exceptions are common in J (all special code)
Actually, _grammatical_ exceptions are extremely rare in J. That's one of
J's defining features. And one of the reasons we love it.
[Not that we don't love Perl, too - where not having a grammatical exception
would be an ex
I wrote:
> That said, the interpreter does take special steps to allow for
> cap to have aliases, as in cap=:[:
Raul responded
> Yes.
Actually, I did find one use for this special-casing. We can combine it
with J's built-in performance monitoring tools, to compare how many times
the left tine o
On Thu, Jul 26, 2012 at 4:48 PM, Dan Bron wrote:
> To understand why, we must recall that capped fork is a grammatical
> _exception_.
Yes.
Grammatical exceptions are common in J (all special code) and in
natural language (where the idioms vary much more wildly than J's
special code -- ideally, t
[Sorry for the delays in my replies - I didn't have as much time to get
engaged in this topic as I expected.]
Raul wrote:
> I disagree that [: capping a fork is unrelated to its definition.
I simply can't see it any other way.
Capped fork is a grammatical rule, and the parser recognizes it by
On Tue, Jul 24, 2012 at 4:52 PM, Dan Bron wrote:
> Raul wrote:
>> Personally, I not only cannot see any valid interpretations where its
>> domain is not empty.
>
> This is the crux. The use of [: to cap a fork is _unrelated to its
> definition_ (including domain, codomain, interpretation, rank,
mments as preferences/opinion. )
-Dan
-Original Message-
From: programming-boun...@forums.jsoftware.com
[mailto:programming-boun...@forums.jsoftware.com] On Behalf Of Raul Miller
Sent: Tuesday, July 24, 2012 4:17 PM
To: programm...@jsoftware.com
Subject: Re: [Jprogramming] cap
On Tue, Jul 24, 2012
On Tue, Jul 24, 2012 at 3:59 PM, Dan Bron wrote:
> Raul wrote:
>> This kind of reasoning -- that a language primitive should
>> not be treated as having utility explicitly stated in the
>> documentation of that primitive, and obviously present in
>> the implementations -- does not make sense t
l Message-
From: Dan Bron [mailto:j...@bron.us]
Sent: Tuesday, July 24, 2012 3:59 PM
To: 'programm...@jsoftware.com'
Subject: RE: [Jprogramming] cap
Raul wrote:
> This kind of reasoning -- that a language primitive should
> not be treated as having utility explicitly stated in
de, and my
primary user is myself. So my views might be parochial.
-Original Message-
From: programming-boun...@forums.jsoftware.com
[mailto:programming-boun...@forums.jsoftware.com] On Behalf Of Tracy Harms
Sent: Tuesday, July 24, 2012 11:05 AM
To: programm...@jsoftware.co
Hi, Dan,
What do you do when you write a tacit verb and you wish to assure that it
isn't accidentally invoked dyadically?
--Tracy
--
For information about J forums see http://www.jsoftware.com/forums.htm
On Mon, Jul 23, 2012 at 4:57 PM, Dan Bron wrote:
> Raul wrote:
>> It's defined as having an empty domain --
>> why not rely on the definition being
>> accurate?
>
> Cap's raison d'etre is grammatical, not semantic. That it is a verb, and
> that its domain is defined to be empty, is incidental
-Dan
-Original Message-
From: programming-boun...@forums.jsoftware.com
[mailto:programming-boun...@forums.jsoftware.com] On Behalf Of Raul Miller
Sent: Monday, July 23, 2012 4:44 PM
To: programm...@jsoftware.com
Subject: Re: [Jprogramming] cap
On Mon, Jul 23, 2012 at 2:01 PM, Dan Bron wrote:
> I
On Mon, Jul 23, 2012 at 2:01 PM, Dan Bron wrote:
> I constrain my use of cap to the left tine of forks. I do not apply it as a
> verb, because I don't like to rely on its domain(s) being empty.
It's defined as having an empty domain -- why not rely on the
definition being accurate?
> Finally, a
jsoftware.com
[mailto:programming-boun...@forums.jsoftware.com] On Behalf Of David Ward
Lambert
Sent: Monday, July 23, 2012 10:05 AM
To: programming
Subject: [Jprogramming] cap
Another fine application of cap:
Suppose we have an agenda selection function which returns 0 1 3 . Cap
in this tie error
Another fine application of cap:
Suppose we have an agenda selection function which returns 0 1 3 . Cap
in this tie error checks select .
f`g`[:`h @. select Y
I regret not being able to attend the conference this year---I would
like to meet you.
Dave.
--
23 matches
Mail list logo
