Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b5901dc4efda9

Jump to content

// Workers AI · dad joke modeWhat did Nord say to its date? "You're a nice syntax.

From Wikipedia, the free encyclopedia

Nord Programming Language
ParadigmProcedural, imperative
DeveloperNorsk Data
First appeared1974; 52 years ago (1974)
Final release
Final
Typing disciplineStatic, strong
ScopeLexical
PlatformNorsk Data minicomputers
OSSintran III
LicenseProprietary

Nord Programming Language (NPL), is a procedural programming language by the Norwegian minicomputer manufacturer Norsk Data. It shipped as a standard component of the operating system Sintran III.

The language was also used to implement Sintran III: the core and file system of which are written in NPL, as was the NPL compiler, and some core applications early on, until the release of high-level programming language named PLANC. Then, the linker and other software were rewritten in PLANC.

The NPL compiler was also special in that it did not emit object code as most compilers do. Instead it emitted an intermediate representation, in the form of assembly language code, which then had to be assembled using the Norsk Data Assembler.

The registers of the CPU were available in NPL as predefined variables. Thus could be written:

X + T =: A

and the compiler would emit:

COPY SX DA
RADD ST DA

Functions could be declared with multiple entry points:

FUNC FUN1, FUN2

FUN1: T := 1
FUN2:

code here

END

FUN1 could be called to set T to 1 before falling into FUN2 or T could be set to something else and call FUN2. If T register specified which file handle to write to, then either FUN1 could be called to always output to terminal or T could be specified to handle a file in T and call FUN2 to output to that file.