Use Bikeshed’s algorithm construct.

[tobie]

This PR:

• marks up all algorithms with <div algorithm>,
• gives a name to those which don't include a <dfn>,
• turns single step algorithms (e.g. return false) to prose.
• Fix algorithms that generated Bikeshed warnings (due to missing variables or mistakes in variable names).

This PR is too big to be apprehended as a whole in GitHub, however it's split into explicitly named commits.

The first commit is just a markup change, as shown by its HTML diff.

Every following commit is atomic and addresses a particular issue raised by Bikeshed.

---

Preview | Diff

Per Commit Preview & Diffs

b6b4453: Preview | Diff w/ Head (2016-10-21 11:03)
8d188f5: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 06:29)
ad0c8fd: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 07:50)
32b176d: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 08:21)
8b14740: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 08:24)
50fc7e9: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 08:39)
aa81166: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 09:11)
735054f: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 10:02)
da785b7: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 12:14)
6c5dd1b: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 12:29)
c442f0e: Preview | Diff w/ Head | Diff w/ Previous (2016-10-23 12:32)
Latest (a605edb): Preview | Diff w/ Head | Diff w/ Previous (2016-10-25 17:13)

[domenic]

turns single step algorithms (e.g. return false) to prose.

Not a big fan of this personally. Having algorithms always be nice numbered lists helps me immensely when reading and understanding.

[tobie]

turns single step algorithms (e.g. return false) to prose.

Not a big fan of this personally. Having algorithms always be nice numbered lists helps me immensely when reading and understanding.

OK. There's a lot of single step algorithms which are folded into prose, e.g.: most IDL to ES type mappings. Would you want those fixed at some point? I don't care either way, but I'd like consistency in the spec.

[domenic]

Ah interesting point. I think fixing those would be good, yeah.

[tobie]

OK, this is now ready to be reviewed.

[marcoscaceres]

Github can't show all the changes :( You might need to send this in chunks?

[marcoscaceres]

Actually, nm. Can look at the commits individually.

[tobie]

Folks, it would really help if someone actually reviewed the following commits:

• 8d188f5 (Replace prose calls to [[Call]] method by Call(args).)
• ad0c8fd (Fix incorrectly named variables.)
• 735054f (Fix copy/paste error in map serialiser algorithm.)
• c442f0e (Fix invoke algorithm.)

These are all bugs in the spec uncovered by using Bikeshed's algorithm construct. It shouldn't take a lot of your time, but would allow me to land this commit before I have to handle a bunch of merge conflicts. Thanks.

[annevk]

Those four commits look fine to me, but I'd kinda prefer if we used « » over prose-allocation of a List.