151–160 of 185 posts
Why should I be interested in this - given there are many free high quality implementations for Scheme like Racket, Gambit etc?
Chez is known for being very fast, and for using state-of-the-art compiler technology.
Someone explain to me: Chez vs Gambit vs Chicken vs Bigloo. Which do I pick? Especially interested in parallel/multithreading abilities, standards compliance, and overall performance.
Out of the four you mentioned, only Chez has true posix threads.
Earlier quoted context omitted.
I newly joined this company, and they have 20 years old codebase which is mix of C and Scheme code. The only way they debug the massive Scheme part is using print statements. And I only have bad things to say about that. :( If there's a better way all of them have been missing, I'd love to hear that. I've learned that they have adapted the MIT Scheme implementation to add Object Oriented features, and it "kind of" wo…
> The only way they debug the massive Scheme part is using print statements. Why would you need anything else for debugging?!?
Earlier quoted context omitted.
> The only way they debug the massive Scheme part is using print statements. Why would you need anything else for debugging?!?
See I'm so naive I don't even know if this is sarcasm. :/
Earlier quoted context omitted.
> Apparently the [guile] 2.2 branch has full elisp support. Can't wait for Emacs to run on it. I really wish folks would spend the time they spent porting elisp to guile Scheme porting elisp to Lisp instead. Scheme's great for what it is (really), but what it is not is an industrial-strength systems programming language. Common Lisp is.
>porting elisp to guile Scheme This is a common misunderstanding. Emacs Lisp is not being rewritten as Scheme. What is actually happening is that there is a compiler for Emacs Lisp that runs on Guile's virtual machine. Elisp isn't going anywhere.
Earlier quoted context omitted.
See I'm so naive I don't even know if this is sarcasm. :/
I'm 100% serious. Interactive debugging is hugely overrated. I am not aware of a debugging technique better than logging + contracts + asserts.
IIRC, this was a high performance scheme developed at Indiana University that was closed source for a long time. Good on Cisco for open sourcing it. I'm interested to hear what regular scheme programmers feel about this news.
And aside from the JVM implementations and some works in progress the last time I checked, the only one with native instead of green threading.
Earlier quoted context omitted.
I'm 100% serious. Interactive debugging is hugely overrated. I am not aware of a debugging technique better than logging + contracts + asserts.
For one, that forces you to change the code and recompile all the time. And some projects have huge recompile times.
There is no big difference between building with contracts and logs on (log level is selected dynamically, no need to recompile) and building with debug symbols/suppressed optimisations.
Earlier quoted context omitted.
If you look at scheme.com, you will see Copyright © 2011 Cadence Research Systems. Cisco bought Cadence back in 2012.
AFAIK, Cisco never bought Cadence -- Cadence is an independent company -- maybe they bought some division or subsidiary of Cadence?
Earlier quoted context omitted.
>porting elisp to guile Scheme This is a common misunderstanding. Emacs Lisp is not being rewritten as Scheme. What is actually happening is that there is a compiler for Emacs Lisp that runs on Guile's virtual machine. Elisp isn't going anywhere.
Regardless, I wish that they'd spent that effort writing an elisp→Lisp compiler rather than an elisp→Scheme compiler.