[m-dev.] for review: MLDS back-end stuff

[Warwick Harvey]

Tyson wrote:
> On 04-Aug-1999, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > +<ul>
> > +<li> 1. parsing (source files -> HLDS)
> > +<li> 2. semantic analysis and error checking (HLDS -> annotated HLDS)
> > +<li> 3. high-level transformations (annotated HLDS -> annotated HLDS)
> > +<li> 4. code generation (annotated HLDS -> target representation)
> > +<li> 5. low-level optimizations
> > +     (target representation -> target representation)
> > +<li> 6. output code (target representation -> target code)
> > +</ul>
> 
> You should probably use the HTML ordered list <OR> tag if you want this.

(and a similar comment later when the structure is refined for multiple 
back-ends.)

Just out of interest: if one uses automatic numbering here, how does one 
then ensure that it matches up with the later section headings?

E.g.

> > +<h3> a. LLDS BACK-END </h3>
> >  
> > +<h4> 4a. Code generation. </h4>

Can this be done in HTML?

Warwick

--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------