I don't see why name_. is preferable to lexical closures. It seems more
difficult to use and complicated to describe; not significantly easier to
implement; and it doesn't nest.
Leaving aside performance (which can be resolved), I don't like the semantics
of name_.. . Its sole virtue is
u n: is to be => ([x] u y)
this happens to be the same output as the verb u.
u n: A is to be=> ([x] u y) A
Difference between left and right is that left is a contained function that (u
n:) can be considered a conjunction where x and y are m and n parameters.
Except that an actual
Read- and write-locks as you describe are what we use for public
locales. Each lock requires a RFO cycle, plus more if the lock is
contended.
Private namespaces require no lock, since nothing can ever contend. We
would have to add something to those paths.
Those paths are carefully timed
Giving an answer in spite of not having been addressed
because I just criticized the reasoning that I thought
was based on that word’s meaning (dispute resolved privately):
Two vectors are orthogonal if the projection of one onto the other is 0.
In colloquial terms, it means “there is no part of
Dear Mr. Stone:
I am increasingly seeing the word "orthogonal" used in various computer forums.
Looking up the word in various online dictionaries does not help, as there are
usually several definitions. What do you mean here by "orthogonal"? Thank you.
-Original Message-
From:
Note that, conceptually, at least, your proposed name_.. might not
need full locking of all name lookups.
Such locking is technically only needed when an execution containing
the specific name has been parsed.
So, conceptually speaking, most name lookups would only need a "read
lock" (which can
there is something like,
f=. {{
a=. 5
b=. 6
g=. (a;b) {{ ... [ 'a b' =. m }}
g=. a {{ ... m ... }} NB. if fewer parameters transferred.
a=. 7
}}
On Tuesday, January 17, 2023 at 10:58:05 p.m. EST, Elijah Stone
wrote:
Basically, yes. It's interesting that you refer to them
I just noticed that gethttp from the web/gethttp library supports https on both
Linux and Windows but not on Android. On Android it returns:
only http:// supported
Is there any way to fix this or a good workaround people use?
--
Omar
You are addressing a need, I admit, but one that is fairly rare, and the
proposed change is drastic IMO. The need is for something like lexical
scope, when function g can refer to a local name in function f.
Rather than remembering the environment, suppose we added some syntax if
g to
Distinguishing between "semi tacit" and explicit modifiers is done by whether
the ( : string) or {{}} modifier "mentions" x and y. If it does, it cannot
return a non-noun. It is a "glorified verb" with extra parameters. If it
doesn't it has all the power of tacit modifiers.
There is no
On Wed, Jan 18, 2023 at 6:53 AM Hauke Rehr wrote:
> Nice troll ;)
Wasn't a troll.
At the very least, errors are considered a feature aimed at helping
coders find their mistakes. Otherwise, for example, indexing with what
we currently consider invalid values could return fill rather than
Nice troll ;)
Generally speaking, in life contexts, “dark” is orthogonal to “useful”.
Which might be related to why Dark Matter is looked up on,
by some in the Physics community — it seems that it Matters too much.
But if the problem is that brightness is insufficiently constrained,
why should
Generally speaking, in computing contexts, "powerful" is orthogonal to "useful".
Which might be related to why explicit definitions are looked down on,
by some in the J community -- It seems that they're "too powerful".
But if the problem is that explicit definitions are insufficiently
13 matches
Mail list logo
