22
iiii
3y

I really wonder who is that genius from API team who decided that a namespace with the name "main" is a great fucking idea...

Because of this shit I've had to resort to hacky pImpl implementation of the API.

Comments
  • 4
    it's like someone didn't know what main() is, or does and decided to roll their own dice instead. 😦

    I can't decide which is worse.
  • 1
    Jesus fucking Christ. What an absolute dong-head thought this would be a good idea?!?
  • 0
    Why not just rename the namespace ?
  • 0
    Wait c++ will consider namespaces and variables and functions in the same scope ???
    That makes no sense !
  • 0
    @MadMadMadMrMim external API. I have no power over it
  • 0
    @iiii well that sucks.
  • 0
    @MadMadMadMrMim it sucks indeed.
  • 0
    Wow. Just wow. I have now tried several attempts to resolve this in a little test file. There is really no way around isolating off the main function into its own module to avoid the name clash. Whoever did this is either a complete idiot... or a real badass C++ troll.
  • 1
    @iiii in .net namespaces and classes don’t exist in the same scope that way
  • 0
    Rename it to master 😂
  • 1
    @DirtEffect yes, you can only isolate the submodule that uses that API.
Add Comment