chiark / gitweb /
Import upstream version 5.3.
[mup] / mup / docs / uguide / debug.html
CommitLineData
69695f33
MW
1<HTML>
2<HEAD><TITLE>
3Mup debugging
4</TITLE></HEAD>
5<BODY>
6<P>
7&nbsp;&nbsp;&nbsp;<A HREF="param.html">&lt;-- previous page</A>
8
9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="adjust.html">next page --&gt;</A>
10</P>
11
12<H2>
13Debugging
14</H2>
15<P>
16Since Mup requires its input in a fairly strict format, when a song is put
17in, it may contain &quot;typos.&quot; Generally, the error messages that Mup prints
18will give you an idea of what is wrong. However, sometimes Mup is not able
19to recognize that something is wrong until some distance beyond the actual
20error. If you can't find anything wrong with the line that Mup lists as
21being in error, try looking at the end of the previous line, or even earlier
22lines. Some of the most common problems are missing semicolons and missing
23quotes. Missing quote marks tend to be especially confusing to Mup, and may
24cause many error messages, even though there is only one problem.
25Another common problem that may cause a very large number of error messages is
26forgetting to state &quot;music&quot; to enter music context.
27</P>
28<P>
29Often listening to
30<A HREF="midi.html">MIDI output</A>
31is much more effective at spotting things like wrong notes and missing
32accidentals than trying to find them by eye.
33</P>
34<HR><P>
35&nbsp;&nbsp;&nbsp;<A HREF="param.html">&lt;-- previous page</A>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="index.html">Table of Contents</A>&nbsp;&nbsp;&nbsp;&nbsp;<A HREF="adjust.html">next page --&gt;</A>
36</P>
37</BODY></HTML>