Re: Help Getting Sente to Work

> > Ok, new github issues is here >> . >> > Great, thanks - will follow up there later today! Cheers :-) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@goo

Re: Clojure on Cloudbees versus Heroku?

Yes. On Wed, Jul 30, 2014 at 5:18 PM, Jonathon McKitrick wrote: > Did you deploy clojure apps? > > > On Wednesday, July 30, 2014, Mark Engelberg > wrote: > >> My experience is that Cloudbees' free tier works better than Heroku's and >> is somewhat easier to deploy (with cloudbees you just uplo

Re: Clojure on Cloudbees versus Heroku?

Did you deploy clojure apps? On Wednesday, July 30, 2014, Mark Engelberg wrote: > My experience is that Cloudbees' free tier works better than Heroku's and > is somewhat easier to deploy (with cloudbees you just upload a war file > that you've built on your machine, whereas on Heroku, you are ch

Re: Clojure on Cloudbees versus Heroku?

My experience is that Cloudbees' free tier works better than Heroku's and is somewhat easier to deploy (with cloudbees you just upload a war file that you've built on your machine, whereas on Heroku, you are checking files into git which are built server-side, and if the build doesn't quite work pr

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2277

Can you please list the affected clients on this ticket http://dev.clojure.org/jira/browse/CLJS-830, thanks! David On Wed, Jul 30, 2014 at 5:29 PM, Thomas Heller wrote: > I posted some User Agents in the other Thread. > > https://groups.google.com/d/msg/clojurescript/diRGgGmTXPk/bbNMj3XHQ4AJ > >

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2277

I posted some User Agents in the other Thread. https://groups.google.com/d/msg/clojurescript/diRGgGmTXPk/bbNMj3XHQ4AJ Mozilla/5.0 (iPad; CPU OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D257 Safari/9537.53 Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac

Re: Redefined 'count' produces no warning

On Jul 30, 2014, at 1:37 PM, Andy Fingerhut wrote: > My first thought at a lint implementation was simply "warn if a let-bound > name matches any Var name in clojure.core", although granted that could > produce more false positives than you want. Yeah, I'd just disable that globally for our cod

Re: Redefined 'count' produces no warning

My first thought at a lint implementation was simply "warn if a let-bound name matches any Var name in clojure.core", although granted that could produce more false positives than you want. The linter could be enabled by default, and experienced folks could disable it completely. Alternately, whe

Re: Redefined 'count' produces no warning

Yeah, I do this all the time as well (in Cursive, I frequently have things with names like 'symbol' and 'list' for example), but it does bite me when I later refactor or copy some code around. I'm not sure what criteria I'd want used for this warning - attempting to invoke a local binding that had

Re: Future termination

Never is an awfully long time :-) If you wait about 60 seconds, the command you gave calling (future 1) does terminate, at least on Mac OS X 10.8.5 where I tested it, and I have seen the same behavior on Linux and I think Windows. This version terminates much more quickly: java -jar clojure-1.6.

Enterprise Integration Using SOAP Web Services an Clojure

Hi everyone, Are there any libraries other than clj-soap for implementing SOAP Web-Services? Regards, Timur -- 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

Future termination

Hello. I have a problems using code with futures. For example, if I run following code: java -jar clojure-1.6.0.jar -e "(println 1)" the process prints 1 and terminates. But when I'm trying to run code with futures: java -jar clojure-1.6.0.jar -e "(future 1)" the process doesn't terminates. T

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2277

Based on this information it sounds like the new Google Closure artifacts are good to go. The keyword thing we'll have to address in a subsequent release. It would be useful to know what Mobile Safari clients you see being affected. David On Wed, Jul 30, 2014 at 11:11 AM, Thomas Heller wrote: >

Re: ANN: ClojureScript 0.0-2277

FYI, using the :psuedo-names compiler option is very handy for debugging advanced-compile munging issues, e.g.: :compiler {:optimizations :advanced :pseudo-names true ...} On Wednesday, July 30, 2014 10:11:17 AM UTC-5, Thomas Heller wrote: > Geez, 2277 actu

Re: Redefined 'count' produces no warning

FWIW we have several places where the obvious local name shadows a core function - so the existing behavior is both desirable (IMO) and in existing production usage. I would not want to see that changed :) Eastwood seems like the correct place for this (Eastwood has continued to detect bugs in

Re: Redefined 'count' produces no warning

This would be an appropriate kind of check for a lint tool like Eastwood to make, and warn about. It currently does not do so, but I've created an issue to remind me of the potential enhancement. [1] It is up to the Clojure core team to decide whether they would like to make such a change to the

Re: timbre logging, java libs

Very useful, thanks! I was considering just dropping timbre, or extracting the profiling macros. The main things I use from timbre are the profiling macros. I found Stuart's post about the original contrib profiling macros being a half-baked idea, but I'm unaware of a usable alternative. GUIs l

Redefined 'count' produces no warning

I had code that looked like this: (let [{count :count data :data} (fetch-data) real-count (count data)]) As you can see, I was inadvertently redefining the 'count' symbol, and then tried to use the core 'count' function. I thought the compiler usually warned about this sort of

Re: Help Getting Sente to Work

Hey Peter, Responses are inlined. On Tue, Jul 29, 2014 at 12:51 AM, Peter Taoussanis wrote: > Wrt the CSRF issue, I'll try running again without it. >> > > Out of curiosity, sure - but if you've already gone to the effort of > setting up the CSRF I'd leave it in (better to have it) :-) > Yep,

Re: ANN: ClojureScript 0.0-2277

Geez, 2277 actually works just fine. 2234 doesn't work, but it actually doesn't work with either closure-library version. Forgot that I reverted to 2234 due to the keyword issue. 2277 + [org.clojure/google-closure-library "0.0-20140718-946a7d39"] seems fine, except for that keyword issue. Sorr

Re: ANN: ClojureScript 0.0-2277

Sorry, I would be if I could. Trying to track it down, but debugging an optimized build is not exactly easy. :( When using 2277 I have no errors, when using 2277 with the new closure lib release I have some "undefined" errors. That usually means some sort of renaming gone wrong. Error: Cannot

Re: ANN: ClojureScript 0.0-2277

Can you be more specific about the naming issues? David On Wednesday, July 30, 2014, Thomas Heller wrote: > David its probably best to hold off on that release. It seems the > closure-library HEAD version depends on a newer closure compiler version > than the one available via maven. > > At lea

Clojure on Cloudbees versus Heroku?

I've deployed a few apps to Heroku, but I'm always looking for new options with better pricing or features. Is there any reason Cloudbees might be better for Clojure apps than Heroku? If the big selling point of Cloudbees is Jenkins, I don't think that benefits Clojure projects, right? -- Yo

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2277

David its probably best to hold off on that release. It seems the closure-library HEAD version depends on a newer closure compiler version than the one available via maven. At least I'm seeing some renaming issues for advanced compilation. -- You received this message because you are subscribe