Hi Nicola,
This is great stuff. Are there plans for a tools.emitter.js?
Thanks,
Michael
--
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 -
Hi, Alex.
I'll send you a few thoughts on this. The reader problem is the biggest
issue.
-David
On Thursday, August 21, 2014 8:01:29 PM UTC-5, Alex Miller wrote:
Hey David,
I'm working on the feature expressions stuff. At the moment I've been
focusing on the clj/cljs use case as that
David,
I personally have no plans to port tools.analyzer.jvm to a
tools.analyzer.clr, not for disinterest but simply because I don't know
anything about the .NET platform nor about clojureCLR.
That said, it shouldn't be hard to port it at all, the main file to port
would be
Nicola,
Thanks for the very helpful comments.
I'll likely proceed with the translation -- there are calls to get
core.async sync'ed up with the JVM version and tools.analyzer.* has to be
there.
Thanks for pointing me to the feature expressions discussion. That will be
extremely useful,
Hey David,
I'm working on the feature expressions stuff. At the moment I've been focusing
on the clj/cljs use case as that seems to be most urgent. I had been planning
to circle back around to clr eventually though and would be very interested in
any known issues.
Alex
--
You received this
Hi Alex,
Is the current feature expressions design basically what's under Proposed
Solution: feature expressions at
http://dev.clojure.org/display/design/Feature+Expressions? I read through
the comments a while back and a lot of the suggestions there got fairly
complicated, I'd be interested to
Nicola,
of course you're right.
I recently switched to the 3-ary analyze in order to
use :validate/wrong-tag-handler and I was wrongly passing {} as the env,
instead of (empty-env).
When I saw the Invalid token: ::a/b errors I was fooled into thinking
they were purely syntactical errors (but
Nicola,
Excellent work!
Looking forward to seeing tools.analyzer.clr in the near future. :)
Well, actually, seriously, with the use of tools.analyzer.* in critical
projects such as core.async, a port of tools.analyzer.jvm seems necessary.
Unless you know of plans to make a port, I'll add it
Nicola,
thank you for your work, and for :validate/wrong-tag-handler specifically,
which is very useful to me.
It seems that analyzer refuses keywords in the form ::a/b, which are used
in some projects
(e.g. [org.clojure/core.typed] clojure.core.typed.check.fn contains
::t/cmethods at line
Nicola,
thank you for your work, and for :validate/wrong-tag-handler specifically,
which is very useful to me.
It seems that analyzer refuses keywords in the form ::a/b, which are used
in some projects
(e.g. [org.clojure/core.typed] clojure.core.typed.check.fn contains
::t/cmethods at line
Francesco,
that doesn't seem to be the case in my tests:
[~/src/tools.analyzer.jvm/src/main/clojure] cat test.clj
(ns test (:require [clojure.string :as s]))
::s/foo
clojure.tools.analyzer.jvm (- (analyze-ns 'test) last :form)
:clojure.string/foo
Note that to analyze keywords in the form
You rule Nicola! I really appreciate all of the work you've put into this.
Your code has forever influenced the way I write lexical analyzers with
Clojure. :)
On Wednesday, August 13, 2014 12:54:54 PM UTC-4, Nicola Mometto wrote:
As some of you might know, I've been working contiuously on my
This looks really 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 moderated - please be patient with your
first post.
To unsubscribe from this
Keep up the great work Nicola.
On Wednesday, August 13, 2014 12:54:54 PM UTC-4, Nicola Mometto wrote:
As some of you might know, I've been working contiuously on my various
tools.* contrib libraries for the past months and I've recently added
tools.analyzer.js to the list of contrib
14 matches
Mail list logo
