Current issue

Vol.26 No.4

Vol.26 No.4


© 1984-2024
British APL Association
All rights reserved.

Archive articles posted online on request: ask the archivist.


Volume 23, No.3

In Session

Under the Table

Stephen Taylor

APL is famously good at describing things using tables, and tables are an obvious way to represent the contents of a spreadsheet or the results of an SQL query. But tables don’t have to grow very wide before we face a writing problem. We commonly want to select rows based on expressions that refer to columns. How to refer to columns clearly?

‘Cannon’s Canon’[1] – no numeric constants in the code – steers us away from referring to them by number like this:

tbl←0,⍨'Orders'DB.FindM('Item' 'Price' 'Quantity')('')
tbl[;4]←×/tbl[;2 3]
html,←'TABLE'tag'{TR'tag'TD'∘tag∘⍕¨⍵}/tbl[;1 4]

(DB.FindM queries a database table Orders and tag marks up character vectors with HTML tags). We can improve on this a little with local names for column indexes:

tbl[;AMNT]←×/tbl[;PRIC QUANT]
html,←'TABLE'tag'{TR'tag'TD'∘tag∘⍕¨⍵}/tbl[;ITEM AMNT]

We can write something closer to the simplicity of our first textbook by representing the table as a namespace in which named vectors represent the columns:

tbl←'Item Price Quantity'DB.Tbl'Orders'
html,←'TABLE'tag'{TR'tag'TD'∘tag∘⍕¨⍵}/⍉↑tbl.(Item Amount)

Dot notation gives us even better opportunities when we come to tables with matching column names. Consider a table CON of contact information from a spreadsheet. We’ll use some of the records to update contacts already in our database. The others we’ll add as new contacts. So the first question is: which records in CON represent existing contacts? Our first step is to match email addresses, record the corresponding ContactID and write a bitmask to show which records were not matched.

C←'ContactID Email CompanyID Name'#.DB.Tbl'Contacts'
no←0=CON.ContactID←(C.ContactID,0)[⊃⍳/(C CON).Email]


  • use of ⍳/ with dot notation to look up a column from one table in its homonym in the other;
  • the clarity of setting and testing for the ‘null’ value 0 in the same line.

But people use multiple email addresses, so we’ll test the unmatched records to see if we can recognise any others. Here we’ll look for matches on both CompanyID and Name.

(no/CON.ContactID)←(C.ContactID,0)[⊃⍳/1 no/¨↓∘⍉∘↑¨(C CON).(CompanyID Name)]


  • use of dot notation to specify the CompanyID and Name columns from both tables;
  • use of ↓∘⍉∘↑¨ (zip each) to convert each pair of vectors into a vector of pairs;
  • use of 1 no/¨ to mask only the CON pairs;
  • use of (no/CON.ContactID)← to insert just the matched contact IDs, if any.

This is clearly not beginner’s writing, but the single line is easier to analyse and maintain than the same operations dispersed across several lines and temporary variables.


  1. “Three Principles of Coding Clarity” Taylor, S. Vector 18(4) pp113-124

Valid HTML 4.01 Strict

script began 10:17:01
caching off
debug mode off
cache time 3600 sec
indmtime not found in cache
cached index is fresh
recompiling index.xml
index compiled in 0.1769 secs
read index
read issues/index.xml
identified 26 volumes, 101 issues
array (
  'id' => '10011860',
regenerated static HTML
article source is 'HTML'
source file encoding is 'UTF-8'
URL: =>
URL: #ref1 => art10011860#ref1
URL: =>
URL: =>
URL: =>
completed in 0.2024 secs