1.1 --- a/docs/wiki/Downloads Tue Dec 13 17:04:42 2022 +0100
1.2 +++ b/docs/wiki/Downloads Tue Dec 13 17:05:11 2022 +0100
1.3 @@ -14,7 +14,7 @@
1.4
1.5 The source code repository is located at the following location:
1.6
1.7 -https://hg.boddie.org.uk/L4Re/idl4re
1.8 +[[https://hg.boddie.org.uk/L4Re/idl4re]]
1.9
1.10 The repository can be cloned using [[https://www.mercurial-scm.org/|Mercurial]]
1.11 as follows:
1.12 @@ -30,51 +30,3 @@
1.13 attempts are made to avoid such situations. Therefore, you should choose to
1.14 update with care and be prepared to switch to a "known working" revision if
1.15 necessary.
1.16 -
1.17 -== Releases ==
1.18 -
1.19 -{{{#!wiki tip
1.20 -See below for downloadable archives.
1.21 -}}}
1.22 -
1.23 -Releases are tagged in the repository. The currently-supported releases are
1.24 -listed here for convenience:
1.25 -
1.26 -{{{#!table
1.27 -'''Release''' || '''Details'''
1.28 -==
1.29 -0.1 || [[https://hg.boddie.org.uk/idl4re/rev/rel-0-1|changeset]]
1.30 - .. [[https://hg.boddie.org.uk/idl4re/file/rel-0-1|files]]
1.31 -}}}
1.32 -
1.33 -Details of changes introduced in each new release can be found in the
1.34 -[[../Changelog|changelog]].
1.35 -
1.36 -=== Archives ===
1.37 -
1.38 -Downloadable archives are provided below. Choose "get" to download the
1.39 -appropriate file.
1.40 -
1.41 -<<AttachList(,application/x-tar)>>
1.42 -<<AttachList(,application/x-bzip2)>>
1.43 -
1.44 -=== Signatures ===
1.45 -
1.46 -Downloadable archive signatures are provided below. Choose "get" to download
1.47 -the appropriate file.
1.48 -
1.49 -<<AttachList(,text/plain)>>
1.50 -<<AttachList(,application/pgp-signature)>>
1.51 -
1.52 -To verify an archive, download the archive and accompanying signature file to
1.53 -the same location and then run a command of the following form:
1.54 -
1.55 -{{{
1.56 -gpg --verify <signature file> <archive file>
1.57 -}}}
1.58 -
1.59 -For example:
1.60 -
1.61 -{{{
1.62 -gpg --verify idl4re-0.1.tar.bz2.asc idl4re-0.1.tar.bz2
1.63 -}}}
2.1 --- a/docs/wiki/Roadmap Tue Dec 13 17:04:42 2022 +0100
2.2 +++ b/docs/wiki/Roadmap Tue Dec 13 17:05:11 2022 +0100
2.3 @@ -29,26 +29,6 @@
2.4 parsing toolkit. [[http://www.dabeaz.com/ply/|PLY]] would be a potentially
2.5 usable candidate.
2.6
2.7 -== More Integrated Compound Interfaces ==
2.8 -
2.9 -Having compound interfaces supported at the command level helps to avoid
2.10 -difficult issues introduced by supporting them at the language level, but it
2.11 -would arguably be more elegant to support them using a form of interface
2.12 -inheritance, even though this introduces some awkward issues of its own.
2.13 -
2.14 -== Consolidation of Output Files ==
2.15 -
2.16 -Currently, the `_interface.h`, `_interfaces.h` and `_interface_type.h` files
2.17 -generated for compound interfaces are all created because individual
2.18 -interface details are written incrementally to different output constructs,
2.19 -and such constructs are most easily maintained using distinct output streams.
2.20 -However, the details of the individual interfaces are readily available from
2.21 -the processed command options.
2.22 -
2.23 -Thus, interface type information (`_interface.h` and `_interface_type.h`)
2.24 -could be written out completely without involving the individual interface
2.25 -code generation in the production of these files.
2.26 -
2.27 == More Abstract Type Handling ==
2.28
2.29 Types employed in interface descriptions are currently mostly propagated to