Probably not countable.
--- bittest(x:small,y:small) is wrong if y>31
--- x:small%y:small cannot use % in C because -2%3 would be wrong
--- || and && are not always fully short-circuiting if second argument is a block.
-- modifying loop index of vector does not work
Things that are poorly implemented:
----------------------------------
--- Array (vector, matrix) may be disconnected in the stack.
--- vector() and matrix() do not garbage collect.
--- Garbage collecting should always be done after a loop.
--- Code generated for "a=if(b,c,d)" constructs is ugly.
--- user-defined member functions should be inlined
--- local() variables are treated identically to my() variables. Thus the scope of local()
variable after function call are not the same in GP and in C.
Things that are not implemented:
--------------------------------
--- a[b,]+=c
--- issquare(4,&a[b,])
Discrepancy between gp2c and gp:
--------------------------------
--- =\n= is allowed by gp, but not by gp2c. Don't cry.
--- Spaces in middle of term like (a b==ab) are not allowed. Be sensible.
--- gp2c does not allow functions named local() to be called.
--- "error" output PARI errors, not user errors.
--- gp2c is generally more lenient than gp about syntax.
--- Do not catch misuse of GP 'global()' vars.
--- Use of small may lead to overflow problems.
--- return() can return 0 instead of nothing.
Generated by dwww version 1.15 on Fri May 24 06:58:37 CEST 2024.