2,951
edits
Talk:Array notation design considerations: Difference between revisions
Jump to navigation
Jump to search
Talk:Array notation design considerations (view source)
Revision as of 23:06, 19 August 2022
, 23:06, 19 August 2022no edit summary
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
If the history of a notation is of relevance and interest then it's a history of ideas that grow and change. Insights that go toward formulating those ideas are therefore relevant. --[[User:Phil Last|Phil Last]] ([[User talk:Phil Last|talk]]) 22:55, 19 August 2022 (UTC) | If the history of a notation is of relevance and interest then it's a history of ideas that grow and change. Insights that go toward formulating those ideas are therefore relevant. --[[User:Phil Last|Phil Last]] ([[User talk:Phil Last|talk]]) 22:55, 19 August 2022 (UTC) | ||
:Aside, I've noted my objections to publishing as a pdf here [[File_talk:Embedding_data.pdf|on the relevant page]]. Yes, my criticism applies to other parts of the page. I don't think it achieves APL Wiki's goal of an encyclopedic presentation, that is, informative and digestible for the average APL programmer. I moved it because deleting is a drastic measure. | |||
:Relevance is relative; see [[wikipedia:Wikipedia:Neutral_point_of_view#Due_and_undue_weight|undue weight]]. Compare to [[Control_structure#History|control structures]] which has much less detail for a much more written-about topic. The sources are there as citations if the reader wants to dig into them. | |||
:The description of APL#'s notation as consisting of "name-value pairs" with "major and minor separators being line-end and assignment arrow" is wrong: that's not the syntax it uses. --[[User:Marshall|Marshall]] ([[User talk:Marshall|talk]]) 23:06, 19 August 2022 (UTC) | |||