Using gocode from command-line about gocode HOT 4 CLOSED

It helps to pay attention to -h ;) So now I have

gocode -in="test.go" autocomplete test.go 14

and now we blow up in package.go, at parseExportedName (331)

panic: expected "@", got String (""os'"")

steve d.

from gocode.

Hi. As far as I can see you use the latest gocode version, but you haven't updated to the latest Go weekly. Latest Go weekly has a new package files format, it was changed due to preparation for adding inlining optimizations.

So, just update your Go to the latest weekly or checkout different gocode version (see gocode git repo tags, it has a lot of compatibility tags).

from gocode.

That was about the second panic. The first panic indeed may happen due to incorrect cursor position. I wasn't paying a lot of attention to checking the correctness of incoming data.

from gocode.

Thanks, man - that worked great - I was obviously not paying attention when trying to update to latest Go (it did feel like a file format change problem). Thankfully, Go 1 will freeze things and we won't have to play catch-up all the time.

from gocode.