Parser error on 386 arch by int overflows

[r3code]

Windows 7 32-bit
go1.11.2 windows/386
Trying to do:

package main

import (
	"github.com/antonmedv/expr"
)

func main() {
	p, err := expr.Compile("1+2") 
}

Build fails with multiple errors:

Installation failed: # github.com/antonmedv/expr/parser/gen
..\..\..\..\github.com\antonmedv\expr\parser\gen\expr_parser.go:2231: constant 4228579072 overflows int
..\..\..\..\github.com\antonmedv\expr\parser\gen\expr_parser.go:2249: constant 4228579072 overflows int
..\..\..\..\github.com\antonmedv\expr\parser\gen\expr_parser.go:2300: constant 4228579072 overflows int

[antonmedv]

Looks like Antlr generated code doesn't support 32 bit arch. I think this is Antlr issue.

[r3code]

@antonmedv I tried to update Go.
Now go version go1.12.9 windows/386 at one PC with Win 7 32bit it fails and at another it works (the same OS version).
How can I help to debug it?

Антон, на одной машине у нас все ОК, на другой такая ошибка. Может как то заставить Antlr перегенерировать код?

[r3code]

@antonmedv the related issue in Antlr antlr/antlr4#2433

[antonmedv]

Yes, I think this is only possible to solve it, by solving issue at Antlr. It's really difficult to patch already generated code.

[r3code]

@antonmedv Strange to see when at one computer it works and at another it fails... looks odd

[antonmedv]

Yes, but 4228579072 > 2^32 is overflow.

[hoshsadiq]

This antlr project doesn't seem to be very interested in this issue, I'm thinking, would it make sense to enforce int32 everywhere within this package?

[antonmedv]

Hmm, why to enforce? I’m thinking about rewriting parser from the scratch actually.

[hoshsadiq]

I guess my thinking is a bit premature without actually doing any research. I guess I was thinking that since this is an overflow error, it's likely that somewhere in this package int/int64 was used that then is passed into antlr. But once I read your comment I realised that this could equally be happening inside the antlr project.

[antonmedv]

Fixed.

I've rewritten the entire parser for this. :)

[r3code]

@antonmedv Is it here a3582e9 ?

[antonmedv]

Yes.

[r3code]

Спасибо!