Re: [Bug-apl] A few problems

[Dr . Jürgen Sauermann]

Hi,

thanks for reporting this. Could you please give an example for the gcc warnings> I am using
g++  4 .8.4 and I am not getting the warnings.

Thanks,
/// Jürgen

On 02/02/2019 06:38 PM, vvs wrote:

Hi all!

There are some (possibly minor) problems with current version of the
interpreter. This is all on Linux with gcc 8.2.1. The first problem
was introduced in latest SVN 1121: compilation now fails without
CXX_WERR=no, because of -Wclass-memaccess. Apparently gcc isn't happy
about using POSIX memory functions to access class members. This can
be either changed to C++ style operations or this warning could be
silenced by compiler pragma.

The second problem lies in the implementation of symbol scope. If
there is a function with the same name, assignment to variable will
fail with error message. But if the same assignment occurred in the
function definition it is accepted and brings havoc by infinite memory
allocation. For example:

∇A
[1] A←0∇

Assigning A←1 after that definition might make problems by eating all
of available memory. Obviously it should be rejected as in above case,
where function definition doesn't contain the same variable. Also, by
using the same name as a function argument the error is printed, but
the function becomes not erasable and only )CLEAR will get rid of it.

With best regards