On 25 Nov 2015 7:06 pm, "John Wiegley" wrote: > > The code: (funcall) > > Interpreted: Raises an error: eval: Wrong number of arguments: funcall, 0 > > Byte-compilation: No warnings or errors printed. This is a bug then (probably in the advertised-calling-convention of funcall). Functions called with the wrong number of arguments are usually reported as warnings by the byte-compiler.