Implementing a bignum calculator – Rob Pike [video]

Post by xtacy » Fri, Dec 19, 2014, 3:08 PM UTC

xixixao wrote: post #11

This snippet from the implementation sheds some light on the origins of Go for me, the mindset from which it's born and why it isn't a language for me. interactive := false if name == "-" { interactive = true fd = os.Stdin } else { interactive = false fd, err = os.Open(name) } Or do you think I am reading into it too much?

Post by tptacek » Fri, Dec 19, 2014, 4:19 PM UTC

willvarfar wrote: post #4

He wants to compute some bignums, so he writes an APL interpreter in Go... Now he is scratching his itch and making nice slides to boot. However, it would have been simpler for him to have typed "python" at the commandline... Python ints are arb precision :)

Post by pkhagah » Fri, Dec 19, 2014, 4:52 PM UTC

angersock wrote: post #15

lispm wrote: post #10

Earlier quoted context omitted.

or GNU CLISP which not only has big ints, big ratios, big complex (like all Common Lisp implementations), but also big floats. Big ratios: [2]> (/ 5723475972349572938475982734985723984759823749587 7239457928374598723984759237459723497598234) 5723475972349572938475982734985723984759823749587/7239457928374598723984759237459723497598234 Big complex numbers: [4]> (* 572934759237495723482374957239475982374957239847523485…

Ah yes, but a small userbase!

Post by deeviant » Fri, Dec 19, 2014, 6:24 PM UTC

pkhagah wrote: post #16

angersock wrote: post #15

Earlier quoted context omitted.

Ah yes, but a small userbase!

If you're talking about userbase, I presume, Go should have less of a userbase than lisp.

Post by reportingsjr » Fri, Dec 19, 2014, 6:43 PM UTC

deeviant wrote: post #18

pkhagah wrote: post #16

Earlier quoted context omitted.

If you're talking about userbase, I presume, Go should have less of a userbase than lisp.

People use lisp for something other than a programming discussion talking point?