Re: Keep application running when main thread only starts go blocks

2016-08-08 Thread Richard Möhn
On Sun, Aug 07, 2016 at 10:21:44PM -0600, Timothy Baldridge wrote: > So I'm tempted to ask at this point, what does your program do? If you're > doing nothing but CPU work, then yeah you may need to do something in the > main thread. However, all IO work should be done outside of go block. Go >

Re: Keep application running when main thread only starts go blocks

2016-08-07 Thread Richard Möhn
Am Samstag, 6. August 2016 21:30:53 UTC+9 schrieb Alex Miller: > > I think this is solution is fine. A single channel is not going to use any > noticeable resources. You've basically created a latch - there are several > latch-like things built into Java you can use as well. > > In the main

Re: Keep application running when main thread only starts go blocks

2016-08-07 Thread Richard Möhn
Am Samstag, 6. August 2016 16:50:35 UTC+9 schrieb Miguel Ping: > > Dunno about clojure, but in javaland you would submit jobs through an > executor and then wait for all tasks on the executor to finish, blocking > the main thread. > > A bit of googling, and you can alter the core.async

Re: ANN: diehard 0.3.0

2016-08-07 Thread Richard Möhn
Great! I was just going go implement a primitive retry myself, when I found this by chance. Thanks for contributing! -- 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

Keep application running when main thread only starts go blocks

2016-08-05 Thread Richard Möhn
I'm using core.async. In my application the main thread creates a few channels, starts a few go blocks and that's it. When I run it as a stand-alone (i.e. not in the REPL), it starts those go blocks and then exits. After being surprised initially, I understand why this happens: the main thread

Global catastrophic risks

2016-03-27 Thread Richard Möhn
http://worrydream.com/ClimateChange/ I hadn't been thinking about global overheating (aka climate change) much before Eric Normand recommended that article of Bret Victor's in his Clojure Gazette. Now I'm thinking about it a lot and thought I'd try and bring it to broader attention in the

Re: [ANN] Grenada 1.0.0-rc.2

2015-08-30 Thread Richard Möhn
Am Mittwoch, 26. August 2015 11:33:13 UTC+9 schrieb Richard Möhn: Am Dienstag, 25. August 2015 18:11:25 UTC+9 schrieb zcaudate: […] Hydrox looks good! (As do your other libraries. – I hadn't had them on my radar at all until now.) It appears to be a cool new tack on documentation

Re: [ANN] Grenada 1.0.0-rc.2

2015-08-26 Thread Richard Möhn
Am Mittwoch, 26. August 2015 14:52:31 UTC+9 schrieb zcaudate: […] Yep, it’s exactly how you’ve described. The main emphasis is on writing documentation that can be verified through tests and so if the api changes, then the documentation can be fixed accordingly. The grenada project

Re: [ANN] Grenada 1.0.0-rc.2

2015-08-25 Thread Richard Möhn
Am Dienstag, 25. August 2015 18:11:25 UTC+9 schrieb zcaudate: […] Great work on the project! I'd love to see the final generated output if you have time to do so. Also, we at Helpshift are working on a similar project here - https://github.com/helpshift/hydrox. It'll be great to get your

Re: [ANN] Grenada 1.0.0-rc.2

2015-08-19 Thread Richard Möhn
Apologies to those reading this as plain text. I had forgotten how horrible Google Groups' rendering is. -- 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

[ANN] Grenada 1.0.0-rc.2

2015-08-19 Thread Richard Möhn
This project was announced three months ago as a ‘Common Clojure Source Metadata Model’. You might also have read about it http://us4.campaign-archive1.com/?u=a33b5228d1b5bf2e0c68a83f4id=52f3bba560 in the Clojure Gazette. It is now called Grenada https://github.com/clj-grenada/grenada-spec and

Re: [ANN] suchwow: a grab-bag library with some twists

2015-07-14 Thread Richard Möhn
Hi all, I'm the GSoC student. Sorry for tuning in rather late. What you talk about sounds all very familiar to me. Some comments below. Am Mittwoch, 15. Juli 2015 03:40:26 UTC+9 schrieb Reid McKenzie: […] I'm also advising the GSoC documentation representation project, which is publicly

Re: Identifying objects that cannot be read

2015-06-18 Thread Richard Möhn
I mean, as long as that's the only case, it's fine. But I don't know what cases there are… -- 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 -

Re: Identifying objects that cannot be read

2015-06-18 Thread Richard Möhn
Am Mittwoch, 3. Juni 2015 11:05:03 UTC+9 schrieb Alex Miller: Try pr with 1.7.0-RC1 ... Meh: user= (def bla 4) #'user/bla user= (pr-str #'bla) #'user/bla user= (edn/read-string (pr-str #'bla)) RuntimeException No dispatch macro for: ' clojure.lang.Util.runtimeException (Util.java:221)

Re: Identifying objects that cannot be read

2015-06-03 Thread Richard Möhn
Am Donnerstag, 4. Juni 2015 00:10:33 UTC+9 schrieb Marshall Bockrath-Vandegrift: Richard Möhn richar...@posteo.de javascript: writes: How do I remove from a nested datastructure the objects whose (pr obj) representation doesn't comply with the EDN specification? Fx, {:a 1 :b (find

Identifying objects that cannot be read

2015-06-02 Thread Richard Möhn
How do I remove from a nested datastructure the objects whose (pr obj) representation doesn't comply with the EDN specification? Fx, {:a 1 :b (find-ns 'user)} → {:a 1} Or, easier, how do I just not print these objects? I want to extract the metadata maps from arbitrary Clojure objects and

Re: [ANN, GSoC] A Common Clojure Source Metadata Model

2015-06-02 Thread Richard Möhn
Am Donnerstag, 28. Mai 2015 07:57:37 UTC+9 schrieb Colin Fleming: […] Much of this is specific to editing environments, and more concretely specific to Cursive. It's also mostly necessary because I'm working from unexpanded source rather than introspecting a REPL. I see. I think I

Re: Identifying objects that cannot be read

2015-06-02 Thread Richard Möhn
Am Mittwoch, 3. Juni 2015 11:05:03 UTC+9 schrieb Alex Miller: Try pr with 1.7.0-RC1 ... Awesome. -- 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

Re: [ANN, GSoC] A Common Clojure Source Metadata Model

2015-05-25 Thread Richard Möhn
Am Freitag, 22. Mai 2015 11:09:40 UTC+9 schrieb Colin Fleming: On one of the latest Cognicasts, Colin Fleming talked about a repo where library authors can upload extensions that help the IDE understand their macros. I have to listen to it again, but it sounded a bit like what you're

Re: [ANN, GSoC] A Common Clojure Source Metadata Model

2015-05-21 Thread Richard Möhn
Thanks for the great feedback! Am Freitag, 22. Mai 2015 05:48:38 UTC+9 schrieb Laurent PETIT: Sorry for jumping late inside the pool, but the topic has retained my attention from day one. As a developer of an IDE plugin (CounterClockWise for Eclipse), I'm very interested in this effort.

Re: [ANN, GSoC] A Common Clojure Source Metadata Model

2015-05-19 Thread Richard Möhn
Just trying to bump this up a bit. Coding will start soon, so I'd be happy about some more input. Especially if you have further thoughts or wishes along the lines of https://groups.google.com/d/topic/clojure/E1oxVE4UMxQ/discussion. -- You received this message because you are subscribed to