Re: [ANN] org.clojure/tools.cli 0.4.1

2018-10-05 Thread Pierre-Yves Ritschard
Thanks for tools.cli, it's a pillar of a number of our projects, present in 
almost all our `main.clj` files :-)

On Sunday, September 23, 2018 at 11:16:34 PM UTC+2, Sean Corfield wrote:
>
> Alex says the auto-generation process is broken and needs to be run 
> manually for each project right now. I figured out that was 
> `clojure/contrib-api-doc` and ran it on `tools.cli` so those docs are 
> up-to-date now.
>
>  
>
> I also ran it manually for `java.jdbc` so that’s up-to-date 
> (0.7.9-SNAPSHOT) as well.
>
>  
>
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
>  
> --
> *From:* Sean Corfield >
> *Sent:* Sunday, September 23, 2018 1:35:42 PM
> *To:* clo...@googlegroups.com 
> *Subject:* RE: [ANN] org.clojure/tools.cli 0.4.1 
>  
>
> That documentation is auto-generated behind the scenes as part of the 
> build system (I think, or maybe some other process) so if it isn’t 
> up-to-date, maybe Alex Miller can take a look?
>
>  
>
> Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
> An Architect's View -- http://corfield.org/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
>  
> --
> *From:* clo...@googlegroups.com   > on behalf of Patrick Kristiansen  >
> *Sent:* Sunday, September 23, 2018 12:54:25 PM
> *To:* Clojure
> *Subject:* Re: [ANN] org.clojure/tools.cli 0.4.1 
>  
> Thanks, Sean. 
>
> Any chance you could update the API documentation here: 
> http://clojure.github.io/tools.cli/index.html
>
> On Sunday, September 23, 2018 at 5:18:44 AM UTC+2, Sean Corfield wrote: 
>>
>> Tools for working with command line arguments. 
>> https://github.com/clojure/tools.cli clj -Sdeps '{:deps 
>> {org.clojure/tools.cli {:mvn/version "0.4.1"}}}' 
>> Boot/Leiningen: [org.clojure/tools.cli "0.4.1"] This is a minor update 
>> that introduces new options :update-fn and :default-fn that make it easier 
>> to work with non-idempotent command line options (such as 
>> incrementing/counting options) and addresses a problem raised in 
>> https://dev.clojure.org/jira/browse/TCLI-90 (poor interaction between 
>> the existing :assoc-fn and :default options).
>> -- 
>> Sean A Corfield -- (904) 302-SEAN
>> An Architect's View -- http://corfield.org/
>> World Singles, LLC. -- http://worldsingles.com/
>>
>> "Perfection is the enemy of the good."
>> -- Gustave Flaubert, French realist novelist (1821-1880)
>>
> -- 
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@googlegroups.com 
> Note that posts from new members are moderated - please be patient with 
> your first post.
> To unsubscribe from this group, send email to
> clojure+u...@googlegroups.com 
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+u...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ANN] com.walmartlabs/cond-let 1.0.0

2018-10-05 Thread Howard Lewis Ship
I'm glad my little library has gotten some attention on better-cond, which
even I'm switching over to.

On Thu, Oct 4, 2018 at 10:39 PM Mark Engelberg 
wrote:

> Documentation for latest features in the 2.0.1 branch:
> https://github.com/Engelberg/better-cond/tree/v2.0.1
>
> An example:
>
>  (cond
>(odd? a) 1
>:let [a (quot a 2)]
>:when-let [x (fn-which-may-return-nil a),
>   y (fn-which-may-return-nil (* 2 a))]
>:when (seq x)
>:do (println x)
>(odd? (+ x y)) 2
>:else 3)
>
> The :do performs a side-effecting statement if it gets that far in the
> cond.  :do is my favorite bonus addition for cond beyond :let.  I find I
> use it a lot to quickly insert some debugging print commands without
> needing to change the shape of my code, so it can be trivially removed
> later.
>
> When :do did not exist, but :let did exist in my cond macro, I found
> myself frequently writing things like:
> :let [_ (println x)]
> in order to insert a side-effecting statement into the cond sequence.
> :do is a cleaner solution.
>
> :when only continues with the cond if the value is truthy, otherwise it
> bails out of the cond with nil.
> :when-some (not yet merged in) will do much the same thing, but continuing
> if non-nil, rather than truthy.
>
> :when, :when-some, and :when-let don't add a whole lot of richness.  For
> example, that :when line in the example could just have easily been written
> as:
> (not (seq x)) nil
>
> But using these can potentially add clarity of intention, so even though I
> could make do without them, I go ahead and use them when relevant.
>
> In better-cond's cond macro, that final :else is optional. You may prefer
> the new cond-let library if you want to continue enforcing the use of :else
> on the last clause.
>
> To reiterate, :let is by far the most valuable addition, and I find :do to
> be the second-most valuable addition.  Other additions are fairly minor
> syntactic sugar.
>
> On Thu, Oct 4, 2018 at 1:36 PM Alan Thompson  wrote:
>
>> How would the :when and :do forms work?
>> Alan
>>
>> On Wed, Oct 3, 2018 at 7:22 PM Mark Engelberg 
>> wrote:
>>
>>> This looks like a case of "convergent evolution".
>>>
>>> Having the ability to do a :let in the middle of a cond feels like one
>>> of those things that *should* be in the core language, so if it's not
>>> in there, a bunch of people are naturally going to arrive at the same
>>> solution and make it happen in their own utility libraries.  A bunch of us
>>> Clojure programmers from the early 1.0 days had been privately passing
>>> around and using a "cond that supports :let bindings" macro for years.  The
>>> first time I saw the macro was in a blog post by Christophe Grand. I really
>>> hoped it would make it into Clojure proper -- other functional languages
>>> like Racket and F# support ways to bind local variables with "clearer, more
>>> linear code, that doesn't make a march for the right margin", as Howard
>>> Lewis Ship put it.  But after several years had passed without any
>>> indication that CLJ-200 was ever going to be addressed, I eventually made
>>> the improved cond macro into a clojars library.
>>>
>>> walmartlabs' cond-let addresses the most important thing (let), which is
>>> the critical piece of functionality that feels like the most natural,
>>> needed addition to the language.  better-cond's :let syntax is identical.
>>> But as us old-school Clojurians passed around the "better cond" macro over
>>> the years, it grew in functionality.  So in better-cond, I included the
>>> other little improvements that had accumulated over time, which I had found
>>> useful.  So better-cond also supports :when, :when-let, and :do (and will
>>> soon have :when-some).  :let is the only piece that I felt really belonged
>>> in the core language's cond, and if CLJ-200 had made it into the core
>>> language, I would have been content to just use Clojure's own cond.  But
>>> once I realized I was going to need a library to achieve the much-needed
>>> :let inside of cond, I figured I might as well use that library to include
>>> the other convenient cond additions as well.  So better-cond is a superset
>>> of cond-let's functionality, with support for :let plus a few bonuses.
>>>
>>> Use whichever one strikes your fancy.  cond-let is perfect if all you
>>> care about is adding :let to your cond.  If you want to experiment with
>>> some of the other features beyond :let, you could use better-cond and see
>>> what you think.
>>>
>>> Either way, I strongly encourage you to use one of these two libraries
>>> so you can start using :let inside your cond.  I agree fully with Howard
>>> Lewis Ship that it results in clearer code.  Try either library which
>>> supports this -- it will change your life!
>>>
>>>
>>> On Wed, Oct 3, 2018 at 5:05 PM Matching Socks 
>>> wrote:
>>>
 Is this a refinement of Mark Engelberg's "better-cond", or an
 alternative approach?

 I have not used better-cond myself, but it s

SOAP server

2018-10-05 Thread Renata Soares
Hello!

I need suggestions of libraries (or others solutions) to implement a soap 
server in a clojure project. The project is long-term and i saw some 
libraries that are no longer maintained. So anyone uses one of them? Which 
is recommended?

Thanks.

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Differences in generator output for gen/fmap

2018-10-05 Thread Alexander Sedgwick
I'm running into differences when having gen/fmap inside a s/with-gen vs 
running it outside a s/with-gen. Am I missing something?

```clojure
(ns scribble
  (:require [clojure.spec.alpha :as s]
[clojure.spec.gen.alpha :as gen]))

(s/def ::some-int
  (s/or :zero zero?
:pos pos-int?))

;; works as expected
(gen/sample (gen/fmap
 (fn [x] (* x 2))
 (s/gen ::some-int)))

(s/def ::some-other-int
  (s/with-gen
(s/or :zero zero?
  :pos pos-int?)
#(gen/fmap
  (fn [x] (* x 2))
  (s/gen ::some-other-int

;; Stack overflow
(gen/sample (s/gen ::some-other-int))
```
Any help is appreciated.

Thanks!
Alex

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Differences in generator output for gen/fmap

2018-10-05 Thread Alexander Sedgwick
Nevermind, I see now the infinite loop I've generated.. I'll delete the 
post thanks!

On Friday, October 5, 2018 at 1:49:12 PM UTC-5, Alexander Sedgwick wrote:
>
> I'm running into differences when having gen/fmap inside a s/with-gen vs 
> running it outside a s/with-gen. Am I missing something?
>
> ```clojure
> (ns scribble
>   (:require [clojure.spec.alpha :as s]
> [clojure.spec.gen.alpha :as gen]))
>
> (s/def ::some-int
>   (s/or :zero zero?
> :pos pos-int?))
>
> ;; works as expected
> (gen/sample (gen/fmap
>  (fn [x] (* x 2))
>  (s/gen ::some-int)))
>
> (s/def ::some-other-int
>   (s/with-gen
> (s/or :zero zero?
>   :pos pos-int?)
> #(gen/fmap
>   (fn [x] (* x 2))
>   (s/gen ::some-other-int
>
> ;; Stack overflow
> (gen/sample (s/gen ::some-other-int))
> ```
> Any help is appreciated.
>
> Thanks!
> Alex
>

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: SOAP server

2018-10-05 Thread Erik Assum
Last time I worked with SOAP, I used plain old java interop which suited me 
quite nicely.
Here is a repo which shows how that worked:

https://github.com/slipset/soap-box/

HTH,

Erik.

> On 5 Oct 2018, at 20:43, Renata Soares  wrote:
> 
> Hello!
> 
> I need suggestions of libraries (or others solutions) to implement a soap 
> server in a clojure project. The project is long-term and i saw some 
> libraries that are no longer maintained. So anyone uses one of them? Which is 
> recommended?
> 
> Thanks.
> 
> -- 
> 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 members are moderated - please be patient with your 
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: SOAP server

2018-10-05 Thread Sean Corfield
Yup, as someone who has also gone down this path before, I agree that Java 
interop is probably the way to go these days. SOAP is very enterprise-y and I 
expect most Clojurians try to avoid it where possible 😊

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


From: clojure@googlegroups.com  on behalf of Erik 
Assum 
Sent: Friday, October 5, 2018 1:19:51 PM
To: clojure@googlegroups.com
Subject: Re: SOAP server

Last time I worked with SOAP, I used plain old java interop which suited me 
quite nicely.
Here is a repo which shows how that worked:

https://github.com/slipset/soap-box/

HTH,

Erik.

On 5 Oct 2018, at 20:43, Renata Soares 
mailto:renata.sd...@gmail.com>> wrote:

Hello!

I need suggestions of libraries (or others solutions) to implement a soap 
server in a clojure project. The project is long-term and i saw some libraries 
that are no longer maintained. So anyone uses one of them? Which is recommended?

Thanks.

--
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ANN] Clojure 1.10.0-beta1

2018-10-05 Thread Alex Miller


1.10.0-beta1 is now available. You can try it with clj using:
  clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version 
"1.10.0-beta1"}}}'

1.10.0-beta1 includes the following changes since 1.10.0-alpha9:

   - Revert change for CLJ-1550 
    - Classes generated by 
   deftype and defrecord don’t play nice with .getPackage
   - Revert change for CLJ-1435 
    - 'numerator and 
   'denominator fail to handle integral values (i.e. N/1)
   - Add changelog since 1.9
   - Mark prepl as alpha
   

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ANN] Clojure 1.10.0-beta1

2018-10-05 Thread Alex Miller
Now is a great time to try 1.10.0-beta1 and let us know if you find any 
major bugs or performance issues. 

I also meant to mention that all changes in Clojure 1.10 are now collected 
in the changelog:

https://github.com/clojure/clojure/blob/master/changes.md

At this point, we consider 1.10 to be feature complete and only plan to 
address critical bug fixes so we can move expeditiously towards a final 
release.



On Friday, October 5, 2018 at 11:09:25 PM UTC-5, Alex Miller wrote:
>
> 1.10.0-beta1 is now available. You can try it with clj using:
>   clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version 
> "1.10.0-beta1"}}}'
>
> 1.10.0-beta1 includes the following changes since 1.10.0-alpha9:
>
>- Revert change for CLJ-1550 
> - Classes generated by 
>deftype and defrecord don’t play nice with .getPackage
>- Revert change for CLJ-1435 
> - 'numerator and 
>'denominator fail to handle integral values (i.e. N/1)
>- Add changelog since 1.9
>- Mark prepl as alpha
>
>

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ANN] Clojure 1.10.0-beta1

2018-10-05 Thread Alan Thompson
Looks good to me, tested on both prod and open source code.
Alan

On Fri, Oct 5, 2018 at 9:21 PM Alex Miller  wrote:

> Now is a great time to try 1.10.0-beta1 and let us know if you find any
> major bugs or performance issues.
>
> I also meant to mention that all changes in Clojure 1.10 are now collected
> in the changelog:
>
> https://github.com/clojure/clojure/blob/master/changes.md
>
> At this point, we consider 1.10 to be feature complete and only plan to
> address critical bug fixes so we can move expeditiously towards a final
> release.
>
>
>
> On Friday, October 5, 2018 at 11:09:25 PM UTC-5, Alex Miller wrote:
>>
>> 1.10.0-beta1 is now available. You can try it with clj using:
>>   clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version
>> "1.10.0-beta1"}}}'
>>
>> 1.10.0-beta1 includes the following changes since 1.10.0-alpha9:
>>
>>- Revert change for CLJ-1550
>> - Classes generated by
>>deftype and defrecord don’t play nice with .getPackage
>>- Revert change for CLJ-1435
>> - 'numerator and
>>'denominator fail to handle integral values (i.e. N/1)
>>- Add changelog since 1.9
>>- Mark prepl as alpha
>>
>> --
> 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 members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: [ANN] Clojure 1.10.0-beta1

2018-10-05 Thread Sean Corfield
Thank you! We’re already on Alpha 8 in production, and we upgraded to Alpha 9 
in dev today. We’ll get Beta 1 onto dev and into QA on Monday and I expect 
we’ll take it to production early next week.

Will there be more detail about prepl in a blog post or similar?

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


From: clojure@googlegroups.com  on behalf of Alex 
Miller 
Sent: Friday, October 5, 2018 9:21:20 PM
To: Clojure
Subject: Re: [ANN] Clojure 1.10.0-beta1

Now is a great time to try 1.10.0-beta1 and let us know if you find any major 
bugs or performance issues.

I also meant to mention that all changes in Clojure 1.10 are now collected in 
the changelog:

https://github.com/clojure/clojure/blob/master/changes.md

At this point, we consider 1.10 to be feature complete and only plan to address 
critical bug fixes so we can move expeditiously towards a final release.



On Friday, October 5, 2018 at 11:09:25 PM UTC-5, Alex Miller wrote:

1.10.0-beta1 is now available. You can try it with clj using:

  clj -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.10.0-beta1"}}}'


1.10.0-beta1 includes the following changes since 1.10.0-alpha9:

  *   Revert change for CLJ-1550 
- Classes generated by deftype and defrecord don’t play nice with .getPackage
  *   Revert change for CLJ-1435 
- 'numerator and 'denominator fail to handle integral values (i.e. N/1)
  *   Add changelog since 1.9
  *   Mark prepl as alpha

--
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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 members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.