Skip to content

Conversation

@jmcarcell
Copy link
Contributor

@jmcarcell jmcarcell commented Jan 15, 2024

BEGINRELEASENOTES

  • Fix a warning about using namespace in headers and a few other warnings

ENDRELEASENOTES

These changes are not trivial since repositories like k4MarlinWrapper depending on Marlin will have to be updated too.

@jmcarcell jmcarcell changed the title Fix compiler warnings and change LCIO_LIBRARIES to LCIO::lcio Fix compiler warnings and change LCIO_LIBRARIES Sep 10, 2025
Copy link
Contributor

@tmadlener tmadlener left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect this will break pretty much all iLCSoft packages that use Marlin as this has been handled rather sloppily in the past.

Plus it will probably also break quite a few packages that we do not build within the stack.

ParseException() { /*no_op*/ ; }
public:
virtual ~ParseException() throw() { /*no_op*/; }
virtual ~ParseException() noexcept { /*no_op*/; }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
virtual ~ParseException() noexcept { /*no_op*/; }
virtual ~ParseException() noexcept = default;

And similar below?

@jmcarcell
Copy link
Contributor Author

Yes, this would be very painful, there are too many packages that don't build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants