opeongo
opeongo
Duplicate of #603 Hi @rob-X1, @bugla Please read the issue #603 for details about what was going on with the release of beanshell 2.1.1 The summary is that it requires...
> Please go through the relevant points below and let us know if you agree with the decisions or not I had a quick review of your write up and...
I am still not able to use V3 for my workloads. It is a combination of small issues (like #725 and #726), deeper issues (#659) and planned incompatibilities (e.g. variable...
> It is not a small change. Seems to be a small non-intrusive change, have a look at #727. Could you help me out and explain what I overlooked that...
> > Seems to be a small non-intrusive change, have a look at #727. Could you help me out and explain what I overlooked that makes this more than a...
I found a fix for this problem. If consists of commenting out two lines in the AbstractCharStream class. See [my comments on the ParserGeneratorCC site](https://github.com/tulipcc/ParserGeneratorCC/issues/33#issuecomment-1480293386) about this. These changes can...
I took another look and was able to fix the remaining issues, the fix just had to gestate. By the way `new {{false}, true};` was explicitly test and checking the...
Hopefully this can be merged
Not trying to be confrontational, but this is so different from expectations that I don't see how this fits with BeanShell/Java model. I really think it is worth revisiting this...
I added a PR to fix this issue. Discussion welcome.