octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc7 build error with recent tip


From: Daniel J Sebald
Subject: Re: gcc7 build error with recent tip
Date: Sat, 24 Jun 2017 13:58:43 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0

On 06/24/2017 01:12 PM, John W. Eaton wrote:
On 06/24/2017 12:39 PM, Daniel J Sebald wrote:

Hmm, is it possible to do some kind of typedef ahead of the template
definition, a technique that often solves the same kind of referencing
issues with C?

I couldn't find one that worked.  I checked in the following changeset
to get around the problem for now:

http://hg.savannah.gnu.org/hgweb/octave/rev/a94ed7424d63

I suppose, but the new template code isn't being used for any compilers now with the "#if 0". Is using template qualifier in a nested way unconventional? Probably not. Some alternatives would be:

1) If GCC7 developers decide this is a compiler bug, use the new template syntax without the two separate implementations, and place a restriction in "configure" disabling the use of GCC7 prior to the version associated with the fix.

2) Perhaps some alternate syntax, given the GCC7 compiler must have some means of doing such a construct. Dimitri, in your bug report, please ask if there is some alternate syntax for achieving the nested construct that GCC developers know works for GCC7.

Dan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]