Re: [go-nuts] GoAWK: an AWK interpreter written in Go

2018-11-17 Thread 'Alan Donovan' via golang-nuts
This is great, both as an "étude"---a challenge for sharpening your technique---and as an exemplary write-up of the process of building something non-trivial and making it both correct and fast. Nice work. I'm sure you knew already, but Peter Weinberger (the W in AWK) is on the Go team at Google.

Re: [go-nuts] GoAWK: an AWK interpreter written in Go

2018-11-17 Thread ktye78
That looks nice! I wonder if it makes sense, to expose more of the interpreter to go. E.g.: register a user function or add an action written in go. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving

[go-nuts] Re: HTTP client CheckRedirect behavior for the first redirect

2018-11-17 Thread Caleb Spare
I took another look at this and realized what I'd gotten wrong: each Request given to CheckRedirect, including req and each of via, has a nested Response that caused the request, *not* the response to that request, as I had assumed. This is mentioned in the documentation: // Response is the redire

[go-nuts] compiling from within vim not working

2018-11-17 Thread rob
Hi.  I'm interested in trying the internal compiling option for Go. Vim 7.4.  Ubuntu 16.04 amd64 go 1.11.2 I'm using the version of vim that gets installed by apt. When I type :make from a window showing a buffer containing Go code, I get this error: /bin/bash: go: command not found .vimrc

Re: [go-nuts] GoAWK: an AWK interpreter written in Go

2018-11-17 Thread Ben Hoyt
I've "finished" my Go AWK interpreter and released v1.0.0 now. I've fixed several bugs, and also sped up the interpreter significantly, primarily by: 1) Resolving variable names to integers at parse time so we can do []value lookups instead of map[string]value lookups at runtime 2) Using normal er