Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #87

Closed
Open
Created Apr 10, 2017 by snuverink_j@snuverink_jDeveloper

OPAL master does not compile with NOCPLUSPLUS11_NULLPTR=ON

OPAL master does not compile (gcc 4.8.5) with build option NOCPLUSPLUS11_NULLPTR=ON with the following error:

src/Classic/AbsBeamline/RFCavity.cpp:152:27: error: call of overloaded ‘unique_ptr(NULL)’ is ambiguous frequency_td_m(nullptr)

This comes from:

RNormal_m(nullptr)

which is defined as

std::unique_ptr<double[]> RNormal_m;

With NOCPLUSPLUS11_NULLPTR this is translated to RNormal_m(NULL), for which multiple constructors are possible.

Since there is already quite a bit of C++11 in OPAL, instead of fixing I would suggest (but with caution as I don't know the reason for the build option) to remove the NOCPLUSPLUS11_NULLPTR (and perhaps also the similar NOCPLUSPLUS11_FOREACH).

Assignee
Assign to
OPAL 1.9.x
Milestone
OPAL 1.9.x
Assign milestone
Time tracking