[m-rev.] diff: updating programming style in samples

Zoltan Somogyi zoltan.somogyi at runbox.com
Wed Jul 7 05:28:07 AEST 2021

When I searched the samples for examples of parsing to recommend
in m-users, I found myself looking at code I would not want to recommend
to anyone. This diff goes some way towards fixing that.

BTW, it would have been nice if the samples had test cases that were
exercised during bootcheck. The biggest sample program, muz, has
a simple test, but it cannot have ever been passed, because muz is
missing a module (ironically named repository.m), which, looking at the
backup snapshot I took of the CVS repository when I left UoM, seems
to have been never added to CVS.

Can we add a policy that any *new* programs added to samples
have to be tested by bootcheck?

Similarly, should we change bootcheck so that -e (checking the extras)
is the default?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.samples
Type: application/octet-stream
Size: 2098 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20210707/27072a55/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.samples
Type: application/octet-stream
Size: 382154 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20210707/27072a55/attachment-0003.obj>

More information about the reviews mailing list