The first Go program (2013)

Post by coldtea » Sun, Mar 05, 2017, 4:29 PM UTC

frou_dh wrote: post #9

wtbob wrote: post #4

Earlier quoted context omitted.

One of my backlog-projects is an implementation of Common Lisp in Go, which can be easily used to provide an embedded scripting language for Go programs (and, eventually, an excuse to write 'Go' code which is actually Lisp). It's one of those crazy ideas I'll probably never get to, but it sure would be fun.

I have ~that. Of course it's not Common Lisp though (so, Hubris Lisp?). Notably you have to statically register the Go functions you want to be callable from the Lisp side, because otherwise they might not even be present in the compiled binary (and even if they were, I don't think Go will help you find an arbitrary function by name at runtime). I've used it much more as a normal 'shebang' shell scripting language (e…

Post by coldtea » Sun, Mar 05, 2017, 4:49 PM UTC

frou_dh wrote: post #12

coldtea wrote: post #11

Earlier quoted context omitted.

> and even if they were, I don't think Go will help you find an arbitrary function by name at runtime You'd be surprised: https://golang.org/pkg/reflect/#Value.MethodByName

That's about methods and not functions ;) Yes indeed, if you are partying in the context of a specific value, you can use that reflection. My language is not "OO"-aware though. Maybe after I give the embedded mode more real world use then that aspect will be unavoidable.

Post by coldtea » Sun, Mar 05, 2017, 5:43 PM UTC

frou_dh wrote: post #14

coldtea wrote: post #13

Earlier quoted context omitted.

A, yes. In that case you could expose all the functions you want in advance, in some map that's accessible by (string) name.

// Static err = rootEnv.DefineForeignProcedure("sprintf", fmt.Sprintf) # Runtime (let x 2 (sprintf "%d cubed is %d" x (pow x 3))) => "2 cubed is 8"