APL syntax: Difference between revisions

From APL Wiki
Jump to navigation Jump to search
m (Fix red link "primitive" to point to "primitive function" and "primitive operator" respectively)
m (→‎Syntactic elements: Simpler link encoding)
Line 16: Line 16:
* [[Niladic function]]s, which are evaluated immediately to become one of the above values
* [[Niladic function]]s, which are evaluated immediately to become one of the above values
* In some APLs, [[hyperator]]s continue the array-function-operator hierarchy.
* In some APLs, [[hyperator]]s continue the array-function-operator hierarchy.
Each of these values can usually be stored in a variable, either by [[assignment]] or [[function definition]]. Values of these types can also be written directly in many cases, with [[string]]s, [[numeric literal]]s, or [[array notation]], as predefined [[primitive function|primitive functions]] and [[primitive operator|operators]], or as inline [[dfn]]s. There are some anomalies which do not fit easily into this system, such as [[Outer Product]], which is written with two [[glyph]]s, and [[function-operator overloading]].
Each of these values can usually be stored in a variable, either by [[assignment]] or [[function definition]]. Values of these types can also be written directly in many cases, with [[string]]s, [[numeric literal]]s, or [[array notation]], as predefined [[primitive function]]s and [[primitive operator|operators]], or as inline [[dfn]]s. There are some anomalies which do not fit easily into this system, such as [[Outer Product]], which is written with two [[glyph]]s, and [[function-operator overloading]].


Additionally, there are some syntactic elements that cannot be used as values:
Additionally, there are some syntactic elements that cannot be used as values:

Revision as of 14:22, 29 May 2020

APL's syntax refers to the way programs are written—the arrangement of functions and arrays, along with other values, keywords, and punctuation—in contrast to its semantics, that is, the meaning of the actual operations performed. In part because of APL's close relationship with mathematical notation, its syntax can be very different from typical programming languages. Distinctive features of APL include its use of infix functions, evaluated right to left with no relative precedence ordering, and its division of arrays, functions, and operators into different syntactic as well as semantic classes.

Overview

APL's core syntactic principles are:

  • Arrays as first class citizens
  • Functions act on arrays and have long right scope ("right to left")
  • Operators act on functions or arrays and have long left scope ("left to right")

A typical APL statement consists of an arrangement of the three types above, parentheses for grouping, and possibly assignment. While such individual statements may be enough for simple programming in a session, larger programs are constructed by defining functions, with control structures used to organize APL statements.

Syntactic elements

In most APLs, values in the language can have one of the following classes:

Each of these values can usually be stored in a variable, either by assignment or function definition. Values of these types can also be written directly in many cases, with strings, numeric literals, or array notation, as predefined primitive functions and operators, or as inline dfns. There are some anomalies which do not fit easily into this system, such as Outer Product, which is written with two glyphs, and function-operator overloading.

Additionally, there are some syntactic elements that cannot be used as values:

The second group, consisting of fixed syntax written with particular tokens, is common to many programming languages (in fact, APL tends to have a simpler fixed syntax than many contemporary languages). However, the first group is unusual because it means that a variable's syntactic properties are determined by the variable's value and not just by how it's written. This property makes it impossible to parse an APL statement with variables in general: for example, the statement a b c could be a function application, two function applications, a function modified by an operator, and so on.

Example array definitions

      simplenumvec←1 2 3 4 ⍝ A simple numeric vector
      simplecharvec←'ABCD' ⍝ A simple character vector

Example function definition

    ∇  r←l Tradfn r              
[1]    ⍝ An infix (dyadic) tradfn
[2]    r←l r                     
    ∇

Example operator definition

     ∇ r←larg(Main OVER PreProc)rarg                                                 
[1]    r←(PreProc larg)Main(PreProc rarg)                                            
     ∇

Example function application

      ÷3         ⍝ Prefix primitive function
0.3333333333
      1+2        ⍝ Infix primitive function
3
      +/1 2 3 4  ⍝ Prefix primitive derived function
10
      2+/1 2 3 4 ⍝ Infix primitive derived function
3 5 7

Scoping rules

Functions

Operators

External links


APL syntax [edit]
General Comparison with traditional mathematicsPrecedenceTacit programming (Train, Hook, Split composition)
Array Numeric literalStringStrand notationObject literalArray notation (design considerations)
Function ArgumentFunction valenceDerived functionDerived operatorNiladic functionMonadic functionDyadic functionAmbivalent functionDefined function (traditional)DfnFunction train
Operator OperandOperator valenceTradopDopDerived operator
Assignment MultipleIndexedSelectiveModified
Other Function axisBracket indexingBranchStatement separatorQuad nameSystem commandUser commandKeywordDot notationFunction-operator overloadingControl structureComment