vic/rouge

---

vic/rouge.json

{
  "defaultBranch": "master",
  "description": "Ruby + Clojure = Rouge",
  "fullName": "vic/rouge",
  "homepage": "",
  "language": "Ruby",
  "name": "rouge",
  "pushedAt": "2012-10-12T11:39:14Z",
  "stargazersCount": 9,
  "updatedAt": "2025-09-23T20:49:24Z",
  "url": "https://github.com/vic/rouge"
}

rouge

Ruby + Clojure = Rouge.

quickstart

Rouge is not yet mature enough to have an installer or distributions. Just clone the source and run the rouge script to start:

git clone git://github.com/unnali/rouge
cd rouge
bundle install
bin/rouge

You’ll see the user=> prompt. Enjoy!

example

See boot.rg, em-rg, but to demonstrate salient features:

; define a macro
(defmacro defn [name args & body]
  `(def ~name (fn ~name ~args ~@body)))

; call a Ruby method on Kernel (if the ruby namespace is referred)
(defn require [lib]
  (.require Kernel lib))

; call a Ruby method on an Array with a block argument
(defn reduce [f coll]
  (.inject coll | f))

; using Ruby's AMQP gem with an inline block
(.subscribe queue {:ack true} | [metadata payload]
  (puts (str "got a message: " payload))
  (.ack metadata))

; copied from core.clj and modified to work with our currently smaller core
(defmacro binding [bindings & body]
  (let [var-ize (fn [var-vals]
                  (.flatten
                    (map
                      (fn [pair]
                        (let [key (first pair)
                              val (second pair)]
                          [`(.name (var ~key)) val]))
                      (.each_slice var-vals 2))
                    1))]
  `(try
     (push-thread-bindings (hash-map ~@(var-ize bindings)))
     ~@body
     (finally
       (pop-thread-bindings)))))

What about in Rails?

$ r c -- -I../rouge/lib -rrouge
Loading development environment (Rails 3.2.6)
1.9.3p194 :002 > Rouge::REPL.repl []
user=> (.where ruby/Content {:id 1})
  Content Load (0.7ms)  SELECT "contents".* FROM "contents" WHERE "contents"."id" = 1
[#<Content id: 1, content_group_id: 1, name: "welcome", content: "blah blah", created_at: "2012-08-26 11:30:50", updated_at: "2012-08-26 11:50:27", order: nil>]
user=>

TODO

See TODO, but big ones include:

• seqs
• persistent datastructures everywhere
• defprotocol

contributions

Yes, please! The usual dance would be:

• Fork.
• Check that tests are passing. (master should always be 100%, but currently this is not the case.)
• Make a topic branch.
• Do your tests, do your thing.
• Make sure you didn’t break anything!
• Pull request!

Note that I’ve yet to work out copyright or license (will ask on clojure-dev), but promise that they won’t be anything stupid.

authorship

Original author: Arlen Cuss — [ar@len.me]!(mailto:ar@len.me).

Inspiration: 100% Clojure. Thanks be to Rich Hickey.

copyright and licensing

Yet to be determined; likely EPL due to the entire concept and some code taken direct from Clojure.