Re: Compilation problem with base64.c

[Ben Pfaff]

Micah Cowan <address@hidden> writes:

> It's a relatively recent addition to the C language, so the restrict
> keyword is #defined to nothing for C compilers that don't support it
> (doesn't apply to modern GCC, which has supported it for a while, but
> _only_ when running as a C compiler). 

G++ does support restricted pointers, but it requires them to be
tagged with __restrict or __restrict__, not restrict.
-- 
"The fact is, technical people are better off not looking at patents. If
 you don't know what they cover and where they are, you won't be knowingly
 infringing on them. If somebody sues you, you change the algorithm or you
 just hire a hit-man to whack the stupid git." --Linus Torvalds