Page 9 - Demo
P. 9
Interface to Maple%uf09f%uf09fRCPConsult2020-2025Page 9You need only to define a DEFFUNC number instead symbol %u2018?%u2019, for example 1. Do not alter fixed names MAPLE,StrurelToMapleand MapleInterface.If your symbolic expressions contain definition of at least one FLIM,after parsing the expression above will be transformed toDEFFUNC(1,MAPLE,StrurelToMaple)(p1,p2){Maple Common Interface}=MapleInterfaceTo use this DEFFUNChaving two arguments (p1,p2)in symbolic expressions youhaveto call it by its keyword FUNCwith specific values for (p1,p2). The first argumentp1 is a text string and the second argument p2 defines a switch which can have only thevalues: 0 or 1. For case0 the abovetext string is thename of an external script filewithout extension%u2019.mpl%u2019written using rules as describedin 6.For case 1it is a direct expression written in Maplelanguage, see 7.FLIM(21)=FUNC(1)(\or FLIM(22)=FUNC(1)(\Additionally, a special formfor case1can be used. If the firstcharacter in the string of a function argumentisthe symbol %u2019%%u2019, the entire expression will be interpreted as a sequence of statement(s)for the Mapleengine, separated by %u2019;%u2019.In this case no value is computed,and the return value is an empty state like %u00d8. This possibility allows to provide pre-settingsand/or engine specific pre-calculation around acall ofthestate function or similar function in STRUREL. For example,with DEFFUNC(1)as defined above:DEFFUNC(41)=FUNC(1)(\DEFFUNC(42)=FUNC(1)(\DEFFUNC(43)=FUNC(1)(\DEFFUNC(44)=FUNC(41)+FUNC(42)+FUNC(43)Evaluation of DEFFUNC(44)looks like:This feature requires sufficient experience in the handling oftheinterface enginetoMaple. Please take a care when using it!