Closed seanm closed 10 months ago
I thought that most were in the private section of the classes, so renaming should be fine. I will see if there are any in the public sections... If you have a list of the public ones, you could add to this issues.
Well the one quoted (global_to_local__
) is in a public section.
I guess we could do a renaming, then do something like:
#define global_to_local__ new_name_for_global_to_local
to provide backwards compatibility.
global_to_local__
is in the private section of the Ioss::Map and Ioss::DatabaseIO classes in my code...
There are a couple xx__
in the public section of Iocgns::DatabaseIO, but I think they are just misplaced and can be moved to private...
Starting a PR to address this #420
global_to_local__
is in the private section of the Ioss::Map and Ioss::DatabaseIO classes in my code...
OK, I didn't look very deeply. I just see it under a public:
section:
class IOCGNS_EXPORT DatabaseIO : public Ioss::DatabaseIO
{
public:
[... snip ...]
int64_t node_global_to_local__(int64_t global, bool must_exist) const override;
Thanks for starting the PR!
I think the reference PR solves the issue. Please reopen if still problems.
VTK almost builds cleanly with clang's
-Wreserved-identifier
. Some of the remaining warnings are from seacas, ex:This warning is admittedly very pedantic, but it's often easy to fix with a simple rename. I was going to do so, but noticed many of the symbols in question are public. So not sure how to proceed...