Proposal for a Go Interpreter

michaelbuckbee wrote: post #4

phlyingpenguin wrote: post #3

Earlier quoted context omitted.

Can you explain what you mean?

OP posted to a document that was/is modifiable by anyone who can access it - so jerks started messing with it.

Tought so, but now it says it's "too popular" and some features have been disabled, so it should be "solved" -- I definitely didn't see anything weird in the document.

Re: Proposal for a Go Interpreter

#6

Post by ecnahc515 » Mon, Sep 07, 2015, 1:18 AM UTC

FYI: To view it without the 'suggestions' just go to the right and change your own mode to view. Then the stupid changes other are suggesting wont show.

Re: Proposal for a Go Interpreter

#7

Post by mratzloff » Mon, Sep 07, 2015, 2:12 AM UTC

Go is a great language. But why on Earth would you want to script with it?

Re: Proposal for a Go Interpreter

#8

Post by derefr » Mon, Sep 07, 2015, 2:30 AM UTC

mratzloff wrote: post #7

Go is a great language. But why on Earth would you want to script with it?

I'm not sure either. So these are just guesses:

• You already know it.

• You want to use Go libraries.

• You want to extend a Go codebase at runtime, without integrating another language like Lua.

Weirder possibilities:

• You want to be able to use it as the basis for a Go "live image" system, where you can hot-reload modules on editor-save by re-parsing their source.

• You want to try building a Go version of Ruby's Pry (http://pryrepl.org)

• You want to enable your Go program to do stupid things involving generating strings of Go code and eval()ing them.

• You want to take some first steps toward some utopian dream of pushing live Goroutines over the network as frozen state + closure source, similar to what could be achieved on Mosix or the Erlang VM.

Re: Proposal for a Go Interpreter

#9

Post by archimedespi » Mon, Sep 07, 2015, 2:36 AM UTC

dr_zoidberg wrote: post #5

michaelbuckbee wrote: post #4

Earlier quoted context omitted.

OP posted to a document that was/is modifiable by anyone who can access it - so jerks started messing with it.

Tought so, but now it says it's "too popular" and some features have been disabled, so it should be "solved" -- I definitely didn't see anything weird in the document.

I didn't see anything odd either.

Re: Proposal for a Go Interpreter

#10

Post by alexschleber » Mon, Sep 07, 2015, 2:38 AM UTC

Here is a potentially more urgent idea: Create a transpiler Javascript to Go. Now THAT would get my attention.