{VERSION 3 0 "IBM INTEL NT" "3.0" } {USTYLETAB {CSTYLE "Maple Input" -1 0 "Courier" 0 1 255 0 0 1 0 1 0 0 1 0 0 0 0 }{CSTYLE "2D Math" -1 2 "Times" 0 1 0 0 0 0 0 0 2 0 0 0 0 0 0 }{CSTYLE "Hyperlink" -1 17 "" 0 1 0 128 128 1 0 0 1 0 0 0 0 0 0 } {CSTYLE "2D Output" 2 20 "" 0 1 0 0 255 1 0 0 0 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 Heading" -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 "Courier" 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 "Hea ding 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 }{PSTYLE "Diagnostic" 7 9 1 {CSTYLE "" -1 -1 "" 0 1 64 128 64 1 0 0 0 0 0 0 0 0 0 }0 0 0 -1 -1 -1 0 0 0 0 0 0 -1 0 }{PSTYLE "Maple Output" 0 11 1 {CSTYLE "" -1 -1 "" 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 }3 3 0 -1 -1 -1 0 0 0 0 0 0 -1 0 }} {SECT 0 {SECT 0 {PARA 0 "" 0 "" {TEXT 26 6 "Error:" }{TEXT -1 18 " inv alid arguments" }}{PARA 0 "" 0 "" {TEXT -1 383 "Many of Maple's comman ds and functions are very particular about the number, types and order of the arguments they are given, and will report an error if these ar e not correct.\n\nLook at the help for a function, in particular the \+ \"calling sequence\" and \"parameters\" sections, to see the correct f orms to use. Or imitate one of the examples that are given on the hel p page.\n\nUse the " }{MPLTEXT 0 21 9 "tracelast" }{TEXT -1 188 " com mand to see more about the error. In particular it will show what fun ctions were being called with what arguments when the error occurred. \+ In some cases it may be helpful to use the " }{MPLTEXT 0 21 4 "type" }{TEXT -1 4 " or " }{MPLTEXT 0 21 8 "whattype" }{TEXT -1 362 " command to check on the type of some argument.\n\nOne common way that these e rrors can occur is when you try to use a name as a symbolic variable, \+ but it turns out that the name has been assigned a value. This is the case in the second example below. If so, either use a different name that does not have a value or unassign the value if it is no longer n eeded." }}}{SECT 0 {PARA 3 "" 0 "" {TEXT 26 9 "Examples:" }}{EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 19 "limit([x,x^2],x=1);" }}{PARA 8 "" 1 "" {TEXT -1 35 "Error, (in limit) invalid arguments" }}}{EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 6 "p:= 5:" }}}{EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 16 "fsolve(p^2=2,p);" }}{PARA 8 "" 1 "" {TEXT -1 36 "Erro r, (in fsolve) invalid arguments" }}}{EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 10 "tracelast;" }}{PARA 9 "" 1 "" {TEXT -1 52 " fsolve ca lled with arguments: 25 = 2, 5\n #(fsolve):" }}{PARA 8 "" 1 "" {TEXT -1 36 "Error, (in fsolve) invalid arguments" }}{PARA 9 "" 1 "" {TEXT -1 122 " locals defined as: _X = _X, eqns = eqns, opt = opt, r = r, so l = sol, tvars = tvars, t1 = t1, s = s, t = t, eqns2 = eqns2" }}} {EXCHG {PARA 0 "> " 0 "" {MPLTEXT 1 0 12 "whattype(p);" }}{PARA 11 "" 1 "" {XPPMATH 20 "6#%(integerG" }}}}{SECT 0 {PARA 0 "" 0 "" {TEXT 26 9 "See also:" }{TEXT -1 1 " " }{HYPERLNK 17 "type" 2 "type" "" }{TEXT -1 2 ", " }{HYPERLNK 17 "whattype" 2 "whattype" "" }{TEXT -1 2 ", " } {HYPERLNK 17 "tracelast" 2 "tracelast" "" }}}{SECT 0 {PARA 0 "" 0 "" {TEXT 26 23 "Maple Advisor Database " }{TEXT -1 15 " R. Israel 1997" } }}{PARA 3 "" 0 "" {TEXT -1 0 "" }}{PARA 0 "" 0 "" {TEXT -1 0 "" }}} {MARK "0 1 6" 218 }{VIEWOPTS 1 1 0 1 1 1803 }