We have a large app at CircleCI - as of September:
"The repo for our main app contains 93,983 lines of Clojure code. The src
directory of our main app contains 369 namespaces."
http://blog.circleci.com/why-were-no-longer-using-core-typed/
On Sun, Nov 15, 2015 at 7:22 PM, null
I've been having a (friendly) argument with a friend who is an old-school
OOP programmer. He insists that you need objects to make large-scale
codebases legible and maintainable over the long run. Quite apart from
this argument's virtues or lack thereof, this made me curious -- what are
the
Eastwood, the Clojure lint tool, version 0.2.2 has been released. See
install instructions and complete documentation at [1].
Below are some of the changes since version 0.2.1. A complete list is at
[2].
Go squash some bugs!
Jonas Enlund, Nicola Mometto, and Andy Fingerhut
[1]
It's funny, because most of the larger OOP projects I worked on were large
because of class bloat, not because of business concerns. For example, the
C# app I used to work on was a more or less simple CRUD app. We had a ORM
that served up objects to a Silverlight UI. So if we wanted to display
Wonderful screencasts! I'll use it to shock people!
Thank you very much for this work,
Andrea.
--
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
Exactly this. I couldn’t find a reliable way of counting LOC but my
(Clojure/ClojureSciprt) src tree (excluding test) in the project I have to hand
is 1.5MB.
> On 15 Nov 2015, at 21:27, Timothy Baldridge wrote:
>
> It's funny, because most of the larger OOP projects I
I use cloc(http://cloc.sourceforge.net/) to counting the LOC of our
projects, it's total about 41025 lines of Clojure code.
2015-11-16 7:22 GMT+08:00 Colin Yates :
> Exactly this. I couldn’t find a reliable way of counting LOC but my
> (Clojure/ClojureSciprt) src
Sorry, that link to the docs on the new wrong pre/post-condition linter
should have been: https://github.com/jonase/eastwood#wrong-pre-post
Andy
On Sun, Nov 15, 2015 at 1:25 PM, Andy Fingerhut
wrote:
> Eastwood, the Clojure lint tool, version 0.2.2 has been released.
With updates I have made in the latest release of Eastwood 0.2.2 (announced
in a separate message), I am seeing pretty much identical linting results
running Eastwood on about 80 Clojure contrib and 3rd party libraries when
using Clojure 1.8.0-RC1 as I see with Clojure 1.7.0. The run time is
Cool, thanks for doing these!
Bill
On Sunday, November 15, 2015 at 11:15:46 AM UTC-8, Magnar Sveen wrote:
>
> I've made a short video series on writing a game with Clojure and
> ClojureScript. The last episode is out today, so the series is complete.
> Hope you find some entertainment in it.
I'm reminded of the old joke: to err is human; to really screw up you need
a computer (read: OO).
On Nov 15, 2015 3:27 PM, "Timothy Baldridge" wrote:
> It's funny, because most of the larger OOP projects I worked on were large
> because of class bloat, not because of
Tom, would you be able to run your performance regression suite against 1.8
with direct linking enabled and share the performance changes?
On Mon, Nov 16, 2015 at 1:19 PM Andy Fingerhut
wrote:
> With updates I have made in the latest release of Eastwood 0.2.2
>
Thank you so much for the effort you put on these screencasts. There's so
much for me to learn from them!
Best,
Denis
El domingo, 15 de noviembre de 2015, 11:15:46 (UTC-8), Magnar Sveen
escribió:
>
> I've made a short video series on writing a game with Clojure and
> ClojureScript. The last
user=> (def obj (Object.))
#'user/obj
user=> (defmacro mac1 [& body] `(locking ~obj ~@body))
#'user/mac1
user=> (mac1 nil)
CompilerException java.lang.RuntimeException: Can't embed object in code,
maybe print-dup not defined: java.lang.Object@2a747a37,
compiling:(NO_SOURCE_PATH:1:1)
Why am I
I think the reason is in macroexpand-1 result:
user=> (macroexpand-1 '(mac1 1))
(clojure.core/locking # 1)
It's not a valid form to be read and eval by clojure reader,the object form
can't be parsed.
If define obj to be a map {}, it works fine:
user=> (def obj {})
#'user/obj
user=> (mac1 1)
1
The problem here is that you are splicing in obj when there is no need to.
You actually want your generated code to refer to obj. So just
(defmacro mac1 [& body] `(locking obj ~@body))
is fine.
dennis' solution will work too, but it will work almost accidentally? All
blank maps evaluate to the
I've made a short video series on writing a game with Clojure and
ClojureScript. The last episode is out today, so the series is complete.
Hope you find some entertainment in it. :-)
http://www.parens-of-the-dead.com/
- Magnar
--
You received this message because you are subscribed to the
17 matches
Mail list logo