Re: Problem compiling sparse-xdiv.cc (typename)

[Michael Goffioul]

On Sat, May 9, 2009 at 4:20 PM, Jaroslav Hajek <address@hidden> wrote:
> However, the code seems valid to me. I think that typename always
> applies to the following qualified dependent name, regardless of any
> operators following. So I suspect it's a MSVC++ bug. I think our
> current (kind of unofficial) policy is that only the mainstream gcc
> version is worth putting workarounds into Octave code itself (if the
> code is otherwise OK).

Personally, I find that policy unfortunate, especially when you can
get the same result with something that could work on more compilers.
But I'm not the one who decides.

> So I suggest you keep a compatibility patch for
> MSVC++ and report the bug. Maybe it's going to be fixed soon.
> Btw. I keep another workaround patch for Intel C++. I reported the bug
> in question to Intel 2 months ago, but no trace of a progress yet :(
> As you may have noticed, gcc 3 doesn't compile Octave either.

I find this a little unfortunate as well , as many (not so) older systems are
still running on gcc-3.

Michael.