Is it possible to make new ecap version with standard <memory> instead <tr1/memory>?

Asked by Yuri on 2018-01-31

Is it possible to make new ecap version with standard <memory> instead <tr1/memory>?

Because of it is significantly long time part of STL. Yes, I know it is require to re-compile adapters.

However, is it possible?

Question information

Language:
English Edit question
Status:
Answered
For:
eCAP Edit question
Assignee:
No assignee Edit question
Last query:
2018-01-31
Last reply:
2018-02-01
Alex Rousskov (rousskov) said : #1

> Is it possible to make new ecap version with standard <memory> instead <tr1/memory>?

Yes, of course. This change is being tracked at https://bugs.launchpad.net/ecap/+bug/1595488

> I know it is require to re-compile adapters.

Yes, and the host application. Other problems include:

1. Adapters and host applications will need to switch to C++11. We cannot support both interfaces in the same libecap version. Switching to C++11 will require _more_ than just recompilation in many cases. The build system parameters and the code itself will need to be changed to keep compilers happy.

2. If we are have to change the library version and, likely, force many folks to adjust their code, it would be great to add missing libecap API calls and fix the broken ones. Deciding what to add/fix requires time.

To avoid misunderstanding, I do believe that this change should be done, and I do understand that this change should be done soon. Help, especially with #2, is welcomed.

Can you help with this problem?

Provide an answer of your own, or ask Yuri for more information if necessary.

To post a message you must log in.