# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1670947511 -3600
# Node ID 48e832898a02ecc5ec51b287d50c972acf43d346
# Parent  bb05d5c2d7364fde43ae3b1556563259cf4e55df# Parent  c24e354011ac85bb722de3caef677d88358ac414
Merged concurrent changes.

diff -r bb05d5c2d736 -r 48e832898a02 docs/wiki/Downloads
--- a/docs/wiki/Downloads	Tue Dec 13 17:04:42 2022 +0100
+++ b/docs/wiki/Downloads	Tue Dec 13 17:05:11 2022 +0100
@@ -14,7 +14,7 @@
 
 The source code repository is located at the following location:
 
-https://hg.boddie.org.uk/L4Re/idl4re
+[[https://hg.boddie.org.uk/L4Re/idl4re]]
 
 The repository can be cloned using [[https://www.mercurial-scm.org/|Mercurial]]
 as follows:
@@ -30,51 +30,3 @@
 attempts are made to avoid such situations. Therefore, you should choose to
 update with care and be prepared to switch to a "known working" revision if
 necessary.
-
-== Releases ==
-
-{{{#!wiki tip
-See below for downloadable archives.
-}}}
-
-Releases are tagged in the repository. The currently-supported releases are
-listed here for convenience:
-
-{{{#!table
-'''Release''' || '''Details'''
-==
-0.1 || [[https://hg.boddie.org.uk/idl4re/rev/rel-0-1|changeset]]
-    .. [[https://hg.boddie.org.uk/idl4re/file/rel-0-1|files]]
-}}}
-
-Details of changes introduced in each new release can be found in the
-[[../Changelog|changelog]].
-
-=== Archives ===
-
-Downloadable archives are provided below. Choose "get" to download the
-appropriate file.
-
-<<AttachList(,application/x-tar)>>
-<<AttachList(,application/x-bzip2)>>
-
-=== Signatures ===
-
-Downloadable archive signatures are provided below. Choose "get" to download
-the appropriate file.
-
-<<AttachList(,text/plain)>>
-<<AttachList(,application/pgp-signature)>>
-
-To verify an archive, download the archive and accompanying signature file to
-the same location and then run a command of the following form:
-
-{{{
-gpg --verify <signature file> <archive file>
-}}}
-
-For example:
-
-{{{
-gpg --verify idl4re-0.1.tar.bz2.asc idl4re-0.1.tar.bz2
-}}}
diff -r bb05d5c2d736 -r 48e832898a02 docs/wiki/Roadmap
--- a/docs/wiki/Roadmap	Tue Dec 13 17:04:42 2022 +0100
+++ b/docs/wiki/Roadmap	Tue Dec 13 17:05:11 2022 +0100
@@ -29,26 +29,6 @@
 parsing toolkit. [[http://www.dabeaz.com/ply/|PLY]] would be a potentially
 usable candidate.
 
-== More Integrated Compound Interfaces ==
-
-Having compound interfaces supported at the command level helps to avoid
-difficult issues introduced by supporting them at the language level, but it
-would arguably be more elegant to support them using a form of interface
-inheritance, even though this introduces some awkward issues of its own.
-
-== Consolidation of Output Files ==
-
-Currently, the `_interface.h`, `_interfaces.h` and `_interface_type.h` files
-generated for compound interfaces are all created because individual
-interface details are written incrementally to different output constructs,
-and such constructs are most easily maintained using distinct output streams.
-However, the details of the individual interfaces are readily available from
-the processed command options.
-
-Thus, interface type information (`_interface.h` and `_interface_type.h`)
-could be written out completely without involving the individual interface
-code generation in the production of these files.
-
 == More Abstract Type Handling ==
 
 Types employed in interface descriptions are currently mostly propagated to