Update bison to 3.6.4 about winflexbison HOT 11 CLOSED

Will take care of it after vacation at the end of July

from winflexbison.

I have updated win_bison to v3.7.1 please test binaries win_flex_bison-2.5.23.zip.

I pushed changes in master branch and built it using VS2019.

Will update CMake stuff in a week. @GitMensch if you have a chance to verify and fix existing CMake and create VS2019 build target I will really appreciate it.

from winflexbison.

if you have a chance to verify and fix existing CMake

only hardly, I try to not use CMake when it isn't necessary and dislike if I have to

and create VS2019 build target

In CMake or a plain VS sln? The later should be possible, if needed.

from winflexbison.

Bison 3.7 is really cool Haven't seen that before - thank you.
So did we get any further with the coloring? This would obviously be useful for 3.7, too.

from winflexbison.

only hardly, I try to not use CMake when it isn't necessary and dislike if I have to

Ok, don't mind I will update CMake.

In CMake or a plain VS sln? The later should be possible, if needed.

I have created VS2019 folder with sln file there.

So did we get any further with the coloring? This would obviously be useful for 3.7, too.

No, I only adopted new code.

Also I had to simplify unicode support introduced in 3.7.1 (see unicodeio.c ). For example instead of Unicode 'dot' symbol it uses fallback "*" character.

To fix this I need some example that uses this code (I guess it's some calling argument). I didn't dig into this.

from winflexbison.

Just looked at v3.7 release notes and saw '-Wcounterexamples' option that uses unicode symbols. I think it makes sense to fix "unicodeio.c" file.

from winflexbison.

Just looked at v3.7 release notes and saw '-Wcounterexamples' option that uses unicode symbols. I think it makes sense to fix "unicodeio.c" file.

After some investigation it seems very hard to output multibyte strings in windows console.
Will leave it as it is.
Any ideas/help are welcome.

vs

from winflexbison.

After some investigation it seems very hard to output multibyte strings in windows console.

That wouldn't be reasonable as the windows console has a long history of bad and partial broken support for that. The only "target" for that would be a redirection of stderr to a file.

Will leave it as it is.

If that is about the

   `.>

instead of the single multibyte character: that would be fine as-is.
But if someone uses an encoding with multibyte chars in the source file (UTF-8, UTF-16 or others) for the tokens, like

%token UMLAUT_AE		"Ä"
%token UMLAUT_UE		"Ü"

then this should be preserved in the generated source.

from winflexbison.

But if someone uses an encoding with multibyte chars in the source file (UTF-8, UTF-16 or others) for the tokens, like

I don't remember any other issues while adopting new bison version.

Can you check that mulibyte tokens are supported now or do you have some example *.y file to try?

from winflexbison.

A new release has been published v2.5.23
Also new version has been pushed as a chocolatey package v2.5.23.20200829.

from winflexbison.

Consider this issue as done.

from winflexbison.