Rename ENDL with TBB_ENDL to reduce the likehood of conflicts ...

[martin-marinov77]

... with application source code.

Description

As per the title, ENDL is renamed to TBB_ENDL. ENDL is a very general macro name and conflicted in our source code with a symbol from another library.

Fixes # - issue number(s) if exists

• - git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details)

Type of change

Choose one or multiple, leave empty if none of the other choices apply

Add a respective label(s) to PR if you have permissions

• bug fix - change that fixes an issue
• new feature - change that adds functionality
• tests - change in tests
• infrastructure - change in infrastructure and CI
• documentation - documentation update

Tests

• added - required for new features and some bug fixes
• not needed

Documentation

• updated in # - add PR number
• needs to be updated
• not needed

Breaks backward compatibility

• Yes
• No
• Unknown

Notify the following users

List users with @ to send notifications

Other information

[isaevil]

LGTM. Just curious, what does "ENDL" expand into in your application code then?

[martin-marinov77]

LGTM. Just curious, what does "ENDL" expand into in your application code then?

Thank you for the review.

We use have a library with a the following definition (inside a namespace):
const char ENDL = '\n';

The TBB ENDL marco definition is causing compilation errors when the TBB macro is expanded in place of ENDL.