{VERSION 2 3 "SUN SPARC SOLARIS" "2.3" }
{USTYLETAB {CSTYLE "Maple Input" -1 0 "Courier" 0 1 255 0 0 1 0 1 0 0 
1 0 0 0 0 }{CSTYLE "Hyperlink" -1 17 "" 0 1 0 128 128 1 0 0 1 0 0 0 0 
0 0 }{CSTYLE "" 0 21 "" 0 1 0 0 0 1 0 0 0 0 2 0 0 0 0 }{CSTYLE "Help H
eading" -1 26 "" 1 14 0 0 0 0 0 1 0 0 0 0 0 0 0 }{PSTYLE "Normal" -1 
0 1 {CSTYLE "" -1 -1 "" 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 }0 0 0 -1 -1 -1 
0 0 0 0 0 0 -1 0 }{PSTYLE "Text Output" -1 2 1 {CSTYLE "" -1 -1 "Couri
er" 1 10 0 0 255 1 0 0 0 0 0 1 3 0 0 }1 0 0 -1 -1 -1 0 0 0 0 0 0 -1 0 
}{PSTYLE "Heading 1" 0 3 1 {CSTYLE "" -1 -1 "" 1 18 0 0 0 0 0 1 0 0 0 
0 0 0 0 }1 0 0 0 6 6 0 0 0 0 0 0 -1 0 }{PSTYLE "Warning" 2 7 1 
{CSTYLE "" -1 -1 "" 0 1 0 0 255 1 0 0 0 0 0 0 1 0 0 }0 0 0 -1 -1 -1 0 
0 0 0 0 0 -1 0 }{PSTYLE "Error" 7 8 1 {CSTYLE "" -1 -1 "" 0 1 255 0 
255 1 0 0 0 0 0 0 0 0 0 }0 0 0 -1 -1 -1 0 0 0 0 0 0 -1 0 }}
{SECT 0 {SECT 0 {PARA 0 "" 0 "" {TEXT 26 13 "Syntax error:" }{TEXT -1 
18 "  ...  unexpected\n" }}{PARA 0 "" 0 "" {TEXT -1 266 "Maple's parse
r came to the point in your input where it has now put the cursor and \+
discovered an error: the thing it indicates is \"unexpected\" can not \+
occur here in a correct Maple statement.  However, the actual error mi
ght well be much earlier in the statement.  \n" }}{PARA 0 "" 0 "" 
{TEXT -1 69 "The most common cause of this error is unbalanced parenth
eses.  Each " }{MPLTEXT 0 21 1 "(" }{TEXT -1 2 ", " }{MPLTEXT 0 21 1 "
\{" }{TEXT -1 4 " or " }{MPLTEXT 0 21 1 "[" }{TEXT -1 23 " needs a cor
responding " }{MPLTEXT 0 21 1 ")" }{TEXT -1 2 ", " }{MPLTEXT 0 21 1 "
\}" }{TEXT -1 4 " or " }{MPLTEXT 0 21 1 "]" }{TEXT -1 31 " respectivel
y.   If there is a " }{MPLTEXT 0 21 1 "(" }{TEXT -1 18 " with no match
ing " }{MPLTEXT 0 21 1 ")" }{TEXT -1 72 " after it, you get a syntax e
rror at the end of your statement, or at a " }{MPLTEXT 0 21 1 "\}" }
{TEXT -1 4 " or " }{MPLTEXT 0 21 1 "]" }{TEXT -1 29 " that has no matc
h after the " }{MPLTEXT 0 21 1 "(" }{TEXT -1 17 ".  If there is a " }
{MPLTEXT 0 21 1 ")" }{TEXT -1 18 " with no matching " }{MPLTEXT 0 21 
1 "(" }{TEXT -1 43 " before it, you get a syntax error at that " }
{MPLTEXT 0 21 1 ")" }{TEXT -1 237 ".  If your expression is so complic
ated and has so many parentheses that it's hard to spot the error, you
 might try building it up in several steps rather than all at once.  T
his can also improve the readability and clarity of your work." }}
{PARA 0 "" 0 "" {TEXT -1 0 "" }}{PARA 0 "" 0 "" {TEXT -1 134 "You can \+
check your input line for syntax errors without attempting to execute \+
it by clicking the check-mark button on the context bar." }}}{SECT 0 
{PARA 3 "" 0 "" {TEXT 26 9 "Examples:" }}{EXCHG {PARA 0 "> " 0 "" 
{MPLTEXT 1 0 15 "[ f(a + b, c ];" }}{PARA 8 "" 1 "" {TEXT -1 28 "Synta
x error, `]` unexpected" }}}{EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 10 "
f(a + b));" }}{PARA 8 "" 1 "" {TEXT -1 28 "Syntax error, `)` unexpecte
d" }}}}{SECT 0 {PARA 0 "" 0 "" {TEXT 26 9 "See also:" }{TEXT -1 1 " " 
}{HYPERLNK 17 "context bar" 2 "worksheet,context" "" }}}{SECT 0 {PARA 
0 "" 0 "" {TEXT 26 22 "Maple Advisor Database" }{TEXT -1 17 "  R. Isra
el, 1997" }}}}{MARK "1 2 0 0" 10 }{VIEWOPTS 1 1 0 1 1 1803 }