Fix #524: wrong string entrypoint decl in C++

[andreasabel]

• Fix C++ backend: Parser.H declares pX(const char*) but implementation defines psX(const char*) #524: overloaded function for file/string entrypoint (as in 2.9.1)
  Closes C++ backend: Parser.H declares pX(const char*) but implementation defines psX(const char*) #524

• Fix C++ backend: Parser.H declares pX(const char*) but implementation defines psX(const char*) #524/nostl: missing declaration of string entrypoint in Parser.H file

[andreasabel]

@TheGhoul21 Please check whether this fixes the problem for you.

[TheGhoul21]

yes, it does fix perfectly the issue on my end. I was wondering: this is not a regression on some other parts of bnfc here? I mean: Probably there was a reason why this had been written this way in the first place? Anyway: using this specific version of the bnfc tool fixes my problem and I don't need to add special overwrites for my code to work.

[andreasabel]

I think it was just a bug introduced in 2.9.2.
You can also try out 2.9.1.1 (a re-release of 2.9.1 I made yesterday as 2.9.1 did not compile anymore).
There, you should also get the correct entrypoints (for STL, maybe not for NoSTL).

[TheGhoul21]

Yes, I definitely confirm that. Using the version 2.9.1.1 works like a charm, 2.9.2 has the issue and clearly this new version, 2.9.6.2 works like a charm as well.