[m-rev.] for review: add --force-disable-trace compiler option

[Julien Fischer]

On Wed, 15 Jun 2005, Ian MacLarty wrote:

> Estimated hours taken: 1
> Branches: main
>
> Add a new compiler option --force-disable-tracing which forces tracing to be
> turned off even if compiling in a .debug or .decldebug grade.
> This is necessary so that the declarative debugger can be compiled with no
> tracing even in .debug or .decldebug grades.
> This allows the declarative debugger to use tail recursion, improves its
> performance and reduces the size of the installed browser library for
> .debug and .decldebug grades.
>
> This diff does not use the --force-disable-tracing option.  It is only added to
> the compiler.  A subsequenct diff will use the option to turn off tracing by
> default in the browser directory.
>
> The declarative debugger will still call traced code in the library,
> however, so this is not a general fix.
> A more general solution would be to link in a non-traced version of the
> library when compiling the declarative debugger, but that can be done later.
>
> compiler/handle_options.m:
> compiler/options.m:
> 	Add and handle the new option.  It overrides all other tracing
> 	options.
>
That's fine except that you haven't provided any documentation for
the new option; if it's a developer-only option you should still
document it but leave it commented out (in mmc --help and the user's
guide.)

Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------