[m-rev.] splitting io.m

Peter Wang novalazy at gmail.com
Tue Aug 18 12:25:48 AEST 2015

On Tue, 18 Aug 2015 11:39:07 +1000, Mark Brown <mark at mercurylang.org> wrote:
> On Mon, Aug 17, 2015 at 4:43 PM, Peter Wang <novalazy at gmail.com> wrote:
> > Would there be any opposition to splitting io.m into multiple modules,
> > while maintaining the interface?
> May I ask what problem(s) you are trying to solve? Not that I oppose
> the idea, but if this point is clearer then it will be much easier to
> evaluate the various suggestions.
> For example:
> (a) It's hard to scroll through the documentation on the web page
> because it scrolls too fast.
> (b) It's hard to edit the body of the module because mtags doesn't do
> a great job of foreign code.
> (c) It's hard for new users to get an overall picture of what the module does.

It's hard to edit the body of the module.

I was trying to fix some aspects of error handling, which covers many
predicates across multiple backends.  I kept losing my place and my
progress, by having to page over many unrelated (for the current task)
procedures and foreign code blocks.  Nothing that couldn't be overcome,
but smaller submodules would make it easier.


More information about the reviews mailing list