[m-rev.] for review: split up term.m

Julien Fischer jfischer at opturion.com
Mon Feb 2 00:42:49 AEDT 2015


Hi Zoltan,

On Mon, 2 Feb 2015, Zoltan Somogyi wrote:

>> If any changes to the term module that break backwards compatibility
>> are delayed until just before we are ready to branch for the next
>> release then that's fine by me.
>
> Will you do the next release?

Either Paul or myself will.

> If yes, do you have an idea about when?

We need to finalise the GC upgrade before we can create a new release
branch.  Once that is done -- and I don't have an estimate for that --
we will create a new release branch almost immediately.

>> One comment concerning the diff: s/Rebame/Rename/
>
> Thanks for the catch.
>
> By the way, I *could* set up Mmakefile rules that will check all Mercury modules
> in each directory for spelling errors. That could catch such errors automatically
> when run. However, I don't think it would be a good idea to run those tests
> automatically, since they would require any new variable names to be listed
> in a file of words that *we* know to have correct spelling, but the spellchecker
> doesn't, and doing that e.g. on every bootcheck would be a nuisance. However,
> before e.g. a new release, it could come in handy. Any opinions?

It's probably not worth the effort, running a spell checker of the
library modules before a release doesn't take that long anyway.

Cheers,
Julien.



More information about the reviews mailing list