[m-dev.] diff: fix tests in hard_coded for MSVC
Peter Ross
peter.ross at miscrit.be
Wed Feb 14 22:22:02 AEDT 2001
On Wed, Feb 14, 2001 at 03:18:39AM -0800, Ralph Becket wrote:
> >From Peter Ross on 14/02/2001 09:40:50
> > 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:
> > > > 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.
>
> I've had this problem before under Cygwin and it seems a tad spurious
> to me. Why is ^M an illegal character? Surely it's just whitespace?
>
That is what you would hope, but the filename reported is `std_util.m^M'
so it is obviously not being treated as whitespace.
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