[m-rev.] for review: grade compability tests in .h files

Paul Bone paul at bone.id.au
Mon Apr 11 15:44:59 AEST 2016


On Mon, Apr 11, 2016 at 12:34:38PM +1000, Zoltan Somogyi wrote:
> 
> I prefer the second option, because it allows the standalone programs
> in the grade_lib directory (some of which will eventually be user-visible)
> to be compiled in a different grade from the compiler itself. This means that
> e.g. if I want to rebuild one of those small programs in a debug grade,
> I don't have to wait for the rest of the system (including the Mercury
> standard library) to be rebuilt in that grade. (This is the reason
> why we use this technique for the deep profiling and slice directories.)
> The downside is small: it means using the installed standard library,
> so the grade library's code cannot build on a new standard library predicate
> in the workspace until that workspace has been installed.

Ah, that's why those files are built that way.

> 
> Does anyone object to this choice?
> 

Either option is fine with me.

> 
> Does anyone object to this plan, or have a better one?
> 

This makes sense to me.

-- 
Paul Bone


More information about the reviews mailing list