|Title||there is no human-helpful map of MPS files|
|Assigned user||Gareth Rees|
|Description||there is no human-helpful map of MPS files|
This is a big topic; here's a start, looking at source files:
A new user is presented with over 200 cryptically 8.3-named source files.
It is hard to:
- discern the purpose of each file;
- discern the grouping of files;
- notice the more important files (in an alphabetical listing they get
swamped by big groups such as event*.*)
- list files such that ./design/XX is collated near to ./code/XX.c
|Analysis||An easy first step is to make and maintain a web-page. |
For each MPS file it has:
- a link to the file;
- a pithy description of the file's purpose.
These elements are grouped semantically.
Just do ./design/* and ./code/* to start with.
Done pro-tem in:
See also job000543.
|Created by||Richard Kistruck|
|Created on||2005-03-21 20:25:39|
|Last modified by||Gareth Rees|
|Last modified on||2016-03-06 18:36:47|
|History||2005-03-21 RHSK create|
2005-04-04 RHSK add depot-name of my quick-hack map (in user/rhsk/mps)
2013-03-19 GDR Assigned to GDR.
|189679||closed||2016-03-06 18:36:47||Gareth Rees||Index to MPS source code.|
|150720||open||2005-03-21 20:55:12||Richard Kistruck||Move and rename mps-file-map.html,
and the source files used to generate it.
All these are just in user/rhsk/mps for now.