Most people these days seem to like having lots of contributed packages
to choose from, and don't expect everything to be done in a primitive.
Also, there might not be a clean mapping of the needs of dictionaries
onto the existing J primitives.
I think your reluctance to use packages is misplaced: for example, bugs
in calculus can be fixed in the addon, whereas the primitives were never
going to be updated.
Henry Rich
On 4/15/2021 3:55 PM, David Lambert wrote:
Primitive or addon? The readily available, well documented primitives are
easy to use. For instance, I have avoided the calculus addon while I would
have used those primitives since removal. The tagged bag example from the
object oriented programming lab is a hash. Were the hash data type
builtin, such verbs as `from' and `key amend' would fit naturally.
|Date: Wed, 14 Apr 2021 10:24:50 -0400
|From: Henry Rich <[email protected]>
|To: [email protected]
|Subject: [Jprogramming] Hashing primitives WAS: Farewell for now!
|Message-ID: <[email protected]>
|Content-Type: text/plain; charset=utf-8; format=flowed
|
|If we could come up with a good spec for hashing primitives, we could
|implement it. JE does lots of hashing, notably in the i.-family, but
|the table is not exposed to the user. When I have thought about hashing
|primitives, I have ended up deciding it could be done in an addon just
|as well as in a primitive.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
