Forgot your password?
typodupeerror
Programming GNU is Not Unix

Two Years of GNU Guile Scheme 2.0 107

Posted by Unknown Lamer
from the better-lisp-for-a-better-tomorrow dept.
Two years ago Guile Scheme, the official extension language of the GNU project, released version 2.0, a major upgrade to the implementation. As part of the two year anniversary, the maintainers organized a challenge to hack a small project using Guile in 30 days as part of a birthday software potluck. The two coolest dishes appear to be OpenGL support using the FFI, and XCB bindings built using the XML specification for XCB: "guile-xcb is a language implemented in the Guile VM that parses the XML files used by the xcb project to specify the X protocol and compiles them into Guile modules containing all the methods and data needed to send requests to the X server and receive replies/events back. If new X extensions are added to the xcb library, guile-xcb can compile and add them with no additional work. " See the release announcement for details on the other dishes.
This discussion has been archived. No new comments can be posted.

Two Years of GNU Guile Scheme 2.0

Comments Filter:
  • by Anonymous Coward on Wednesday February 20, 2013 @11:38AM (#42955783)

    Correct me if I'm wrong, but wouldn't that break the fact that in Lisp everything is supposed to be a list? In (+ a b) it's clear to both user and interpreter what the first member of the list is, but with {a + b} the interpreter may know what is what, but the user no longer sees firsthand that the s-expression is a list like any other. The key to groking Lisp is to learn to think recursively like the interpreter, and I would think that this change in notation unhealthily forces thinking patterns derived from other languages.

  • by cduffy (652) <charles+slashdot@dyfis.net> on Wednesday February 20, 2013 @11:52AM (#42955935)

    Correct me if I'm wrong, but wouldn't that break the fact that in Lisp everything is supposed to be a list?

    Plenty of LISPs break that "rule", and usually for the better. Clojure wouldn't be the tremendously practical and useful language it is if it didn't have vectors, maps, queues, and the like.

    What's important is that the language retains isomorphism (and thus, LISP's full measure of metaprogramming power) -- as long as your parse tree and your code map 1:1, adding some additional types does no harm and a world of good.

You will be successful in your work.

Working...