Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Fri, Mar 4, 2011 at 12:53 PM, Stuart Halloway wrote: > In the context of chaining operators such as ->>, it is logical to consider > both the input and output of the function. The functions listed under the > "Seq In, Seq Out" section at http://clojure.org/sequences should all take > their seq

Re: Tranforming an ACL file: Comparing Clojure with Ruby

>> This is hardly unfortunate! The API is carefully designed: object args come >> >> first, seq args come last. >> >> Eh, not always: conj, nth, and several others put seq args first, >> though cons can be used on seqs in place of conj and has the seq arg >> last. >> >> You may be right, but so

Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Fri, Mar 4, 2011 at 12:34 PM, Stuart Halloway wrote: > This is hardly unfortunate! The API is carefully designed: object args come > > first, seq args come last. > > Eh, not always: conj, nth, and several others put seq args first, > though cons can be used on seqs in place of conj and has the

Re: Tranforming an ACL file: Comparing Clojure with Ruby

>> This is hardly unfortunate! The API is carefully designed: object args come >> first, seq args come last. > > Eh, not always: conj, nth, and several others put seq args first, > though cons can be used on seqs in place of conj and has the seq arg > last. You may be right, but so far your chose

Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Fri, Mar 4, 2011 at 7:50 AM, Stuart Halloway wrote: > This is hardly unfortunate! The API is carefully designed: object args come > first, seq args come last. Eh, not always: conj, nth, and several others put seq args first, though cons can be used on seqs in place of conj and has the seq arg

Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Fri, Mar 4, 2011 at 4:50 AM, Stuart Halloway wrote: > This is hardly unfortunate! The API is carefully designed: object args come > first, seq args come last. I didn't mean to imply that the first/last choice is random or arbitrary. I understand that the seq functions trace their history to l

Re: Tranforming an ACL file: Comparing Clojure with Ruby

> On Thu, Mar 3, 2011 at 9:15 PM, Stefan Rohlfing > wrote: >> I personally find Stuart's suggestion to be the most readable. The use of >> the ->> macro makes the workflow quite easy to follow. > > Yes, both the -> and ->> macros are useful. Unfortunately, about half > of Clojure's functions put

Re: Tranforming an ACL file: Comparing Clojure with Ruby

Thanks for your suggestion. Using the 'for' macro here makes the main part of the parse function much clearer. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new mem

Re: Tranforming an ACL file: Comparing Clojure with Ruby

'for' can be handy when unpacking compound lines: (ns foobar (:require [clojure.java.io :as io])) (defn parse-acl [acl-file] (with-open [r (io/reader acl-file)] (apply merge-with into (for [[status users path] (map #(.split % "\\|") (line-seq r)) :when (= "avail" stat

Re: Tranforming an ACL file: Comparing Clojure with Ruby

You are perfectly right. Organizing the code so that -> or ->> an be applied is key here. Unfortunately, only if all functions to be composed follow the same pattern of either 'insert first' or 'insert last' can these macros be used. -- You received this message because you are subscribed to t

Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Thu, Mar 3, 2011 at 9:15 PM, Stefan Rohlfing wrote: > I personally find Stuart's suggestion to be the most readable. The use of > the ->> macro makes the workflow quite easy to follow. Yes, both the -> and ->> macros are useful. Unfortunately, about half of Clojure's functions put the "object

Re: Tranforming an ACL file: Comparing Clojure with Ruby

Thank you all so much for helping me improve my code! I personally find Stuart's suggestion to be the most readable. The use of the ->> macro makes the workflow quite easy to follow. I hope that with some more experience I will be able to see these patterns myself and adapt my code accordingly

Re: Tranforming an ACL file: Comparing Clojure with Ruby

On Thu, Mar 3, 2011 at 7:35 PM, Mark Engelberg wrote: >        (when (not= avail "avail") Whoops, should be: (when (= avail "avail") -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note t

Re: Tranforming an ACL file: Comparing Clojure with Ruby

It's also worth noting that you can translate the Ruby code almost line for line if you make use of Clojure's atoms to adopt a more "imperative" approach. In general, it's more satisfying to find a pure functional way to solve a problem, but while you're transitioning from Ruby, it's not unreasona

Re: Tranforming an ACL file: Comparing Clojure with Ruby

Don't be afraid to split your work across multiple functions. Not only is this clearer, but you can then test the functions independently. So something like this: (defn access-map-add-users [access-map users path] (apply merge-with into access-map (for [user users] {user [path]}))) (

Re: Tranforming an ACL file: Comparing Clojure with Ruby

i was gonna suggest this: (let [users (->> (split (slurp "acl") #"\n") (map #(split % #"\|")) (map (fn [[a u p]] [a (split u #",") p])) (filter (fn [[a _ _]] (= "avail" a))) (mapcat (fn [[_ users path]]

Re: Tranforming an ACL file: Comparing Clojure with Ruby

> Dear Clojure Group, > > I am currently reading the online book Pro Git. In chapter 7.4 (section > “Enforcing a User-Based ACL System”) there is a task of reading in an access > control list (ACL) file, such as the following > > # avail/unavail | users | path > avail|nickh,pjhyett,defunkt,tpw

Tranforming an ACL file: Comparing Clojure with Ruby

Dear Clojure Group, I am currently reading the online book Pro Git . In chapter 7.4 (section “Enforcing a User-Based ACL System”) there is a task of reading in an access control list (ACL) file, such as the following # avail/unavail

Tranforming an ACL file: Comparing Clojure with Ruby

Dear Clojure Group, I am currently reading the online book Pro Git. In chapter 7.4 (section “Enforcing a User-Based ACL System”) there is a task of reading in an acce