Array notation design considerations: Difference between revisions

Jump to navigation Jump to search
→‎History: removing irrelevance.
(→‎History: pre-history)
(→‎History: removing irrelevance.)
Line 31: Line 31:
=== 1996 ===
=== 1996 ===


[[John Scholes]] sent an early draft of ''Dynamic Functions in Dyalog APL'' <ref>[[John Scholes|Scholes, John M.]] https://www.dyalog.com/uploads/documents/Papers/dfns.pdf Dynamic Functions in Dyalog APL]</ref> to [[Phil Last]]. Among the plethora of new ideas that this sparked, one had consequences entirely out of scope. The ability to write a multi-line function embedded in another with line-ends between paired braces hinted at the possibility to do a similar thing between brackets and parentheses to solve a problem for which Last had been seeking a solution for a decade.  
The publication of [[John Scholes' ''Dynamic Functions in Dyalog APL'' <ref>[[John Scholes|Scholes, John M.]] https://www.dyalog.com/uploads/documents/Papers/dfns.pdf Dynamic Functions in Dyalog APL]</ref> showed that a number of expressions could be grouped together within paired delimiters and separated by line-ends. This hinted at the possibility of doing a similar thing between brackets and parentheses to solve a problem for which Phil Last had been seeking a solution for a decade.  


=== 2010 ===
=== 2010 ===
Line 39: Line 39:
=== 2013 ===
=== 2013 ===


Having attempted to engage Dyalog in the idea of an array notation over several years Phil Last sent a proposal to John Scholes outlining two possible executable notations for creating multi-dimensional arrays without function application. One using potential new system construct :Array and :Cell to be used in tradfns and another using line-ends between balanced brackets to define arrays of rank-2 or greater in both dfns and tradfns.
Phil Last sent a proposal to Dyalog outlining two possible executable notations for creating multi-dimensional arrays without function application. One using potential new system construct :Array and :Cell to be used in tradfns and another using line-ends between balanced brackets to define arrays of rank-2 or greater in both dfns and tradfns.


Scholes replied with
It became RFE 9458: Large and higher rank literal values.  See [[File:Embedding data.pdf]]
:''... I agree that APL could really do with a primitive mechanism for specifying higher rank literal values''


It became RFE 9458: Proposal for a mechanism to specify large and higher rank literal values directly in code.  
Description: Proposal for a mechanism to specify large and higher rank literal values directly in code.  


After which in the following year ...
After which in the following year ...
19

edits

Navigation menu