[ANN] ribol 0.3.1 - conditional restarts - api stablized, docs updated.

[zcaudate]

Thanks everybody for your feedback and suggestions on the last post.

Version 0.3.1 has the following updates: 

The `finally` clause is supported on `manage` - http://z.caudate.me/ribol/#finally as well as all the hook forms - http://z.caudate.me/ribol/#hooks

`raise-on` and `raise-on-all` have been updated to work better with thrown clojure.lang.ExceptionInfo objects

I've also put in a section on how code can be reused using restarts - http://z.caudate.me/ribol/#unlucky-numbers

[Baishampayan Ghose]

Hi Chris,
If you get the time, could you also write about the architecture of
ribol, its implementation details, etc. too? That'd be immensely
useful.

~BG

> --
> --
> 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/groups/opt_out.



--
Baishampayan Ghose
b.ghose at gmail.com

[Chris Zheng]

No worries!

I'll have a think about how to best go about it. My last attempt at a meet up was a bit of a failure =)

> You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/mpFgNfrAx4Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.

[Dima Sabanin]

Hi Chris,

Thanks for your work on this! I've a new question though. Will the exceptions raised with raise-on and raise-on-all preserve the cause exception? It'd be great if original cause was visible in the stack trace.

Thanks,

Dima

Best regards,
Dima Sabanin
http://twitter.com/dimasabanin

[Chris Zheng]

Hi Dima!

No it will not :) 

I can put an additional :stacktrace key in the issue if that suits you.

[Chris Zheng]

Dima and BG,

A new version is up with implementation details - http://z.caudate.me/ribol/#implementation

as well as the requested stacktrace … although I called it :origin instead of :stacktrace.

- http://z.caudate.me/ribol/#raise-on

Chris

[Baishampayan Ghose]

This is fantastic, Chris. Many thanks! ~BG