Alejandro Anadon

It seems that somewere in grammar generation is looking if parameter is used in option rule. Next grammar also fails: ```grammar CommaSeparatorField; @parser::members { boolean falseFuntion(boolean foo) { return false;...

Hi, Has anyone been able to reproduce this issue? I just wanted to confirm if it really is a bug or a misunderstanding of antlr4. In case it is a...

Thanks for the reply; and even more knowing that you are focused on releasing the 4.11 release. I am not really trying to perform any action to execute during look...

Thanks again for your time. I imagine that you are with the new release, and I don't want to be the one who takes your time; so if you want,...

Hi, I found a way to make it work; but it is a very dirty way. It consists of creating a variable ('globalCommaAllow') in the parser that is assigned in...

Thank you very much for the reply. Seeing the results, what you say is what is happening: passing parameters should not condition the decision; and if you try, you will...

hi, if I may, I will start with the last sentence:"for a fixed length type having 0x00 or 0xFF as part of the rowkey should be fine for indexing". This...

Thanks for the time and atention. yes. Your summary is correct. Just to point out that I also added a UUID ARRAY type, but not a UUID_INDEXABLE ARRAY because I...

After the last commit I reached a stopping point. I would like to continue but I will need someone to tell me how to proced on what I had said...

You can ignore point number 6. I guess @stoty has changed/fixed something in 'Apache Yetus(jenkins) error: unit' and, as I imagined, no longer gives unit errors of type "InListIT.cleanUp:88 refCount...