1.1 --- a/docs/wiki/Roadmap Sun Dec 11 23:57:07 2022 +0100
1.2 +++ b/docs/wiki/Roadmap Mon Dec 12 00:45:00 2022 +0100
1.3 @@ -29,26 +29,6 @@
1.4 parsing toolkit. [[http://www.dabeaz.com/ply/|PLY]] would be a potentially
1.5 usable candidate.
1.6
1.7 -== More Integrated Compound Interfaces ==
1.8 -
1.9 -Having compound interfaces supported at the command level helps to avoid
1.10 -difficult issues introduced by supporting them at the language level, but it
1.11 -would arguably be more elegant to support them using a form of interface
1.12 -inheritance, even though this introduces some awkward issues of its own.
1.13 -
1.14 -== Consolidation of Output Files ==
1.15 -
1.16 -Currently, the `_interface.h`, `_interfaces.h` and `_interface_type.h` files
1.17 -generated for compound interfaces are all created because individual
1.18 -interface details are written incrementally to different output constructs,
1.19 -and such constructs are most easily maintained using distinct output streams.
1.20 -However, the details of the individual interfaces are readily available from
1.21 -the processed command options.
1.22 -
1.23 -Thus, interface type information (`_interface.h` and `_interface_type.h`)
1.24 -could be written out completely without involving the individual interface
1.25 -code generation in the production of these files.
1.26 -
1.27 == More Abstract Type Handling ==
1.28
1.29 Types employed in interface descriptions are currently mostly propagated to