Eigen & GCC 5 : class std::binder2nd is deprecated -

-

i restarted working on project has been on hold few months. last time compiled it working fine, without error nor warning. yet when tried compile earlier today got warning

attention : ‘template<class _operation> class std::binder2nd’ deprecated [-wdeprecated-declarations]

this warning literally appears hundreds of time when including eigen/geometry, use on project

in file included [...]/include/eigen/src/core/arraybase.h:109:0,                  [...]/include/eigen/core:350,                  [...]/include/eigen/geometry:4,                  [...]/include/[myproject]/types.hh:8,                  [...]/include/[myproject]/voronoi.hh:8

since haven't updated eigen (is used 3.2.4 still last update today). however, since last time compiled it, gcc has been updated 5.1.0 (i'm using archlinux)

question:

  • is there issue gcc 5.1.0 telling me std::binder2nd deprecated
  • should eigen updated ?
  • how can silent specific warning without loosing verbosity of build ?

answer

i appreas std::bind2nd deprecated , a commit has been done solve in eigen. commit not yet merged master branch :/ (and doesn't solve issue std::bind2nd still present in eigen's code)

bottom line is: eigen's last stable version deprecated

  • is there issue gcc 5.1.0 telling me std::binder2nd deprecated

no, c++ standard says it's deprecated in c++11, if compile in c++11 mode supposed deprecated.

  • should eigen updated ?

yes. if wants c++17 compatible, std::bind2nd doesn't exist post-c++14 @ all.

  • how can silent specific warning without loosing verbosity of build ?

suppress warning. either compile -wno-deprecated-declarations on command-line or in source when including eigen headers:

#pragma gcc diagnostic push #pragma gcc diagnostic ignored "-wdeprecated-declarations" #include <eigen/whatever.h> #pragma gcc diagnostic pop

or, other answer says, tell gcc treat eigen headers system headers, happens automatically if in /usr/include, or included -isystem, or included header does:

#pragma gcc system_header #include <eigen/whatever.h>

Comments

Post a Comment

Popular posts from this blog

Java 3D LWJGL collision -

-
i making 3d java game lwjgl library, , wondering how add collision detection, player not go through models. i using obj models. here objloader class, loads models: package renderengine; import java.io.bufferedreader; import java.io.file; import java.io.filenotfoundexception; import java.io.filereader; import java.util.arraylist; import java.util.list; import models.rawmodel; import org.lwjgl.util.vector.vector2f; import org.lwjgl.util.vector.vector3f; public class objloader { public static rawmodel loadobjmodel(string filename, loader loader){ filereader fr = null; try { fr = new filereader(new file("res/"+filename+".obj")); } catch (filenotfoundexception e) { system.err.println("couldn't load file!"); e.printstacktrace(); } bufferedreader reader = new bufferedreader(fr); string line; list<vector3f> vertices = new arraylist<vector3f...
Read more

spring - SubProtocolWebSocketHandler - No handlers -

-
i have ugly error during deploying spring app on jboss. 18:11:16,025 error [org.apache.catalina.core.containerbase.[jboss.web].[default-host].[/consumer]] (msc service thread 1-7) exception sending context initialized event listener instance of class org.springframework.web.context.contextloaderlistener: org.springframework.context.applicationcontextexception: failed start bean 'subprotocolwebsockethandler'; nested exception java.lang.illegalargumentexception: no handlers @ org.springframework.context.support.defaultlifecycleprocessor.dostart(defaultlifecycleprocessor.java:176) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.springframework.context.support.defaultlifecycleprocessor.access$200(defaultlifecycleprocessor.java:51) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.springframework.context.support.defaultlifecycleprocessor$lifecyclegroup.start(defaultlifecycleprocessor.java:346) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.s...
Read more

methods - python can't use function in submodule -

-
my folder structure this: pythonstuff/ program.py modulea/ __init__.py foo.py bar.py here's code bar.py : def hello(): print("hello, world!") here's code program.py : #!/usr/bin/env python3 modulea import bar bar.hello() i run $ python3 program.py somehow error: file "program.py", line 3, in <module> bar.hello() attributeerror: 'module' object has no attribute 'hello' edit: __init__.py file empty. edit2: after trying realized had bar.py in root directory contained hello() method. bar.py in modulea/ directory empty. add it import os __all__ = [] module in os.listdir(os.path.dirname(__file__)): if module != '__init__.py' , module[-3:] == '.py': __all__.append(module[:-3]) the init .py files required make python treat directories containing packages; done prevent directories common name, such string, unintentionally hiding v...
Read more