Try removing ':' from paths manually

.gitignore

@@ -1,9 +1,3 @@
-/*.ys
 /Cache/
 /Meta/
 /rosettacode.log
-/entry
-/pick
-/random-clojure-task
-/.clj-kondo/
-/.lsp/

Conf/lang.yaml

@@ -4,7 +4,6 @@
 360 Assembly: '.360'
 4D: .4d
 4DOS Batch: .4dos
-4ME: .4me
 6502 Assembly: '.6502'
 68000 Assembly: '.68000'
 6800 Assembly: '.6800'
@@ -23,19 +22,17 @@ Acornsoft Lisp: .lisp
 Action!: .action
 ActionScript: .as
 Acurity Architect: .acurity
-Ada: .adb
+Ada: .ada
-Adina: .adina
-Agda2: .agda2
 Agda: .agda
+Agda2: .agda2
 Agena: .agena
 AHDL: .ahdl
-AIDED NATURAL LANGUAGE: .aided
 Aikido: .aikido
 Aime: .aime
 Algae: .algae
+ALGOL: .alg
 ALGOL 60: .alg
 ALGOL 68: .alg
-ALGOL: .alg
 ALGOL-M: .alg
 ALGOL W: .alg
 Alice ML: .alice
@@ -53,7 +50,6 @@ Anyways: .anyways
 Apex: .apex
 APL: .apl
 App Inventor: .app
-Apple: .apple
 AppleScript: .applescript
 Applesoft BASIC: .basic
 Application Master: .app
@@ -63,8 +59,6 @@ Arbre: .arbre
 Arc: .arc
 Arendelle: .arendelle
 Argile: .argile
-Aria: .aria
-ArkScript: .ark
 ARM Assembly: .arm
 ArnoldC: .arnoldc
 Arturo: .arturo
@@ -74,7 +68,7 @@ ASP: .asp
 AspectC++: .acpp
 AspectJ: .aspectj
 ASP.Net: .asp
-Assembly: .asm
+Assembly: .as
 AssemblyScript: .asmscript
 Astro: .astro
 Asymptote: .asymptote
@@ -83,14 +77,15 @@ ATS: .ats
 AutoHotkey: .ahk
 Autohotkey V2: .ahk
 AutoHotKey V2: .ahk
-AutoIt: .au3
+AutoIt: .autoit
-AutoLISP: .lsp
+AutoLISP: .l
 Avail: .avail
 AWK: .awk
 Axe: .axe
 Axiom: .axiom
 Axum: .axum
 Ayrch: .ayrch
+B: .b
 B4J: .b4j
 B4X: .b4x
 Babel: .pb
@@ -99,13 +94,12 @@ BaCon: .bacon
 Bait: .bait
 Ballerina: .ballerina
 Bas: .bas
+BASIC: .basic
 Basic09: .basic
 BASIC256: .basic
-BASIC: .basic
 Batari Basic: .basic
 Batch File: .bat
 Battlestar: .battlestar
-B: .b
 BBC BASIC: .basic
 Bc: .bc
 BCPL: .bcpl
@@ -113,7 +107,6 @@ Beads: .beads
 Beef: .beef
 Beeswax: .beeswax
 Befunge: .bf
-Berkeley Logo: .logo
 Beta: .beta
 Biferno: .biferno
 Binary Lambda Calculus: .blc
@@ -137,26 +130,23 @@ Brat: .brat
 Brlcad: .brlcad
 Bruijn: .bruijn
 Burlesque: .blq
+C++: .cpp
+C: .c
 C0H: .c0h
 C1R: .c1r
 C2: .c2
 C3: .c3
 CafeOBJ: .cafeobj
-Calc: .calc
-Calcscript: .calc
 Caml: .caml
 Casio BASIC: .basic
 Cat: .cat
 CB80: .cb80
-CBASIC: .basic
-C: .c
 C++/CLI: .cpp
-C++: .cpp
 Cduce: .cduce
 Cecil: .cecil
 Ceylon: .ceylon
 CFEngine: .cfengine
-Chapel: .chpl
+Chapel: .chapel
 Chef: .chef
 Cherrycake: .cherrycake
 Chipmunk Basic: .basic
@@ -165,7 +155,6 @@ ChucK: .chuck
 Cilk++: .cilk++
 Cilk: .cilk
 Cind: .cind
-CJam: .cjam
 Clarion: .clarion
 Clay: .clay
 Clean: .clean
@@ -176,7 +165,7 @@ CLIPS: .clips
 Clojure: .clj
 CLU: .clu
 CMake: .cmake
-COBOL: .cob
+COBOL: .cobol
 Cobra: .cobra
 Coco: .coco
 Coconut: .coconut
@@ -189,19 +178,19 @@ Common Lisp: .lisp
 Component Pascal: .pas
 Computer/zero Assembly: .0asm
 ContextFree: .cf
-Convex: .convex
 Coq: .coq
 Corescript: .core
 Cowgol: .cowgol
 Crack: .crack
 Craft Basic: .basic
 Creative Basic: .basic
-Crystal: .cr
+Curto: .curto
+Crystal: .crystal
 C sharp: .cs
 C Shell: .csh
 Cubescript: .cube
 Curry: .curry
-Curto: .curto
+D: .d
 Dafny: .dafny
 Dao: .dao
 Dart: .dart
@@ -210,9 +199,8 @@ DataWeave: .dw
 DBL: .dbl
 Dc: .dc
 DCL: .dcl
-D: .d
 DDNC: .ddnc
-Delphi: .pas
+Delphi: .delphi
 Deluge: .deluge
 DeviousYarn: .dy
 DIBOL-11: .dibol-11
@@ -224,23 +212,20 @@ DMS: .dms
 Dodo0: .dodo0
 Draco: .draco
 Dragon: .dragon
-Dragonstone: .dragonstone
 DreamBerd: .dreamberd
 Dt: .dt
-DuckDB: .duckdb
 DUP: .dup
 DWScript: .dw
 Dyalect: .dyalect
 Dylan: .dylan
 Dylan.NET: .dylan
+E: .e
 EasyLang: .easy
 EC: .ec
 EchoLisp: .l
 ECL: .ecl
 Ecstasy: .ecstasy
-Ed: .ed
 EDSAC order code: .edsac
-E: .e
 Eero: .eero
 Efene: .efene
 Egel: .egel
@@ -253,10 +238,10 @@ Elan: .elan
 ElastiC: .elastic
 Elena: .elena
 Elisa: .elisa
-Elixir: .ex
+Elixir: .elixir
 ELLA: .ella
 Elm: .elm
-Emacs Lisp: .el
+Emacs Lisp: .l
 EMal: .emal
 Emojicode: .emojicode
 Enguage: .enguage
@@ -267,29 +252,28 @@ ERRE: .erre
 Es: .es
 ESQL: .esql
 Euler: .euler
-Euphoria: .eu
+Euphoria: .euphoria
 Evaldraw: .evaldraw
 Excel: .excel
 Explore: .explore
 Extended BrainF***: .ebf
-Extended Color BASIC: .basic
 Ezhil: .ezhil
+F: .f
 Factor: .factor
 Falcon: .falcon
 'FALSE': .false
-Fancy: .fancy
 Fan: .fan
+Fancy: .fancy
 Fantom: .fantom
 FAUST: .faust
 FBSL: .fbsl
-FeatureC++: .cpp
 Fe: .fe
+FeatureC++: .cpp
 Felix: .felix
 Fennel: .fennel
 Ferite: .ferite
 Fermat: .fermat
 Fexl: .fexl
-F: .f
 Fhidwfe: .fhidwfe
 Fish: .fish
 FLORA-2: .flora2
@@ -310,7 +294,6 @@ Frink: .frink
 FRISC Assembly: .frisc
 F Sharp: .fs
 FTCBASIC: .basic
-FuncSug: .funcsug
 FunL: .funl
 Furor: .furor
 FurryScript: .furryscript
@@ -340,10 +323,9 @@ GlovePIE: .glovepie
 GLSL: .glsl
 GML: .gml
 Gnuplot: .gnuplot
-Goaldi: .goaldi
-Goboscript: .gobo
 Go!: .go
 Go: .go
+Goaldi: .goaldi
 Golfscript: .golf
 Golo: .golo
 Goo: .goo
@@ -360,7 +342,7 @@ Halon: .halon
 Harbour: .harbour
 Hare: .hare
 Haskell: .hs
-Haxe: .hx
+Haxe: .haxe
 Heron: .heron
 Hexiscript: .hexi
 HicEst: .hicest
@@ -374,11 +356,10 @@ HQ9+: .hq9+
 Huginn: .huginn
 Hy: .hy
 HyperTalk: .ht
+I: .i
 Icon: .icon
 IDL: .idl
 Idris: .idris
-I: .i
-Imp77: .imp77
 Inform 6: '.inf'
 Inform 7: '.inf'
 Informix 4GL: .4gl
@@ -393,19 +374,18 @@ Iptscrae: .iptscrae
 Isabelle: .isabelle
 IS-BASIC: .basic
 IWBASIC: .basic
+J: .j
 Jabaco: .jabaco
 Jack: .jack
 Jacquard Loom: .jacquard
-Jactl: .jactl
 Jakt: .jakt
 JAMES II/Rule-based Cellular Automata: .james
 Janet: .janet
-JavaFX Script: .javafx
 Java: .java
+JavaFX Script: .javafx
 JavaScript: .js
 JCL: .jcl
 Jinja: .jinja
-J: .j
 JoCaml: .jocaml
 JOVIAL: .jovial
 Joy: .joy
@@ -414,34 +394,31 @@ JScript.NET: .jscript
 JSE: .jse
 Jsish: .jsish
 JudoScript: .judo
-Julia: .jl
+Julia: .julia
+K: .k
 Kabap: .kabap
 Kamailio Script: .kamailio
-Kantalo: .kantalo
 KAP: .kap
 Kaya: .kaya
 Keg: .keg
 KeyList Databasing: .keylist
 Kite: .kite
 Kitten: .kitten
-K: .k
 KL1: .kl1
 Klingphix: .klingphix
 Klong: .klong
 Koka: .koka
-Komodo: .komodo
 KonsolScript: .konsol
-Kotlin: .kts
+Kotlin: .kotlin
 KQL: .kql
 Ksh: .ksh
+L++: .l++
 LabVIEW: .labview
-Labyrinth: .labyrinth
 Lambda Prolog: .pro
 Lambdatalk: .lambdatalk
-Lang5: .lang5
 Lang: .lang
+Lang5: .lang5
 Langur: .langur
-Lapyst: .lapyst
 Lasso: .lasso
 LAST: .last
 LaTeX: .tex
@@ -467,7 +444,6 @@ Little: .little
 Little Man Computer: .lmc
 LiveCode: .livecode
 LiveScript: .live
-L++: .l++
 LLP: .llp
 LLVM: .llvm
 Lobster: .lobster
@@ -480,8 +456,8 @@ Lolli: .lolli
 Lotus 123 Macro Scripting: .lotus123
 LotusScript: .lotus
 Lout: .lout
-LSE64: .lse64
 LSE: .lse
+LSE64: .lse64
 LSL: .lsl
 LSTS: .lsts
 Lua: .lua
@@ -502,8 +478,6 @@ Malbolge: .malbolge
 MANOOL: .manool
 Maple: .maple
 MAPPER: .mapper
-MariaDB: .sql
-Mastermind: .mastermind
 Mathcad: .mathcad
 MathCortex: .mathcortex
 Mathematica: .math
@@ -523,21 +497,20 @@ Metapost: .metapost
 MGS: .mgs
 Mia: .mia
 Microsoft Small Basic: .basic
+Min: .min
 MINIL: .minil
 Minimal BASIC: .basic
 MiniScript: .mini
 MiniZinc: .minizinc
-Min: .min
 MIPS Assembly: .mips
 Mirah: .mirah
 Miranda: .miranda
 MIRC Scripting Language: .mirc
 Mirelle: .mirelle
+ML: .ml
 ML/I: .mli
 MLite: .mlite
-ML: .ml
 MMIX: .mmix
-Mn: .mn
 Modula-2: .mod2
 Modula-3: .mod3
 Mojo: .mojo
@@ -547,8 +520,6 @@ Monkey: .monkey
 Monte: .monte
 MontiLang: .monti
 MOO: .moo
-MoonBit: .moonbit
-MoonRock: .moonrock
 MoonScript: .moon
 Morfa: .morfa
 Mosaic: .mosaic
@@ -587,7 +558,6 @@ Nit: .nit
 Niue: .niue
 Nix: .nix
 NLP++: .nlp++
-Nom: .num
 NOWUT: .nowut
 NQP: .nqp
 NS-HUBASIC: .basic
@@ -596,27 +566,24 @@ N/t/roff: .ntroff
 Nu: .nu
 Nutt: .nutt
 Nyquist: .nyquist
-OASYS Assembler: .oasys
 OASYS: .oasys
-Oberon-07: .oberon
+OASYS Assembler: .oasys
 Oberon: .oberon
 Objeck: .objeck
 ObjectIcon: .oi
 Objective-C: .m
-Object Pascal Implementations: .pas
 Object Pascal: .pas
-OCaml: .ml
+OCaml: .ocaml
 Occam: .occam
 Octave: .octave
 Odin: .odin
 Oforth: .fth
 Ol: .ol
 Omega: .omega
-OmniMark: .xom
 Onyx: .onyx
 Onyx (wasm): .onyx
-OOCalc: .oocalc
 OOC: .ooc
+OOCalc: .oocalc
 OoRexx: .rexx
 Opa: .opa
 OpenC++: .openc++
@@ -635,9 +602,8 @@ Panoramic: .panoramic
 ParaCL: .paracl
 Pare: .pare
 PARI/GP: .parigp
-PascalABC.NET: .pas
 Pascal: .pas
-Pascal-P: .pas
+PascalABC.NET: .pas
 PASM: .pasm
 PDP-11 Assembly: .pdp11
 Pebble: .pebble
@@ -646,16 +612,15 @@ Pentium Assembly: .pentium
 PeopleCode: .peoplecode
 PepsiScript: .pepsi
 Peri: .peri
+Perl: .pl
 Perl5i: .p5i
 Perl 6: .pl6
-Perl: .pl
 Peylang: .peylang
-Phixmonti: .phixmonti
 Phix: .phix
+Phixmonti: .phixmonti
 PHL: .phl
 PHP: .php
 Picat: .picat
-Pico-8: .pico8
 PicoLisp: .l
 Pict: .pict
 Piet: .piet
@@ -668,13 +633,12 @@ Plain English: .plain
 PlainTeX: .tex
 Plan: .plan
 PL/B: .plb
-PL/I-80: .pli
 PL/I: .pli
+PL/I-80: .pli
 PL/M: .plm
 PL/pgSQL: .sql
 PL/SQL: .sql
 PLUS: .plus
-Pluto: .pluto
 PLZ/SYS: .plz
 Pointless: .pointless
 Polyglot: .polyglot
@@ -687,58 +651,56 @@ POV-Ray: .povray
 PowerBASIC: .basic
 Powerbuilder: .powerbuilder
 PowerPC Assembly: .ppc
-PowerShell: .ps1
+PowerShell: .psh
 PPL: .ppl
 Processing: .processing
 Processing Python mode: .processing-py
 Processing.R: .processing-r
 ProDOS: .dos
 Prog8: .prog8
-ProgressBASIC: .basic
 Prolog: .pro
 PROMAL: .promal
 PSQL: .psql
+Pure: .pure
 PureBasic: .basic
 Pure Data: .puredata
-Pure: .pure
 Purity: .purity
-Pyret: .arr
+Pyret: .pyret
 Python: .py
+Q: .q
 QB64: .qb64
 QBasic: .basic
 Qi: .qi
 .QL: .ql
 QL SuperBASIC: .basic
 Qore: .qore
-Q: .q
 Quackery: .quackery
 QuakeC: .c
 QuickBASIC: .basic
 Quill: .quill
 Quite BASIC: .basic
 Quorum: .quorum
+R: .r
+Ra: .ra
 Racket: .rkt
 Raku: .raku
 RapidQ: .rapidq
 Rapira: .rapira
-Ra: .ra
 Rascal: .rascal
 RASEL: .rasel
 RATFOR: .ratfor
 Raven: .raven
 REALbasic: .basic
-Reason: .re
+Reason: .reason
-Rebol: .rebol
 REBOL: .rebol
 Red: .red
 Reduce: .reduce
 Refal: .refal
 Relation: .relation
-ReScript: .res
+ReScript: .re
 Retro: .retro
 Revolution: .rev
 REXX: .rexx
-Rhombus: .rhombus
 Rhope: .rhope
 Rhovas: .rhovas
 Ring: .ring
@@ -746,31 +708,28 @@ RISC-V Assembly: .asm
 RLaB: .rlab
 RLSL: .rlsl
 Robotic: .robotic
-Rockstar: .rockstar
-Rocq: .rocq
 Roc: .roc
-RPGIV: .rpgiv
+Rockstar: .rockstar
 RPG: .rpg
-RPL/2: .rpl2
+RPGIV: .rpgiv
 RPL: .rpl
-R: .r
+RPL/2: .rpl2
 RTL/2: .rtl2
 RTSL: .rtsl
 Rubylog: .rubylog
 Ruby: .rb
 Run BASIC: .basic
-Rust: .rs
+Rust: .rust
-Rye: .rye
+S++: .s++
 Sage: .sage
 Salmon: .salmon
-SapbotVM: .sapbot
-SASL: .sasl
 SAS: .sas
+SASL: .sasl
 Sass/SCSS: .sass
 Sather: .sa
 S-BASIC: .basic
 Scala: .scala
-Scheme: .scm
+Scheme: .ss
 Scilab: .scilab
 Scratch: .scratch
 ScratchScript: .scratch
@@ -782,15 +741,14 @@ Seed7: .seed7
 Self: .self
 SenseTalk: .sensetalk
 SequenceL: .sequencel
+SETL: .setl
 Setl4: .setl4
 Set lang: .set
-SETL: .setl
 Shale: .shale
 SheerPower 4GL: .4gl
 Shen: .shen
 Shiny: .shiny
 Sidef: .sidef
-SIL: .sil
 SimpleCode: .simplecode
 SimpleLang: .simple
 SIMPOL: .simpol
@@ -807,8 +765,8 @@ Smalltalk: .st
 Smart BASIC: .basic
 SMEQL: .smeql
 SmileBASIC: .basic
-SNOBOL4: .sno
 Snobol: .sno
+SNOBOL4: .sno
 SNUSP: .snusp
 Soar: .soar
 Soda: .soda
@@ -816,15 +774,14 @@ SoneKing Assembly: .soneking
 SPAD: .spad
 SPARC Assembly: .sparc
 SparForte: .sparforte
-Sparkling: .sparkling
 SPARK: .spark
+Sparkling: .sparkling
 Spin: .spin
 SPL: .spl
 SPSS: .spss
-SQL PL: .sql
 SQL: .sql
+SQL PL: .sql
 Squirrel: .nut
-S++: .s++
 SSEM: .ssem
 Standard ML: .ml
 Star: .star
@@ -845,23 +802,22 @@ SystemVerilog: .v
 TailDot: .taildot
 Tailspin: .tailspin
 TAL: .tal
-TAV: .tav
 Tbas: .tbas
 Tcl: .tcl
 TechBASIC: .basic
 Teco: .teco
 TeLa: .tela
 Tern: .tern
-Terraform: .terraform
 Terra: .terra
+Terraform: .terraform
 TestML: .tml
 Thistle: .thistle
 Thyrd: .thyrd
+TI BASIC: .basic
 TI-57: .ti57
 TI-83 BASIC: .basic
 TI-83 Hex Assembly: .asm
 TI-89 BASIC: .basic
-TI BASIC: .basic
 Tiny BASIC: .basic
 Tiny Craft Basic: .basic
 TIS-100: .tis100
@@ -894,30 +850,31 @@ Uiua: .uiua
 Ultimate++: .ultimate++
 Unicon: .unicon
 Uniface: .uniface
-Unison: .u
+Unison: .unison
 UnixPipes: .up
 UNIX Shell: .sh
 Unlambda: .unlambda
-Ursalang: .ursa
-Ursala: .ursala
 Ursa: .ursa
+Ursala: .ursala
+Ursalang: .ursa
 UScript: .u
 UserRPL: .rpl
 UTFool: .utfool
 Uxntal: .uxnatl
+V: .v
 Vala: .vala
 Vale: .vale
 VAX Assembly: .vax
 VB6: .vb6
 VBA: .vba
-VBScript: .vbs
+VBScript: .vb
 Vedit macro language: .vedit
 Verbexx: .verbexx
 Verilog: .v
-VHDL: .vhd
+VHDL: .vhdl
 Vim Script: .vim
-Visual Basic .NET: .vb
 Visual Basic: .vb
+Visual Basic .NET: .vb
 Visual FoxPro: .fvp
 Visual Objects: .vobj
 Visual Prolog: .pro
@@ -926,10 +883,7 @@ Vorpal: .vorpal
 Vox: .vox
 VRML: .vrml
 VTL-2: .vtl-2
-V: .v
 V (Vlang): .v
-Vyxal: .vyxal
-Waduzitdo: .waduzitdo
 Wart: .wart
 WDTE: .wdte
 WebAssembly: .wasm
@@ -951,32 +905,31 @@ XBase: .xbase
 XBasic: .basic
 XBS: .xbs
 XEec: .xeec
-XLISP: .l
 XL: .xl
+XLISP: .l
 Xojo: .xojo
 XPath 2.0: .xpath
 XPL0: .xpl0
 XProc: .xproc
 XProfan: .xprofan
 XQuery: .xquery
-X-script: .x
+XS: .xs
+XSLT: .xslt
 XSLT 1.0: .xslt
 XSLT 2.0: .xslt
-XSLT: .xslt
-XS: .xs
 XTalk: .xtalk
 XUL: .xul
+Ya: .ya
 Yabasic: .basic
 Yacas: .yacas
 YAMLScript: .ys
-Ya: .ya
 Yorick: .yorick
 Z80 Assembly: .z80
 ZED: .zed
 Zig: .zig
 Zkl: .zkl
-Zoea Visual: .zoea
 Zoea: .zoea
+Zoea Visual: .zoea
 Zonnon: .zonnon
 Zoomscript: .zoom
 ZPL: .zpl

Lang/11l/Bioinformatics-base-count

@@ -0,0 +1 @@
+../../Task/Bioinformatics-base-count/11l

Lang/11l/Meissel-Mertens-constant

@@ -0,0 +1 @@
+../../Task/Meissel-Mertens-constant/11l

Lang/11l/Miller-Rabin-primality-test

@@ -0,0 +1 @@
+../../Task/Miller-Rabin-primality-test/11l

Lang/11l/Sorting-Algorithms-Circle-Sort

@@ -0,0 +1 @@
+../../Task/Sorting-Algorithms-Circle-Sort/11l

Lang/4D/00-LANG.txt

@@ -1,6 +1,3 @@
-{{stub}}
+{{stub}}{{language|4D}}{{IDE}}'''4D''' (or '''4th Dimension''') is a database management system and [[:Category:Integrated Development Environments|integrated development environment]] authored by Laurent Ribardière in 1984.
-{{language|4D
-|site=https://us.4d.com/
-}}{{IDE}}'''4D''' (or '''4th Dimension''') is a database management system and [[:Category:Integrated Development Environments|integrated development environment]] authored by Laurent Ribardière in 1984.
 ==Citations==
 *[[wp:4th_Dimension_%28Software%29|Wikipedia:4th Dimension (Software)]]

Lang/4ME/00-LANG.txt

@@ -1,7 +0,0 @@
-{{language|4ME
-|site=https://thevitebsk.github.io/4ME.by/}}
-4ME is a programing language created by [[User:Gaham]] implemented in 04.07.2024 MSK
-==See Also==
-* [https://esolangs.org/wiki/4ME 4ME in Esolangs.org]
-* [https://github.com/Thevitebsk/4me/ Github repo]
-[[Category:Programming paradigm/Concatenative]]

Lang/4ME/00-META.yaml

@@ -1,2 +0,0 @@
----
-from: http://rosettacode.org/wiki/Category:4ME

Lang/6502-Assembly/00-LANG.txt

@@ -131,29 +131,6 @@ This flag is set if the <code>BRK</code> command was executed. The BRK basically
 * Set with: <code>BRK</code>
 * Cleared with: <code>RTI</code>
 * There are no branches associated with this command.
-
-This flag is used only for differentiating a <code>BRK</code> from an hardware <code>IRQ</code>
-<syntaxhighlight lang="6502asm">IRQ:
-	STA saveAccumulator			; save accumulator
-	PLA							; get flags
-	STA saveFlags				; save flags
-	AND #$10					; check "break" flag
-	BNE IRQ_fromBreak			; if(break flag set){ goto IRQ_fromBreak; }
-		JMP IRQ_fromHardware	; else{ goto IRQ_fromInterrupt; }
-IRQ_fromBreak:
-	LDA saveFlags				; load flags from temp address
-	PHA							; restore flags to stack
-	LDA saveAccumulator			; restore accumulator
-	;...
-	RTI							; return from interrupt
-
-IRQ_fromInterrupt:
-	LDA saveFlags				; load flags from temp address
-	PHA							; restore flags to stack
-	LDA saveAccumulator			; restore accumulator
-	;...
-	RTI							; return from interrupt
-	</syntaxhighlight>
 <br><br>
 
 ===Decimal===

Lang/68000-Assembly/00-LANG.txt

@@ -3,36 +3,31 @@
 {{language}}
 68000 assembly is the assembly language used for the Motorola 68000, or commonly known as the 68K. It should not be confused with the 6800 (which predates it). The Motorola 68000 is a big-endian processor with full 32-bit capabilities (despite most systems that use it being considered 16-bit.) It was used in many computers such as the Amiga or the Canon Cat, as well as game consoles such as the Sega Genesis and Neo Geo.
 
+
 ==Architecture Overview==
 ===Big-Endian===
 The 68000, unlike most processors of its era, is big-endian. This means that bytes are stored from left to right. The example below illustrates this concept:
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.L #$12345678,$100000 ;store the hexadecimal numeral #$12345678 at memory address $100000
-MOVE.L #$12345678,$100000 ;store the hexadecimal numeral #$12345678 at memory address $100000
-</syntaxhighlight>
 
-<pre>
 ;hexdump of $100000:
 ;$100000 = $12
 ;$100001 = $34
 ;$100002 = $56
-;$100003 = $78
+;$100003 = $78</lang>
-</pre>
 
 On a little-endian processor such as in [[x86 Assembly]], the order of the bytes would be reversed, i.e.:
-<pre>
+<lang asm>;hexdump of $100000
-;hexdump of $100000
 ;$100000 = $78
 ;$100001 = $56
 ;$100002 = $34
-;$100003 = $12
+;$100003 = $12</lang>
-</pre>
 
-The main difference is that if you wanted to access this value as a byte or word it would be at a different address, whereas with a little endian architecture it is at the same address.
+This difference isn't usually relevant in the majority of situations, so don't concern yourself too much. It's much more important when doing [[6502 Assembly]] where registers are smaller than the address space.
 
 ===Notation Conventions===
 How you write the source code depends on your assembler and the syntax it uses. This page is written using Motorola syntax but there is also Milo syntax which has different conventions.
 
-How you go about defining numbers or text in your code varies wildly between assemblers.
+How you go about defining numbers or text in your code varies wildly between assemblers. I'm using VASM and these are the rules I have to follow, but your assembler may be different.
 
 * A number with a # in front represents a constant, literal value. For example, the 3 in <code>MOVE.B #3,D0</code> represents the number 3.
 
@@ -50,88 +45,72 @@ How you go about defining numbers or text in your code varies wildly between ass
 
 * The operand before the comma is the "source", and the operand after is the "destination." For example, <code>MOVE.L D3,D2</code> takes the value in D3 and stores it into D2, not the other way around. This is the opposite of x86 and ARM, which have the source on the right and the destination on the left.
 
-Data blocks, on the other hand, begin with <code>DC.B</code>, <code>DC.W</code>, or <code>DC.L</code> and each represents a constant numeric value. You do NOT prefix these with # to signify them as constants (doing so will cause an error on most assemblers). However, you can use the $ or % modifiers to denote hexadecimal or binary.
+
+Data blocks, on the other hand, begin with <code>DC.B</code>, <code>DC.W</code>, or <code>DC.L</code> and each represents a constant numeric value. Strangely, you do NOT prefix these with # to signify them as constants (doing so will cause an error on most assemblers). However, you can use the $ or % modifiers to denote hexadecimal or binary.
 
 Keep in mind that there is no requirement to use hexadecimal, decimal, or binary in your source code. It all gets converted to binary anyway. However, it is recommended to use the notation that is appropriate for how your data is meant to be interpreted, for readability purposes.
 
 ===Data Registers===
 There are eight 32-bit data registers on the 68000, numbered D0-D7. As the name implies, these are designed to hold data. Much like in [[ARM Assembly]], each one is identical in terms of which commands it can use. A command that can be used for D0 can be used for any other D-register.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.B #$FF,D0 ;move the hexadecimal value 0xFF into the bottom byte of D0.
-MOVE.B #$FF,D0 ;move the hexadecimal value 0xFF into the bottom byte of D0.
+ADD.W #$8000,D4 ;add hexadecimal 0x8000 to the value stored in D4.</lang>
-ADD.W #$8000,D4 ;add hexadecimal 0x8000 to the value stored in D4.
-</syntaxhighlight>
 
 ===Address Registers===
 There are eight of these as well, numbered A0-A7. A7 is reserved as the stack pointer, and is commonly referenced as SP in assemblers. The others are free to use for any purpose. Although these registers are 32-bit, the 68000's address space is 24-bit (ranges from 0x000000 to 0xFFFFFF), so the leftmost byte is ignored. You can do simple math involving these registers but more complicated commands like multiply or divide can only be used with data registers. Address registers are used to contain addresses and extract the values stored within.
 ====Loading From Memory====
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVEA.L #$200000,A2 ;usually these are loaded from a label.
-MOVEA.L #$200000,A2 ;usually these are loaded from a label.
 ;The hex dump of address $200000: 44 55 66 77
 MOVE.L #$00000000,D0
 MOVE.B (A2),D0 ;load the byte stored at $200000 into D0. D0 = #$00000044
 MOVE.W (A2),D0 ;load the word stored at $200000 into D0. D0 = #$00004455
 MOVE.L (A2),D0 ;load the long stored at $200000 into D0. D0 = #$44556677
-MOVE.L D2,(A5) ;store the contents of D2 into the memory address pointed to by A5.
+MOVE.L D2,(A5) ;store the contents of D2 into the memory address pointed to by A5.</lang>
-</syntaxhighlight>
+
 
 Note that it's also possible to transfer values to/from memory directly, without involving address registers at all. For constant memory locations, this is fine. However, the real strength of the address registers is in their pre-decrement and post-increment modes, which constant memory locations cannot use.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.L ($00FF0000),D0
-MOVE.L ($00FF0000),D0
 MOVE.W D1,($00FFFFFE)
-MOVE.W ($00FF0000),($00FF1000)
+MOVE.W ($00FF0000),($00FF1000)</lang>
-</syntaxhighlight>
 
 The use of parentheses is not required on most assemblers, but can be used as a reminder to someone reading your code that these represent the values stored at the specified memory locations rather than literal numbers.
 
 ====Post-Increment====
 The post-increment mode is specified by adding a + to the end of parentheses. This means that after the command is done, the address stored in the <b>address register</b> (not the value stored at that address) is increased by the byte length of the command (1 for <code>.B</code>, 2 for <code>.W</code>, 4 for <code>.L</code>). 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVEA.L #$00240000,A4 ;load the address $240000 into A4
-MOVEA.L #$00240000,A4 ;load the address $240000 into A4
 MOVE.W  (A4)+,D0      ;move the word stored at $240000 into D0, then increment to #$240002
 MOVE.L  (A4)+,D1      ;move the long stored at $240000 into D1, then increment to #$240006
-MOVE.L  (SP)+,D3      ;pop the top value of the stack into D3
+MOVE.L  (SP)+,D3      ;pop the top value of the stack into D3</lang>
-</syntaxhighlight>
 
 ====Pre-Decrement====
 The pre-decrement mode is specified by typing a - before the parentheses. This means that before the command is done, the address stored in the address register is decreased by the byte length of the command.
-<syntaxhighlight lang="68000devpac">MOVEA.L #$0024000A,A4 ;load the address $24000A into A4
+<lang 68000devpac>MOVEA.L #$0024000A,A4 ;load the address $24000A into A4
 MOVE.W  -(A4),D0      ;move the word stored at $240008 into D0
 MOVE.L  -(A4),D1      ;move the long stored at $240004 into D1
-MOVE.L  D2,-(SP)      ;push the contents of D2 onto the stack</syntaxhighlight>
+MOVE.L  D2,-(SP)      ;push the contents of D2 onto the stack</lang>
 
 ====Address Offsets====
 A memory address can be offset by a data register, an immediate value, or both. If a data register is used, only the bottom 2 bytes are considered. In either case, the contents of the data register and/or the immediate value are added to the value stored in the address register, and the value is read from that address at the specified length. The offsets are applied during the calculation only; the actual contents in the address register after the move are unchanged. Using a post-increment or pre-decrement with this addressing mode will only update the address by the specified length, not by the offsets.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.B (4,A0,D0),D1 ;The byte at A0+D0+4 is loaded into D1.</lang>
-MOVE.B (4,A0,D0),D1 ;The byte at A0+D0+4 is loaded into D1.
-</syntaxhighlight>
-
 It's possible to use the same data register as the offset and the destination. This does not cause any problems whatsoever, as the data register offset is "locked in" before the move, and is only updated after the command fully executes. Using the same command again immediately afterwards will offset based on the new value of that register.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.W (6,A0,D0),D0 ;The word at A0+D0+6 is read, then loaded into D0.</lang>
-MOVE.W (6,A0,D0),D0 ;The word at A0+D0+6 is read, then loaded into D0.
-</syntaxhighlight>
-
 A very important note is that when using this method with words and longs, the resulting address <b><i>must be even!</i></b> Otherwise the CPU will crash. For <code>MOVE.B</code> it doesn't matter.
 
 ====Effective Address====
 A calculated offset can be saved to an address register with the <code>LEA</code> command, which stands for "Load Effective Address." [[x86 Assembly]] also has this command, and it serves the same purpose. The syntax for it can be a bit misleading depending on your assembler.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>LEA myData,A0  ;load the effective address of myData into A0
-LEA myData,A0  ;load the effective address of myData into A0
 LEA (4,A0),A1  ;load into A1 the effective address A0+4. This looks like a dereference operation but it is not!
-MOVE.W (A1),D1 ;dereference A1, loading the value it points to into D1.
+MOVE.W (A1),D1 ;dereference A1, loading the value it points to into D1.</lang>
-</syntaxhighlight>
 
 This can get confusing, especially if you have tables of pointers. Just remember that <code>LEA</code> cannot dereference an address.
 
 If you don't want to store the effective address in an address register, you can use <code>PEA</code> (push effective address) to put it onto the stack instead.
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>LEA myData,A0 ;load the effective address of myData into A0
-LEA myData,A0 ;load the effective address of myData into A0
+PEA (4,A0)    ;store the effective address of A0+4 onto the stack.</lang>
-PEA (4,A0)    ;store the effective address of A0+4 onto the stack.
-</syntaxhighlight>
 
 ====The Stack====
 The 68000's stack is commonly referred to as <code>SP</code> but it is also address register <code>A7</code>. This register is handled differently than the other address registers when pushing bytes onto the stack. A byte value pushed onto the stack will be padded to the <b>right</b>. The stack needs to pad byte-length data so that it can stay word-aligned at all times. Otherwise the CPU would crash as soon as you tried to use the stack for anything other than a byte!
@@ -145,48 +124,48 @@ The 68000 can work with 8-bit, 16-bit, or 32-bit values. Some commands only work
 If you don't specify a length with your command, it usually defaults to word length, but ultimately it depends on the command you are using. (Some commands cannot be used at word length.)
 
 Bytes and words moved into a register are always stored on the right-hand side. For example:
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.L #$FFFFFFFF,D7
-MOVE.L #$FFFFFFFF,D7
 MOVE.B #$00,D7 ;D7 contains #$FFFFFF00
-MOVE.W #$2222,D7 ;D7 contains #$FFFF2222
+MOVE.W #$2222,D7 ;D7 contains #$FFFF2222</lang>
-</syntaxhighlight>
 
 As you can see, the rest of the register is unchanged. (On the ARM, it would turn to zeroes.) This is very important to remember. If your code is doing something unexpected it might be due to the "old" value of the register corrupting another function.
 
 If the given constant is smaller than the length provided, the value is padded to the left with zeroes.
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVE.W #$FF,D3 ;D3 = #$xxxx00FF, where x is the previous value of D3.
-MOVE.W #$FF,D3 ;D3 = #$xxxx00FF, where x is the previous value of D3.
+MOVE.L #0,D3   ;D3 = #$00000000</lang>
-MOVE.L #0,D3   ;D3 = #$00000000
-</syntaxhighlight>
 
 Loading immediate values into address registers is different. You can only move words or longer into address registers, and if you move a word, the value is sign-extended. This means that if the top nibble of the word is 8 or greater, the value gets padded to the left with Fs, and is padded with zeroes if the top nibble is 7 or less. If you're adding a constant value less than 7FFF to an address, it's usually safe to use the word length operation, which takes less bytes to encode than the long length version.
 
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MOVEA.W #$8000,A4 ;A4 = #$FFFF8000. Remember the top byte is ignored so this is the same as #$00FF8000.
-MOVEA.W #$8000,A4 ;A4 = #$FFFF8000. Remember the top byte is ignored so this is the same as #$00FF8000.
+MOVEA.W #$7FFF,A3 ;A3 = #$00007FFF</lang>
-MOVEA.W #$7FFF,A3 ;A3 = #$00007FFF
-</syntaxhighlight>
 
 ==The Flags==
 The flags are stored in the Condition Code Register, also known as the <code>CCR</code>. The 68000 has no built-in commands like <code>CLC</code> for clearing/setting individual flags. Rather, you can alter them directly with <code>MOVE</code>,<code>AND</code>,<code>OR</code>, and <code>EOR</code>. Unfortunately, this means you'll have to remember which bits represent which flags. Or, if your assembler supports macros, you can define a macro that handles this for you.
 
 The flags update automatically after most operations, and take into consideration the operand sizes when doing so. Check out this example:
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>
 MOVE.L #$12FF,D0
 ADD.B #1,D0
-</syntaxhighlight>
+</lang>
 
 Since we used <code>ADD.B</code>, D0 now contains $1200, and the extend, carry, and zero flags are all set. Had we done <code>ADD.W</code>, we would get $1300 in D0 with none of those flags set. The flags are based on what the actual instruction "sees", not the entire register at all times.
 
 * X: The eXtend flag is bit 4 of the CCR, and is similar to the carry flag. It gets set and cleared often for the same reasons and is used with the <code>ADDX</code>, <code>SUBX</code>, <code>NEGX</code>, <code>ROXL</code>, and <code>ROXR</code> commands. Why the 68000 has both this and the carry flag, I still don't know.
 
+
 * N: The negative flag is bit 3 of the CCR, and is set when the last operation resulted in a "negative" value. What constitutes a negative value depends on the size of the last operation - for <code>.B</code> instructions, $80-$FF. For <code>.W</code> instructions, $8000-$FFFF, and for <code>.L</code> instructions, $80000000-$FFFFFFFF.
 
+
 * Z: The zero flag is bit 2 of the CCR and works like you would expect - it's set whenever an operation results in zero. Unlike x86 Assembly, this also includes moving 0 directly into a register, clearing a register <b>or memory</b> with <code>CLR</code>, etc. 
 
+
 * V: The overflow flag is bit 1 of the CCR. It is set whenever a math operation results in a value crossing the $7F-$80 boundary. (Wraparound from 00 to FF doesn't count as overflow, but it does set the carry flag.)
 
+
 * C: The carry flag is bit 0 of the CCR. It is set when a math operation results in a carry or borrow. Rolling over from FF to 00, or a 1 getting "pushed out" via a bit shift or rotate, set the carry flag. When using <code>CMP</code>, the carry flag determines the unsigned magnitude comparison. Carry set is less than, carry clear is greater than or equal.
 
+
+
 In truth, the flags are a 16-bit register, of which the CCR is just the "low half". The SR (status register) is the full 16-bit register.
 There are a few additional flags in the upper half, which are used by the operating system. You can read these but for the most part you won't need to write to them.
 
@@ -210,15 +189,13 @@ The 68000 supports 7 different interrupts, often called IRQs or Interrupt Reques
 
 ==Alignment==
 The 68000 can only read or write words and longs at even addresses. Doing so at an odd address will result in the CPU crashing. (Note that reading byte data will not cause a crash regardless of whether it's located at an odd or even address.) This isn't usually a problem, but it can be if the programmer is not careful with the way their data is organized. Consider the following example:
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>TestData:
-TestData:
 DC.B $02
 DC.W $0345
 
 LEA TestData,A0 ;load effective address of TestData into A0.
 MOVE.B (A0)+,D0 ;load $02 into D0, increment A0 by 1
-MOVE.W (A0)+,D1 ;this crashes the CPU since A0 is now odd
+MOVE.W (A0)+,D1 ;this crashes the CPU since A0 is now odd</lang>
-</syntaxhighlight>
 
 How was it known that the address was odd at the second instruction? Simple. All instructions take an even number of bytes to encode. So there are only a few ways improper alignment can occur:
 * An odd value is loaded into an address register.
@@ -228,23 +205,18 @@ How was it known that the address was odd at the second instruction? Simple. All
 If the programmer is smart with the way they encode byte-length data they can avoid this problem entirely with little effort.
 
 One way is to separate byte-length data into its own table.
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>ByteData:
-ByteData:
 DC.B $20,$40,$60,$80
 
 WordData:
-DC.W $1000,$2000,$3000,$4000
+DC.W $1000,$2000,$3000,$4000</lang>
-</syntaxhighlight>
 
 Another way is to pad the data with an extra byte, so that there is an even number of entries in the table. This becomes impractical with large data tables, so the <code>EVEN</code> directive can be placed after a series of bytes. If the byte count is odd, <code>EVEN</code> will pad the data with an extra byte. If it's already even, the <code>EVEN</code> command is ignored. This saves you the trouble of having to count a long series of bytes without worrying about wasting space.
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>MyString: DC.B "HELLO WORLD 12345678900000",0
-MyString: DC.B "HELLO WORLD 12345678900000",0
+EVEN ;some assemblers require this to be on its own line</lang>
-EVEN ;some assemblers require this to be on its own line
-</syntaxhighlight>
 
 A third way is to perform a "dummy read." This is when a value is read from an address using pre-decrement or post-increment, with the sole purpose of moving the pointer, and the value being read is of zero interest. This method lets you work with mixed data types in the same table, but it requires the programmer to know in advance where the byte-length data begins and ends.
-<syntaxhighlight lang="68000devpac">
+<lang 68000devpac>TestData:
-TestData:
 DC.B $02,$03,$04
 DC.W $0345
 
@@ -255,8 +227,7 @@ MOVE.B (A0)+,(A1)+   ;copy $04 to a new memory location
 ;if we did MOVE.W (A0)+,(A1)+ now we'd crash. First we need to adjust the pointers.
 MOVE.B (A0)+,D7      ;dummy read to D7. Now A0 is word aligned.
 MOVE.B (A1)+,D7      ;dummy read to D7. Now A1 is word aligned.
-MOVE.W (A0)+,(A1)+   ;copy $0345 to a new memory location
+MOVE.W (A0)+,(A1)+   ;copy $0345 to a new memory location</lang>
-</syntaxhighlight>
 
 Using <code>ADDA.L #1,A0</code> and <code>ADDA.L #1,A1</code> would have worked also, instead of the dummy read. The 68000 gives the programmer a lot of different ways to do a task.
 

Lang/68000-Assembly/Musical-scale

@@ -1 +0,0 @@
-../../Task/Musical-scale/68000-Assembly

Lang/8080-Assembly/Align-columns

@@ -1 +0,0 @@
-../../Task/Align-columns/8080-Assembly

Lang/8080-Assembly/Display-a-linear-combination

@@ -1 +0,0 @@
-../../Task/Display-a-linear-combination/8080-Assembly

Lang/8080-Assembly/Integer-comparison

@@ -1 +0,0 @@
-../../Task/Integer-comparison/8080-Assembly

Lang/8080-Assembly/Loops-Infinite

@@ -1 +0,0 @@
-../../Task/Loops-Infinite/8080-Assembly

Lang/8080-Assembly/Ordered-words

@@ -1 +0,0 @@
-../../Task/Ordered-words/8080-Assembly

Lang/8080-Assembly/Run-length-encoding

@@ -1 +0,0 @@
-../../Task/Run-length-encoding/8080-Assembly

Lang/8080-Assembly/Sieve-of-Eratosthenes

@@ -1 +0,0 @@
-../../Task/Sieve-of-Eratosthenes/8080-Assembly

Lang/8080-Assembly/Square-but-not-cube

@@ -1 +0,0 @@
-../../Task/Square-but-not-cube/8080-Assembly

Lang/8080-Assembly/Twos-complement

@@ -1 +0,0 @@
-../../Task/Twos-complement/8080-Assembly

Lang/8080-Assembly/Zeckendorf-number-representation

@@ -1 +0,0 @@
-../../Task/Zeckendorf-number-representation/8080-Assembly

Lang/8086-Assembly/00-LANG.txt

@@ -4,13 +4,13 @@
 ===Segmented Memory===
 The 8086 uses a segmented memory model, similar to the Super Nintendo Entertainment System. Unlike banked memory models used in the Commodore 64 and late NES games, segment addresses are held in <i>segment registers</i>. These segment registers are 16 bit and get left-shifted by 4 and added to the pointer register of interest to determine the memory address to look up. The 8086 has four in total, but only the <code>DS</code> and <code>ES</code> registers can be used by the programmer. (The other two work with the stack pointer and instruction pointer, and are loaded for you.) On the 8086, you can only load segment registers with the value in a data register, or with the <code>POP</code> command. So first you must load a segment into a data register, THEN into a segment register.
 
-<syntaxhighlight lang="asm">;This is NOT valid code!
+<lang asm>;This is NOT valid code!
 mov ds, @data  ;you're trying to move the data segment location directly into DS. You can't!
 
 
 ;This is the proper way:
 mov ax, @data  ;I chose AX but I could have used BX, CX, or DX.
-mov ds, ax     ;load DS with the data segment.</syntaxhighlight>
+mov ds, ax     ;load DS with the data segment.</lang>
 
 It's important to remember the subtle distinction between a ''segment'' and a ''segment register.'' Your program might have labeled ''segments'' such as <code>.data</code> and <code>.code</code>, but in order to properly read from/write to these sections you'll need to load their memory locations into ''segment registers.''
 
@@ -18,17 +18,17 @@ It's important to remember the subtle distinction between a ''segment'' and a ''
 There are four data registers: <code>AX</code>, <code>BX</code>, <code>CX</code>, and <code>DX</code>. While most commands can use any of them, some only work with particular data registers. System calls in particular are very specific about which registers can be used for what. On [[MS-DOS]], the <code>AX</code> register is used for selecting the desired interrupt to use with the <code>INT</code> command.
 
 Each data register is 16-bit, but has two eight bit halves ending in H or L, e.g. <code>AH, AL</code>. Instructions can be executed using the whole register or just half of it.
-<syntaxhighlight lang="asm">mov ax, 1000h ;move 1000h into AX, or equivalently, move 10h into AH and 00h into AL.</syntaxhighlight>
+<lang asm>mov ax, 1000h ;move 1000h into AX, or equivalently, move 10h into AH and 00h into AL.</lang>
 Moving a value smaller than 16 bits into <code>?X</code> is the same as moving it into <code>?L</code>, and moving 0 into <code>?H</code>. (? represents the data register of your choice. They are all the same in this regard.)
 
-<syntaxhighlight lang="asm">mov ax,0030h
+<lang asm>mov ax,0030h
 ;is the same as:
 mov al, 30h
-mov ah, 0h</syntaxhighlight>
+mov ah, 0h</lang>
 
 Commands that alter the contents of a single register will not affect the other half.
-<syntaxhighlight lang="asm">mov ax,00FFh
+<lang asm>mov ax,00FFh
-inc al</syntaxhighlight>
+inc al</lang>
 If we had executed <code>INC AX</code>, then <code>AX</code> would have been incremented to 0x100. Since we only incremented <code>AL</code>, only <code>AL</code> was incremented in this case, and <code>AH</code> '''still equals 0x00!'''
 
 Generally speaking, the 8086's registers serve the following purposes:
@@ -42,24 +42,24 @@ When writing to or reading from consecutive sections of memory, it is helpful to
 
 The syntax for offsetting an index register will vary depending on your assembler. Many assemblers will often accept multiple different ways of writing it, and it comes down to personal preference.
 
-<syntaxhighlight lang="asm">mov si, offset MyArray
+<lang asm>mov si, offset MyArray
 mov bx,2
 
 mov al,[bx+si] ;loads decimal 30 into AL
 
 MyArray:
-byte 10,20,30,40,50</syntaxhighlight>
+byte 10,20,30,40,50</lang>
 
 ===The Stack===
 As with [[Z80 Assembly]], you can't push 8-bit registers onto the stack. For data registers, you have to push/pop both halves.
-<syntaxhighlight lang="asm">;This is valid code.
+<lang asm>;This is valid code.
 push ax
 push bx
 
 pop bx
 pop ax</lang>
 
-<syntaxhighlight lang="asm">;This is NOT valid code.
+<lang asm>;This is NOT valid code.
 push ah
 push al
 push bh
@@ -69,14 +69,14 @@ push bl
 pop bl
 pop bh
 pop al
-pop ah</syntaxhighlight>
+pop ah</lang>
 
 As with all processors that use a stack, if you push one or more registers and want to restore the backed-up values correctly, you must pop them in the reverse order. You can pop them out of order on purpose to swap registers around. In fact, this is a quick way to move the segment from <code>DS</code> into <code>ES</code>, or vice-versa:
-<syntaxhighlight lang="asm">push DS
+<lang asm>push DS
-pop ES ;you can't do "mov es, ds" but you can do this!</syntaxhighlight>
+pop ES ;you can't do "mov es, ds" but you can do this!</lang>
 
 The proper way to use the stack to preserve registers:
-<syntaxhighlight lang="asm">
+<lang asm>
 call foo
 
 mov ax,4C00h
@@ -91,7 +91,7 @@ push cx
 pop cx
 pop bx
 pop ax
-ret</syntaxhighlight>
+ret</lang>
 
 If one of the push/pop commands in the routine above were missing, the <code>RET</code> instruction would not properly return to where it came from. As long as you pop at the end the same number of registers you pushed at the start, the stack is "balanced" and your return instruction will return correctly. This is because <code>RET</code> is actually <code>POP IP</code> (<code>IP</code> being the instruction pointer, which you can think of as what "line" of code the CPU is on.) The CPU assumes the top of the stack is the correct place to return to, but has no way of actually verifying it. If the function you just wrote causes the CPU to crash or jump to a completely different part of the code, there's a good chance you might have forgotten to balance the stack properly.
 
@@ -107,40 +107,40 @@ One other caveat to mention: On early IBM PCs and compatibles, the 8087 was not
 ===Looping Constructs===
 The 8086 has a lot more of these than most CPUs. The most obvious one is <code>LOOP</code>, which will subtract 1 from <code>CX</code>, then jump back to a specified label if <code>CX</code> is nonzero after the subtraction. If <code>CX</code> becomes zero after subtracting 1, then no jump will occur and the instruction pointer simply moves to the next instruction.
 
-<syntaxhighlight lang="asm">mov cx,0100h ;set the loop counter's starting value. This must be outside the loop, otherwise you'll loop forever!
+<lang asm>mov cx,0100h ;set the loop counter's starting value. This must be outside the loop, otherwise you'll loop forever!
 
 foo:
 ;; your code that you want to loop goes here
-loop foo </syntaxhighlight>
+loop foo </lang>
 
 It's important not to alter <code>CX</code> inside the loop. It's easy to make a mistake like this if you're in a hurry:
 
-<syntaxhighlight lang="asm">foobar:
+<lang asm>foobar:
 mov cx,1000h
 ;your code goes here
-loop foobar</syntaxhighlight>
+loop foobar</lang>
 
 It may not be obvious at first but the above loop will never end. <code>CX</code> decrements to 0x0FFF with the <code>LOOP</code> instruction but the <code>mov cx,1000h</code> was mistakenly placed ''inside'' the loop, resetting the loop counter back to 0x1000, which means no progress is really being made. The correct way to do this is to set the starting loop counter '''outside''' the loop, like so:
 
-<syntaxhighlight lang="asm">mov cx,1000h
+<lang asm>mov cx,1000h
 foobar:
 ;your code goes here
-loop foobar</syntaxhighlight>
+loop foobar</lang>
 
 Sometimes you'll have to change <code>CX</code> during a loop, like if you want to do bit shifts with a shift amount other than 1, for example. There's a simple fix - use the stack to stash and retrieve the loop counter.
-<syntaxhighlight lang="asm">mov cx,0100h
+<lang asm>mov cx,0100h
 
 foo:
 push cx
    mov cl,2
    ror ax,cl   ;starting with the 80186 you don't need CL for bit shifting.
 pop cx
-loop foo</syntaxhighlight>
+loop foo</lang>
 
 By using <code>PUSH CX</code> and <code>POP CX</code>, you can temporarily use <code>CX</code> for something else, as long as you restore it before the <code>LOOP</code> instruction.
 
 You can use other registers as loop counters as well, but not with the <code>LOOP</code> instruction - it's hardcoded to only work with <code>CX</code>. But you can do this:
-<syntaxhighlight lang="asm">mov dx,0100h
+<lang asm>mov dx,0100h
 baz:
 ;your code goes here
 dec dx
@@ -148,7 +148,7 @@ jnz baz
 ; A minor note for advanced programmers:
 ; If you're expecting the flags to be in a particular state based on the loop body, tough luck!
 ; They'll only reflect the decrement of DX from 1 to 0 at this point in the code.
-; LOOP doesn't change the flags, which makes it more useful for loops meant to compare things.</syntaxhighlight>
+; LOOP doesn't change the flags, which makes it more useful for loops meant to compare things.</lang>
 
 
 Another frequently used looping construct is <code>REP</code>. <code>REP</code> can be combined with certain instructions to repeat that instruction until <code>CX</code> equals zero. However, unlike <code>LOOP</code>, which can be used to repeat a block of instructions, <code>REP</code> can only repeat one. It doesn't work on all instructions, only the "string" instructions which operate on a block of memory. Typically these include <code>MOVSB</code>, <code>LODSB</code>, <code>STOSB</code>, <code>CMPSB</code>, and <code>SCASB</code> (each has a variant that ends in W instead of B, for 16-bit data.) There are also <code>REPZ</code> and <code>REPNZ</code>, which stand for "Repeat if Zero" and "Repeat if Nonzero" respectively. These two only work properly with <code>CMPSB</code> and <code>SCASB</code>, as <code>MOVSB</code>, <code>LODSB</code>, <code>STOSB</code> do not affect the flags. (The CPU doesn't detect whether <code>CX</code> equals zero using the flags, as the flags never reflect this equality to zero like you would expect.)

Lang/8th/Angle-difference-between-two-bearings

@@ -1 +0,0 @@
-../../Task/Angle-difference-between-two-bearings/8th

Lang/8th/Environment-variables

@@ -1 +0,0 @@
-../../Task/Environment-variables/8th

Lang/8th/Factorial

@@ -1 +0,0 @@
-../../Task/Factorial/8th

Lang/AArch64-Assembly/Bifid-cipher

@@ -1 +0,0 @@
-../../Task/Bifid-cipher/AArch64-Assembly

Lang/AArch64-Assembly/Binary-strings

@@ -1 +0,0 @@
-../../Task/Binary-strings/AArch64-Assembly

Lang/AArch64-Assembly/Bioinformatics-base-count

@@ -0,0 +1 @@
+../../Task/Bioinformatics-base-count/AArch64-Assembly

Lang/AArch64-Assembly/Calculating-the-value-of-e

@@ -1 +0,0 @@
-../../Task/Calculating-the-value-of-e/AArch64-Assembly

Lang/AArch64-Assembly/Comma-quibbling

@@ -1 +0,0 @@
-../../Task/Comma-quibbling/AArch64-Assembly

Lang/AArch64-Assembly/Compound-data-type

@@ -1 +0,0 @@
-../../Task/Compound-data-type/AArch64-Assembly

Lang/AArch64-Assembly/Conways-Game-of-Life

@@ -1 +0,0 @@
-../../Task/Conways-Game-of-Life/AArch64-Assembly

Lang/AArch64-Assembly/Create-an-HTML-table

@@ -1 +0,0 @@
-../../Task/Create-an-HTML-table/AArch64-Assembly

Lang/AArch64-Assembly/Determine-sentence-type

@@ -1 +0,0 @@
-../../Task/Determine-sentence-type/AArch64-Assembly

Lang/AArch64-Assembly/Environment-variables

@@ -1 +0,0 @@
-../../Task/Environment-variables/AArch64-Assembly

Lang/AArch64-Assembly/Fibonacci-n-step-number-sequences

@@ -1 +0,0 @@
-../../Task/Fibonacci-n-step-number-sequences/AArch64-Assembly

Lang/AArch64-Assembly/Fibonacci-sequence

@@ -1 +0,0 @@
-../../Task/Fibonacci-sequence/AArch64-Assembly

Lang/AArch64-Assembly/Halt-and-catch-fire

@@ -1 +0,0 @@
-../../Task/Halt-and-catch-fire/AArch64-Assembly

Lang/AArch64-Assembly/Hash-from-two-arrays

@@ -1 +0,0 @@
-../../Task/Hash-from-two-arrays/AArch64-Assembly

Lang/AArch64-Assembly/Hofstadter-Q-sequence

@@ -1 +0,0 @@
-../../Task/Hofstadter-Q-sequence/AArch64-Assembly

Lang/AArch64-Assembly/Keyboard-input-Obtain-a-Y-or-N-response

@@ -1 +0,0 @@
-../../Task/Keyboard-input-Obtain-a-Y-or-N-response/AArch64-Assembly

Lang/AArch64-Assembly/Leonardo-numbers

@@ -1 +0,0 @@
-../../Task/Leonardo-numbers/AArch64-Assembly

Lang/AArch64-Assembly/Logical-operations

@@ -1 +0,0 @@
-../../Task/Logical-operations/AArch64-Assembly

Lang/AArch64-Assembly/Machine-code

@@ -1 +0,0 @@
-../../Task/Machine-code/AArch64-Assembly

Lang/AArch64-Assembly/Magic-8-ball

@@ -1 +0,0 @@
-../../Task/Magic-8-ball/AArch64-Assembly

Lang/AArch64-Assembly/Mandelbrot-set

@@ -1 +0,0 @@
-../../Task/Mandelbrot-set/AArch64-Assembly

Lang/AArch64-Assembly/Menu

@@ -1 +0,0 @@
-../../Task/Menu/AArch64-Assembly

Lang/AArch64-Assembly/Miller-Rabin-primality-test

@@ -0,0 +1 @@
+../../Task/Miller-Rabin-primality-test/AArch64-Assembly

Lang/AArch64-Assembly/Phrase-reversals

@@ -1 +0,0 @@
-../../Task/Phrase-reversals/AArch64-Assembly

Lang/AArch64-Assembly/Pi

@@ -1 +0,0 @@
-../../Task/Pi/AArch64-Assembly

Lang/AArch64-Assembly/Read-a-configuration-file

@@ -1 +0,0 @@
-../../Task/Read-a-configuration-file/AArch64-Assembly

Lang/AArch64-Assembly/Repeat-a-string

@@ -1 +0,0 @@
-../../Task/Repeat-a-string/AArch64-Assembly

Lang/AArch64-Assembly/Reverse-words-in-a-string

@@ -1 +0,0 @@
-../../Task/Reverse-words-in-a-string/AArch64-Assembly

Lang/AArch64-Assembly/Sorting-Algorithms-Circle-Sort

@@ -0,0 +1 @@
+../../Task/Sorting-Algorithms-Circle-Sort/AArch64-Assembly

Lang/AArch64-Assembly/Strip-block-comments

@@ -1 +0,0 @@
-../../Task/Strip-block-comments/AArch64-Assembly

Lang/AArch64-Assembly/Strip-comments-from-a-string

@@ -1 +0,0 @@
-../../Task/Strip-comments-from-a-string/AArch64-Assembly

Lang/AArch64-Assembly/Strip-whitespace-from-a-string-Top-and-tail

@@ -1 +0,0 @@
-../../Task/Strip-whitespace-from-a-string-Top-and-tail/AArch64-Assembly

Lang/AArch64-Assembly/Twos-complement

@@ -1 +0,0 @@
-../../Task/Twos-complement/AArch64-Assembly

Lang/AArch64-Assembly/Update-a-configuration-file

@@ -1 +0,0 @@
-../../Task/Update-a-configuration-file/AArch64-Assembly

Lang/AArch64-Assembly/Vigen-re-cipher

@@ -1 +0,0 @@
-../../Task/Vigen-re-cipher/AArch64-Assembly

Lang/AArch64-Assembly/Vigen-re-cipher-Cryptanalysis

@@ -1 +0,0 @@
-../../Task/Vigen-re-cipher-Cryptanalysis/AArch64-Assembly

Lang/AArch64-Assembly/Visualize-a-tree

@@ -1 +0,0 @@
-../../Task/Visualize-a-tree/AArch64-Assembly

Lang/ABAP/00-LANG.txt

@@ -1,14 +1,2 @@
-{{stub}}{{language
+{{stub}}{{language|site=http://www.sdn.sap.com/irj/sdn/abap}}
-|site=http://www.sdn.sap.com/irj/sdn/abap
+ABAP (Advanced Business Application Programming) is a programming language developed by the german software vendor SAP. It is mainly used to build high performance business applications.
-|safety=safe
-|strength=strong
-|compat=nominative
-|checking=static
-|tags=abap}}
-ABAP (Advanced Business Application Programming) is a programming language developed by the german software vendor SAP. It is mainly used to build high performance business applications.
-
-==Citation==
-*[https://en.wikipedia.org/wiki/ABAP]
-
-[[Category:Programming paradigm/Object-oriented]]
-[[Category:Programming paradigm/Imperative]]

Lang/ABC/Arithmetic-derivative

@@ -1 +0,0 @@
-../../Task/Arithmetic-derivative/ABC

Lang/ABC/Look-and-say-sequence

@@ -1 +0,0 @@
-../../Task/Look-and-say-sequence/ABC

Lang/ABC/Population-count

@@ -1 +0,0 @@
-../../Task/Population-count/ABC

Lang/ABC/Square-but-not-cube

@@ -1 +0,0 @@
-../../Task/Square-but-not-cube/ABC

Lang/ABC/Zeckendorf-number-representation

@@ -1 +0,0 @@
-../../Task/Zeckendorf-number-representation/ABC

Lang/AIDED-NATURAL-LANGUAGE/00-LANG.txt

@@ -1 +0,0 @@
-{{stub}}{{language|Ayrch}}

Lang/AIDED-NATURAL-LANGUAGE/00-META.yaml

@@ -1,2 +0,0 @@
----
-from: http://rosettacode.org/wiki/Category:AIDED_NATURAL_LANGUAGE

Lang/ALGOL-60/00-LANG.txt

@@ -16,9 +16,4 @@ gcc hello.c -lalgol -lm -o hello
 *[[wp:ALGOL 60|ALGOL 60 on Wikipedia]]
 *[[ALGOL 68]]
 *[[ALGOL W]]
-*[[Simula]]
+*[[Simula]]
-
-==External links==
-* [http://algol60.org algol60.org]
-* [https://softwarepreservation.computerhistory.org/ALGOL/ History of ALGOL] Includes links to documentation (e.g. reports)
-* [https://www.masswerk.at/algol60/report.htm Revised Report on the Algorithmic Language Algol 60] (HTML)

Lang/ALGOL-60/Additive-primes

@@ -1 +0,0 @@
-../../Task/Additive-primes/ALGOL-60

Lang/ALGOL-60/Anti-primes

@@ -1 +0,0 @@
-../../Task/Anti-primes/ALGOL-60

Lang/ALGOL-60/Even-or-odd

@@ -1 +0,0 @@
-../../Task/Even-or-odd/ALGOL-60

Lang/ALGOL-60/Factorial

@@ -0,0 +1 @@
+../../Task/Factorial/ALGOL-60

Lang/ALGOL-60/Harmonic-series

@@ -1 +0,0 @@
-../../Task/Harmonic-series/ALGOL-60

Lang/ALGOL-60/Horners-rule-for-polynomial-evaluation

@@ -1 +0,0 @@
-../../Task/Horners-rule-for-polynomial-evaluation/ALGOL-60

Lang/ALGOL-60/Integer-comparison

@@ -1 +0,0 @@
-../../Task/Integer-comparison/ALGOL-60

Lang/ALGOL-60/Largest-proper-divisor-of-n

@@ -1 +0,0 @@
-../../Task/Largest-proper-divisor-of-n/ALGOL-60

Lang/ALGOL-60/Loops-Increment-loop-index-within-loop-body

@@ -1 +0,0 @@
-../../Task/Loops-Increment-loop-index-within-loop-body/ALGOL-60

Lang/ALGOL-60/Nth-root

@@ -1 +0,0 @@
-../../Task/Nth-root/ALGOL-60

Lang/ALGOL-60/Prime-decomposition

@@ -1 +0,0 @@
-../../Task/Prime-decomposition/ALGOL-60

Lang/ALGOL-60/Proper-divisors

@@ -1 +0,0 @@
-../../Task/Proper-divisors/ALGOL-60

Lang/ALGOL-60/Semiprime

@@ -1 +0,0 @@
-../../Task/Semiprime/ALGOL-60

Lang/ALGOL-60/Sequence-of-primes-by-trial-division

@@ -1 +0,0 @@
-../../Task/Sequence-of-primes-by-trial-division/ALGOL-60

Lang/ALGOL-60/Square-free-integers

@@ -1 +0,0 @@
-../../Task/Square-free-integers/ALGOL-60

Lang/ALGOL-60/Sum-of-a-series

@@ -1 +0,0 @@
-../../Task/Sum-of-a-series/ALGOL-60

Lang/ALGOL-60/Tau-function

@@ -1 +0,0 @@
-../../Task/Tau-function/ALGOL-60

Lang/ALGOL-60/Tau-number

@@ -1 +0,0 @@
-../../Task/Tau-number/ALGOL-60

Lang/ALGOL-68/00-LANG.txt

@@ -41,7 +41,7 @@ A syntax chart is available [http://www.softwarepreservation.org/projects/ALGOL/
 * [http://www.linkedin.com/groups/Algol68-2333923 Algol68 group at linkedin] - includes various famous compiler composers.
 <br>
 '''Books available online''':
-* [https://algol68genie.nl/ Algol 68G Manual - By Marcel van der Veer] Includes the Revised Report
+* [http://jmvdveer.home.xs4all.nl/en.algol-68-genie.html Algol 68G Manual - By Marcel van der Veer] Includes the Revised Report
 * [http://www.softwarepreservation.org/projects/ALGOL/book/pame.2008.a4.pdf/view Programming Algol 68 Made Easy -  by Sian Mountbatten (on softwarepreservation.org)]
 * [http://www.softwarepreservation.org/projects/ALGOL/book/Lindsey_van_der_Meulen-IItA68-Revised.pdf/view Informal Introduction to Algol 68 - by C. H. Lindsey & S. V. Van der Meulen (on softwarepreservation.org)] - if you prefer (and find) a hardcopy, be sure to get the 1977 edition. Highly recomended!
 
@@ -59,7 +59,7 @@ A syntax chart is available [http://www.softwarepreservation.org/projects/ALGOL/
 ** AND 50th Birthday '''ALGOL 58'''.
 * 23rd August 2009 - [http://sourceforge.net/projects/algol68/files/ algol68g-1.18.0-9h] released
 * 20th December 2009 - Happy 51st/41st Birthdays with [[Hamming_numbers#ALGOL_68|Hamming numbers]] - the 200th '''ALGOL 68''' code contribution on rosettacode.org!  
-** This time code was by [[User:Algol68g|Marcel van der Veer]], author of [https://algol68genie.nl Algol 68 Genie]
+** This time code was by [[User:Algol68g|Marcel van der Veer]], author of [http://www.xs4all.nl/~jmvdveer/algol.html Algol 68 Genie]
 * 25th October 2011 - [[User:Jejones3141|Jejones3141]] added [[Soundex#ALGOL_68|Soundex]] - the 300th '''ALGOL 68''' code specimen.
 
 == Revisions ==
@@ -67,12 +67,203 @@ A syntax chart is available [http://www.softwarepreservation.org/projects/ALGOL/
 *Oct. 1968: Penultimate Draft Report on the Algorithmic Language ALGOL 68 - Chapters 1-9 - Edited by: A. van Wijngaarden, B.J. Mailloux, J.E.L. Peck and C.H.A. Koster.
 *Dec. 1968: Report on the Algorithmic Language ALGOL 68 - Offprint from Numerische Mathematik, 14, 79-218 (1969); Springer-Verlag. - Edited by: A. van Wijngaarden, B.J. Mailloux, J.E.L. Peck and C.H.A. Koster.  
 *Sep 1973: Revised Report on the Algorithmic Language Algol 68 - Springer-Verlag 1976 - Edited by: A. van Wijngaarden, B.J. Mailloux, J.E.L. Peck, C.H.A. Koster, M. Sintzoff, C.H. Lindsey, L.G.L.T. Meertens and R.G. Fisker.
-==Coding style of samples, alphabets and stropping==
+==Coding style of samples==
-See [[ALGOL 68 Representation]].
+Click "Expand" for more details.
+<div class="mw-collapsible mw-collapsed" style="width:880px; overflow:auto; background-color:parent;">
+<div class="mw-collapsible-content" style="padding-left:2em;">
+
+Many of the code samples provided here have a leading <code>main:(</code> and a matching <code>)</code> at the end. These are not actually required in the language, but are included so as to highlight the main routine.
+
+On some compilers, it may be necessary to include appropriate "job cards" 
+or preludes in order for the programs to compile successfully. Hopefully 
+not too much else is required. Examples:
+{|border="1" style="border-collapse: collapse; border: 5px double grey;"  align="center" 
+|| Brief Algol68
+|| Algol68 as in rosettacode
+|| Actual ELLA Algol 68RS code
+|-
+||
+ print(("Hello, world!",new line))
+||
+ main:(
+   print(("Hello, world!",new line))
+ )
+||
+ PROGRAM helloworld CONTEXT VOID
+ USE standard
+ BEGIN
+   print(("Hello, world!", new line))
+ END
+ FINISH
+|}
+<br><br>'''Examples of different program representations'''
+<br><br>
+At the time when ALGOL 68 was defined some predominant computers had 
+24 or 36 bit words, with 6 bit character sets.  Hence it was desirable that
+ALGOL 68 should be able to run on machines with only uppercase.   
+The official spec provided for different representations of the same 
+program. Quote stropping (enclosing the bold words in single quotes)
+and Point stropping (preceeding the bold words with a dot)
+were used.  A variant of Point stropping called RES stropping was also defined.
+In RES stropping some language-defined bold words are not preceded by a dot.   
+A pragmatic comment may have been required to indicate which
+stropping convention was to be used, as in some of the examples below.
+Upper stropping (representing the bold words by upper case and
+non-bold words in lower case) was introduced by Algol 68R. Upper stropping
+is used by Algol 68RS and is one of the options for Algol 68G.
+Rutgers ALGOL 68 uses quote stropping. Most of the samples
+on Rosetta Code use Upper stropping.
+Examples (pragmatic comments to set the stropping regime not shown):
+{|border="1" style="border-collapse: collapse; border: 2px double grey;"  align="left" 
+|| Algol68 as typically published
+ '''mode''' '''xint''' = '''int''';
+ '''xint''' sum sq:=0;
+ '''for''' i '''while'''
+   sum sq≠70&times;70
+ '''do'''
+   sum sq+:=i↑2
+ '''od''' 
+|| QUOTE stropping (similar to wiki)
+ 'mode' 'xint' = 'int';
+ 'xint' sum sq:=0;
+ 'for' i 'while'
+   sum sq≠70&times;70
+ 'do'
+   sum sq+:=i↑2
+ 'od' 
+|| POINT stropping
+ .MODE .XINT = .INT;
+ .XINT SUM SQ:=0;
+ .FOR I .WHILE
+   SUM SQ .NE 70*70
+ .DO
+   SUM SQ .PLUSAB I .UP 2
+ .OD
+|| RES stropping
+ mode .xint = int;
+ .xint sum sq:=0;
+ for i while
+   sum sq≠70&times;70
+ do
+   sum sq+:=i↑2
+ od 
+|| Upper stropping
+ MODE XINT = INT;
+ XINT sum sq:=0;
+ FOR i WHILE
+   sum sq /= 70*70
+ DO
+   sum sq PLUSAB i UP 2
+ OD
+|}
+
+</div></div>
 
 == Coercion (casting) ==
-ALGOL 68 has a hierarchy of contexts which determine which kind of coercions are available at a particular point in the program.<br/>
+ALGOL 68 has a hierarchy of contexts which determine which kind of coercions are available at a particular point in the program.
-See [[:Category:ALGOL_68_Coercions|ALGOL 68 Coercions]] for more details.
+<br>
+Click "Expand" for more details.
+<div class="mw-collapsible mw-collapsed" style="width:880px; overflow:auto; background-color:parent;">
+<div class="mw-collapsible-content" style="padding-left:2em;">
+
+These contexts are:
+{|class="wikitable"
+!rowspan=2| N<br>
+a<br>
+m<br>
+e
+!rowspan=2| Context location 
+!colspan=5| Coercions available in this context
+!rowspan=2| Coercion examples
+|-
+|bgcolor=aaaaff|Soft
+|bgcolor=aaeeaa|Weak
+|bgcolor=ffee99|Meek
+|bgcolor=ffcc99|Firm
+|bgcolor=ffcccc|Strong
+|-
+!S<br>
+t<br>
+r<br>
+o<br>
+n<br>
+g 
+||Right hand side of:
+* Identity-declarations, as "~" in: <syntaxhighlight algol68>REAL x = ~</syntaxhighlight>
+* Initialisations, as "~" in: <syntaxhighlight algol68>REAL x := ~</syntaxhighlight>
+Also:
+* Actual-parameters of calls, as "~" in:<syntaxhighlight algol68>PROC: sin(~)</syntaxhighlight>
+* Enclosed clauses of casts, as "~" in: <syntaxhighlight algol68>REAL(~)</syntaxhighlight>
+* Units of routine-texts
+* Statements yielding VOID
+* All parts (but one) of a balanced clause
+* One side of an identity relation, as "~" in: <syntaxhighlight algol68> ~ IS ~</syntaxhighlight>
+|bgcolor=aaaaff rowspan=4 width="50px"| deproc- eduring
+|bgcolor=aaeeaa rowspan=3 width="50px"| all '''soft''' then weak deref- erencing
+|bgcolor=ffee99 rowspan=2 width="50px"| all '''weak''' then deref- erencing
+|bgcolor=ffcc99 rowspan=1 width="50px"| all '''meek''' then uniting 
+|bgcolor=ffcccc width="50px"| all '''firm''' then widening, rowing and voiding
+|colspan=1 bgcolor=ffcccc|
+Widening occurs if there is no loss of precision. For example: An INT will be coerced to a REAL, and a REAL will be coerced to a LONG REAL.  But not vice-versa.  Examples:
+<syntaxhighlight algol68>INT to LONG INT
+INT to REAL
+REAL to COMPL
+BITS to []BOOL
+BYTES to STRING</syntaxhighlight>
+A variable can also be coerced (rowed) to an array of length 1.  
+
+For example:
+<syntaxhighlight algol68>INT to [1]INT
+REAL to [1]REAL</syntaxhighlight> etc
+|-
+!F<br>
+i<br>
+r<br>
+m
+||
+*Operands of formulas as "~" in:<syntaxhighlight algol68>OP: ~ * ~</syntaxhighlight>
+*Parameters of transput calls
+|colspan=3 bgcolor=ffcc99| Example:
+<syntaxhighlight algol68>UNION(INT,REAL) var := 1</syntaxhighlight>
+|-
+!M<br>
+e<br>
+e<br>
+k
+||
+* Trimscripts (yielding INT)
+* Enquiries: e.g. as "~" in the following
+<syntaxhighlight algol68>IF ~ THEN ... FI</syntaxhighlight> and 
+<syntaxhighlight algol68>FROM ~ BY ~ TO ~ WHILE ~ DO ... OD etc</syntaxhighlight>
+* Primaries of calls (e.g. sin in sin(x))
+|colspan=4 bgcolor=ffee99|Examples:
+<syntaxhighlight algol68>REF REF BOOL to BOOL
+REF REF REF INT to INT</syntaxhighlight>
+|-
+!W<br>
+e<br>
+a<br>
+k
+||
+* Primaries of slices, as in "~" in: <syntaxhighlight algol68>~[1:99]</syntaxhighlight>
+* Secondaries of selections, as "~" in: <syntaxhighlight algol68>value OF ~</syntaxhighlight>
+|colspan=5 bgcolor=aaeeaa|Examples:
+<syntaxhighlight algol68>REF BOOL to REF BOOL
+REF REF INT to REF INT
+REF REF REF REAL to REF REAL
+REF REF REF REF STRUCT to REF STRUCT</syntaxhighlight>
+|-
+!S<br>
+o<br>
+f<br>
+t
+|| The LHS of assignments, as "~" in: <syntaxhighlight algol68>~ := ...</syntaxhighlight>
+|colspan=6 bgcolor=aaaaff| Example:
+* deproceduring of: <syntaxhighlight algol68>PROC REAL random: e.g. random</syntaxhighlight>
+|}
+For more details about Primaries and Secondaries refer to [[Operator_precedence#ALGOL_68|Operator precedence]].
+
+</div></div>
 
 ==See also==
 *[[Web 68]]
@@ -82,22 +273,13 @@ See [[:Category:ALGOL_68_Coercions|ALGOL 68 Coercions]] for more details.
 * [[Action!]]
 * [[Agena]]
 * [[Draco]]
-* [[RTL/2]]
 * [https://en.wikipedia.org/wiki/S3_(programming_language) S3 for ICL 2900]
 
 == Library code used in Rosetta Code samples ==
-* [[ALGOL_68/prelude|Various (including the standard prelude)]]
+[https://rosettacode.org/wiki/ALGOL_68/prelude Various (including the standard prelude)]<br/>
-*
+[https://rosettacode.org/wiki/Category:ALGOL_68-primes Prime related]<br/>
-* [[:Category:ALGOL_68-bits|bit-manipulation related]]
+[https://rosettacode.org/wiki/Category:ALGOL_68-rows Row (array) related]<br/>
-* [[:Category:ALGOL_68-files|File related]]
+[https://rosettacode.org/wiki/Category:ALGOL_68-l-system L-System related]
-* [[:Category:ALGOL_68-l-system|L-System related]]
-* [[:Category:ALGOL_68-primes|Prime related]]
-* [[:Category:ALGOL_68-rows|Row (array) related]]
-* [[:Category:ALGOL_68-sort|Sorting related]]
-
-== Tools ==
-[[Syntax_highlighting_using_Mediawiki_formatting#ALGOL 68|Format an upper-stropped Algol 68 source with Mediawiki markup]]<br/>
-[[Compiler/Simple_file_inclusion_pre_processor#ALGOL 68|Implement ''read'' and ''include'' pragmatic-comments for compilers that don't support file inclusion]]
 
 {{language programming paradigm|Concurrent}}
 {{language programming paradigm|Imperative}}

Lang/ALGOL-68/100-prisoners

@@ -1 +0,0 @@
-../../Task/100-prisoners/ALGOL-68

Lang/ALGOL-68/21-game

@@ -1 +0,0 @@
-../../Task/21-game/ALGOL-68

Lang/ALGOL-68/9-billion-names-of-God-the-integer

@@ -1 +0,0 @@
-../../Task/9-billion-names-of-God-the-integer/ALGOL-68

Lang/ALGOL-68/Archimedean-spiral

@@ -1 +0,0 @@
-../../Task/Archimedean-spiral/ALGOL-68

Lang/ALGOL-68/Arithmetic-geometric-mean-Calculate-Pi

@@ -1 +0,0 @@
-../../Task/Arithmetic-geometric-mean-Calculate-Pi/ALGOL-68

Lang/ALGOL-68/Bifid-cipher

@@ -1 +0,0 @@
-../../Task/Bifid-cipher/ALGOL-68

Lang/ALGOL-68/Bioinformatics-base-count

@@ -0,0 +1 @@
+../../Task/Bioinformatics-base-count/ALGOL-68