🚀 go-pugleaf

In article <9209050116.AA04670@skipsun.UUCP> skip@skipsun.UUCP (Skip Gilbrech) writes:
>				I would really appreciate (as would I'm
> quite sure many others) a command-line _option_ to totally disable
> built-in functions (and their prototypes).

I'd like builtins to have _default_ prototypes: `implicit declaration of
function BUILTIN' would give BUILTIN another type than int().  Gcc could
also check that any explicit or `implicit int()' declaration gives the
same call sequence as the built-in declaration - the program has a bug
otherwise.  Maybe -ansi -pedantic would warn about `conflicting types
for built-in function'.

This would still not accept `double memcpy(int, char *);' gracefully, but I
wouldn't trust a program which did that anyway.

An option to disable built-in functions would be nice in a few cases (ie
to use "debug" versions of the built-ins), but it would usually not be
necessary.


Hallvard