contributing & bound-checks

[Giovanni Bajo]

S.Hockenhull wrote:

> and/or who do I tell about:
> #gcc.latest --version
> gcc.latest (GCC) 3.5.0 20040626 (experimental)
>
> #gcc.latest  -fmudflap -fbounds-checking -g -DDEBUG
> -I/root/3ddev/roadgen/rv3d/ -I/root/3ddev/roadgen/xtc/
> -I/root/3ddev/roadgen/xtc/teASCII/ -I/root/3ddev/roadgen/xtc/lib/
> -I/root/3ddev/roadgen/xtc/lib386/ -I/root/3ddev/roadgen/xtc/ide/  -c
> -o main.o main.cpp
> In file included from /root/3ddev/roadgen/xtc/lib/stack_ramlist.h:6,
>                  from /root/3ddev/roadgen/xtc/xtc.h:6,
>                  from /root/3ddev/roadgen/xtc/ide/config.h:5,
>                  from main.cpp:13:
> /root/3ddev/roadgen/xtc/lib/node.h: In member function `void
> Node2D<DERIVEDTYPE>::Unlink()':
> /root/3ddev/roadgen/xtc/lib/node.h:153: error: `next' was not
> declared in this scope
>
>
> node.h is just some double linked list and tree node templates
>
> (maybe I'm late in the news, as I said, takes a while to compile ;)

The usual way to report a bug is using Bugzilla (http://gcc.gnu.org/bugzilla)
after having read our guidelines for bug submissions
(http://gcc.gnu.org/bugs.html). Anyway, for this specific case, even without
looking at the code I would bet that it's just the usual two-stage name lookup
fallout. Check http://gcc.gnu.org/gcc-3.4/changes.html for more information.
-- 
Giovanni Bajo