Known bugs


Anyflo is not a commercial product, but my tool. It is very often changed without guarantee of compatibility with previous versions.
There are many bugs still no corrected or emerged as a result of the correction of other bugs.
Any combination of any number of commands being legal, their number is potentially infinite, all have not been tested, some are to implement, to debug other ...

The interpreter
The graphic
Devices
Helps and demos

















































The interpreter

Parenthesizings
Brackets and braces
Error detection
Memory leak
Globl
Various

Parenthesizings

Some expressions are interpreted wrong, it is generally sufficient to parents on.
As follows:
if(ax!=Ax[2] || ay!=Ay[2])
Must be replaced by:
if((ax!=Ax[2]) || (ay!=Ay[2]))

if(w[3]>0)
Must be replaced by:
if((w[3]>0))

if(n>4 && w[3]=="=")
Must be replaced by:
if(n>4 && (w[3])=="=")

In the same way:
if(++x<5)
Must be replaced by:
if((++x)<5)

Brackets and braces

Some scriptures are misinterpreted:
v[0] += 1; Must be replaced by: v[0] = v[0] + 1;

In the same way v{0} += 1,2,3; Must be replaced by: v{0} = v{0} + (1,2,3);

x[0,y[2]]; Must be replaced by; par x[0,(y[2])];
nn=Nom{i},".wav"; Must be replaced by nn=(Nom{i}),".wav";

a[b[i]];
Must be written:
a[(b[i])];

if(a[i]!=b);
Must be written:
a[(a[i])!=b];

Error detection

The name of the function where the error occurred is correct, but the number of the line may be incorrect.
If an error is detected during a read func, read func, edit func gives a list of names compiled functions well, the error is probably produced in the following the last listed.

Memory leak

There is still no release some mallocs may give rise to a saturation of the virtual memory use interaction time(tmax) to restart the program after tmax images (eg tmax = 90000 sets a tempo of about 1 h).

Global

Type variables global are not yet taken into account.

Various

ini func;
attach_view();

OK, but:
ini func;attach_view();
error...

for(i=1,5);
product error, but not:

for(i=1,5)NIL;

The graphic

Image processing can malfunction mode interpreter prefer interaction mode.

Devices

Le type UDP may produce errors.

Helps and demos

I tried to keep update "helps", the "demos", " the *. Func", the "exemple_ *. Fon", the "test *. Fon", etc., but many are still errors in these files.
Some graphics demos (as demo1_displ.func can not turn on a screen dimensions (1024.768) at least (on a smaller screen menus are not displayed in their entirety).