On Wed, May 2, 2012 at 10:15 PM, Sean Corfield wrote:
> I think the problem is that "good" Clojure style is still evolving and
> a lot of the libraries were started a while ago before the "no dynamic
> variables" guideline really took hold. That's to be expected in a new
> and evolving language.
Sorry for the slow response - we've been wrapped up in a gigantic data
migration at work...
On Tue, May 1, 2012 at 4:26 AM, Wolodja Wentland wrote:
> It certainly does, but I am none the wiser. I always had the
> feeling/impression
> that dynamic variables are something to be avoided, but I see
On Fri, Apr 27, 2012 at 22:21 -0700, Sean Corfield wrote:
> On Fri, Apr 27, 2012 at 4:14 AM, Wolodja Wentland wrote:
> > Could you elaborate on that please? I see that dynamic variables are used
> > quite
> > often to give the user the ability to configure/change the behaviour of a
> > library. T
On Fri, Apr 27, 2012 at 4:14 AM, Wolodja Wentland wrote:
> Could you elaborate on that please? I see that dynamic variables are used
> quite
> often to give the user the ability to configure/change the behaviour of a
> library. That approach is often coupled with a macro that changes the bindings
On Thu, Apr 26, 2012 at 23:35 -0700, Sean Corfield wrote:
> On Tue, Apr 24, 2012 at 8:30 PM, Michael wrote:
> > Would it be possible to make resultset-seq a dynamic var
>
> No, that certainly is not going to happen. Dynamic vars are not the
> right way to build an API in Clojure.
Could you elabo
