[m-dev.] for review: The .NET MSIL backend.

[Fergus Henderson]

On 13-Oct-2000, Tyson Dowd <trd at cs.mu.OZ.AU> wrote:
> On 11-Oct-2000, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > On 22-Sep-2000, Tyson Dowd <trd at cs.mu.OZ.AU> wrote:
> > > diff -u -r1.290 options.m
> > > @@ -2096,7 +2100,10 @@
> > > +		"--target-debug",
> > > +		"\tEnable debugging of the generated target code."
> > 
> > The option should be documented in doc/user_guide.texi too.
> > 
> > Probably the best place to document this is just before --low-level-debug,
> > rather than there.
> > 
> > It seems odd to document both --c-debug and --target-debug without
> > saying that they are the same.  I think it would be better to document
> > them together:
> > 
> > 		"--c-debug",
> > 		"--target-debug",
> > 		"\tEnable debugging of the generated target code."
> > 		"\tIf the target language is C, this has the same effect as",
> > 		"\t`--cflags ""-g"" --link-flags ""--no-strip""'.)",
> > 		"\tIf the target language is IL, this causes the compiler to",
> > 		"\tpass `/debug' to the IL assembler.)",
> 
> I didn't do this mainly because I didn't want to promise that --c-debug
> would do the same as --target-debug.  

OK, how about documenting --target-debug as follows?

 		"--target-debug",
 		"\tEnable debugging of the generated target code."
 		"\tIf the target language is C, this has the same effect as",
 		"`--c-debug' (see below).",
 		"\tIf the target language is IL, this causes the compiler to",
 		"\tpass `/debug' to the IL assembler.)",

That would make the relationship between the two options clearer.

(BTW, don't forget my other two points:
- The option should be documented in doc/user_guide.texi too.
- Probably the best place to document --target-debug is just
  before --low-level-debug.)

> --c-debug will debug C code, but perhaps it should do this with any C
> code generated (perhaps the target is IL but the foreign code is in C
> and you want to do C debugging?).

Yes, actually it sounds like it would be a good idea to separate the
two options, and to add code in handle_options of the form

	( { Target = c } ->
		option_implies(target_debug, c_debug)
	;	
		[]
	).

However, that can be a separate change; for now, an XXX comment would
be enough...

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------