Inconsistent API naming

[Rot127]

Ensure cs_ prefix for all API structs, ids and function names?

Not all API structs and functions have the cs_ prefix. This leads to issues like these: #2316

The question is now, should this be addressed before the v6 Beta? Or before v6 Gold?

Or is API stability more important for everyone and we just keep it as is?

Currently the naming was kinda arbitrary. Sometimes only the arch_ prefix, sometimes cs_arch_.

I think though it is important to make a decision once and then stick with it. And with the many improvements and changes v6 brings, it is most suitable time to do it. So the annoyance is kept to one time only.

NOTE: This would only affect v6 and future versions. v5 would stay as is.

• API means here: Everything in include/capstone/. Internally we have more funny stuff going on, but this is out of scope.

[Rot127]

Converted this discussion back to an issue so a milestone can be assigned to it. Also people find it easier this way.

#2811