interpret_block again

[Ralf Hemmecke]

I remember that I have added this function to FriCAS.

interpret_block(code) ==
$inclAssertions : local := []
$ncMsgList : local := []
$erMsgToss : local := false
$lastPos : local := $nopos
$EchoLines : local := false
st := MAKE_-STRING_-INPUT_-STREAM(code)
intloopInclude0(st, 'webspad, 0)

https://github.com/fricas/fricas/blob/master/src/interp/int-top.boot#L169

Honestly, I had no idea what to put as the second argument of
intloopInclude0(st, 'webspad, 0).

Now, looking a bit deeper and trying to understand the respective boot
code, it seems that this 'webspad parameter is not really used except in
cases where there is a problem then this parameter is used in an error
message indicating a filename.

Since interpret_block is never reading a file, I wonder if there is a
more appropriate way to call the functionality of
ntloopInclude0(st, 'webspad, 0) without using 'webspad.

The reason why I ask this is that I am currently working on a new way to
do the jfricas connection (which I hope will go into FriCAS 1.3.14) and
webspad.lisp will be gone, so I see no reason to keep the identifier
webspad anywhere in FriCAS code.
Of course, I could replace the 'webspad in interpret_block by 'jfricas,
but I think interpret_block is actually independent of jfricas.

Any suggestions?

Ralf

[Waldek Hebisch]

Maybe

ntloopInclude0(st, "interpret block", 0)

--
Waldek Hebisch