Hi Jürgen,
apl_command gives the exact same Tokenizer error as does apl_exec with )copy
with the only difference being that apl_command does not output the usually apl
command result output without assigning it to a variable and outputing it (or
writeln/printf/printf directly)
)clear CLEAR WS
)copy DUMPED 2022-07-29 13:15:37 (GMT-6)
apl_exec(')copy /caf/rseq.seq');
DUMPED 2022-07-29 13:15:37 (GMT-6)
apl_command(')copy /caf/rseq.seq');
[no output]
var b : ansistring;
b := apl_command(')copy /caf/rseq.seq');
writeln(b);
DUMPED 2022-07-29 13:15:37 (GMT-6)
there is no difference between apl_command and apl_exec when working with
)clear )copy )si )wsid etc in my code besides what is mentioned above
i tested the exact same code with python3 libapl and c libapl and get the exact
same complete behaviors and times as with fpc libapl in all respects especially
with the )copy behavior copying a ∇fns header)
(all require ⎕pw←0 in UCS_string.cc but python3 and c not requiring ⎕pw←80 in
the main pgm before executing a )copy like fpc does)
---
if you look at the times below - libapl is the way i need to do my apl coding
when i run your code (a,¨b)⌷¨⊂ar 1 time i get the following times in the
stated various apl environments
in fns in apl ws 111 msec
in an apl executable script 110 msec
fpc executing apl script 110 msec
libapl c 59 msec
libapl python3 60 msec
libapl fpc 59 msec
enztec
On Fri, 29 Jul 2022 20:18:59 +0200
Dr. Jürgen Sauermann <m...@xn--jrgen-sauermann-zvb.de> wrote:
> Hi enztec,
>
> as I explained earlier, you must not use *apl_exec()* with APL commands
> (such as*)COPY* ).
> Use *apl_command()* instead, e.g.
>
> *apl_command(')copy aa.apl');*
>
> Best Regards,
> Jürgen
>
> On 7/29/22 6:51 PM, enz...@gmx.com wrote:
> > Hi,
> >
> > what about this error from :
> >
> > apl_exec(')copy aa.apl');
> > where aa.apl contains the fns header ∇prep (the closing ∇ seems to not
> > cause any problems at this point)
> >
> > SYNTAX ERROR+
> > Tokenizer: No token for Unicode U+2207 (∇)
> > Input: prep
> >
> > enztec
> >
>
