[m-dev.] diff: fix tests in hard_coded for MSVC
Peter Ross
peter.ross at miscrit.be
Wed Feb 14 20:14:50 AEDT 2001
On Wed, Feb 14, 2001 at 09:19:06AM +1100, Simon Taylor wrote:
> On Tue, Feb 13, 2001 at 04:58:17PM +0100, Peter Ross wrote:
> > Estimated hours taken: 8
> >
> > Adapt the tests in the hard_coded directory so that the version of the
> > Mercury compiler built with MSVC passes them in the hlc.gc grade.
>
> > tests/hard_coded/Mmakefile:
> > Remove test_bitset and add bitset.
> >
> > tests/hard_coded/bitset.exp:
> > tests/hard_coded/bitset.m:
> > tests/hard_coded/bitset_tester.m:
> > tests/hard_coded/test_bitset.exp:
> > tests/hard_coded/test_bitset.m:
> > Move this test into one test case because mmake falls over with
> > unable to make `std_util.m^M', plus there is no reason to have this
> > case spread over two files.
> >
> > tests/hard_coded/exceptions/test_exceptions_func.m:
> > Remove the uneeded import of std_util, this avoids the
> > `std_util.m^M' problem mentioned in the previous test case.
>
> Any idea what's causing this problem?
>
> The reason for having test_bitset.m and bitset_tester.m as separate
> files is that it is useful to be able to use bitset_tester.m as a
> replacement for sparse_bitset.m to debug problems in sparse_bitset.m.
>
It is obviously something to do with the fact that having an MSVC
version of mercury compiler, but the cygwin tools as the build
architecture can lead to files being produced in various different
formats. I however cannot work out where this particular ^M is coming
from and why it only a problem with std_util.
Pete
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions: mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------
More information about the developers
mailing list