Interesting, I think I kinda grok what you're saying. I'll keep tabs on this,
though it's unlikely that I'll have to work on this level of abstraction (:
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@goo
OOPS! Manifest error.
Released as 0.0.2. Tested the result. Everything runs again.
Also defined a deploy-release task in boot.build to make releasing a bit
easier. The release is a tad non-standard because of the need to include a
.hl file.
--
You received this message because you are subscri
Notify is focused on sending server-side notifications to the client for
applications building on hoplon and castra. The idea is to have a single
poll loop (for now) and to send changes (in the form of notifications)
rather than snapshots of server state. Notifications are sequenced and sent
in
Hi Yuri,
I followed to the CLJ bug and as far as I understood Alex said that clojure
is not related to this. This is also my thinking. NTF has different
semantics regarding file locking than linux. And I guess that's the
problem, probably the adzerk team never tried it on windows themselves.
D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26.12.2015 00:51, Jethro Kuan Sheng Yuan wrote:
> Have you seen castra before? Seems like both are trying to achieve
> the same objective.
>
No, I haven't seen it before. Thanks for pointing it out. I probably
haven't communicated the objective of
On Tue, Dec 22, 2015 at 10:57 AM, Artur Malabarba
wrote:
> Hi Timothy,
> Glad you liked it! :-)
>
> > The only thing I'm wondering, is if the debugger has:
> > a step into function
>
> Not yet. :-(
> For now, you can instrument in advance the function you want to step into.
>
> > ability to set a
Hi, Mian Pao.
When you call the macro te, a is bound to the *symbol* 'print, not the
*function* print. So, what the ~(a b c) form is doing is calling the
symbol 'print as a function:
('print 1 '(2 3)) => '(2 3)
This is because symbols and keywords implement the function interface, and
the cal
Hi, Mian Pao.
When you call the macro te, a is bound to the *symbol* 'print, not the
*function* print. So, what the ~(a b c) form is doing is calling the
symbol 'print as a function:
('print 1 '(2 3)) => '(2 3)
This is because symbols and keywords implement the function interface, and
the cal
>From what I understand by looking at the Boot file access bugs, they are
>actually Clojure problems (open file leaks) fixed in 1.8, so you might want to
>give it a try using 1.8 Release Candidate.
Cheers……..Yuri
From: 'Sven Richter' via ClojureScript
Sent: Friday, December 25, 2015 1:08 PM
https://github.com/FrankC01/clasew
*clasew *- Clojure AppleScriptEngine Wrapper
*Intent* - clasew provides an idiomatic Clojure wrapper for Java
ScriptManager: specifically apple.AppleScriptManager, as well as providing
scriptable applications HOF DSLs.
Realizing that the audience for such capa
This isn't a schema issue. Without invoking Schema:
user> (do (defrecord Foo []) Foo)
user.Foo
user> (clojure.pprint/pprint (do (defrecord Foo2 []) Foo2))
CompilerException java.lang.RuntimeException: Unable to resolve symbol: Foo2 in
this context,
compiling:(/private/var/folders/_g/_nhxhpvn24
11 matches
Mail list logo
