I find the idea of using a special filename extension rather
appealing. A couple of notes:
(1) I'm not sure there is a "generic clojure". ClojureScript has a
couple serious differences from Clojure, such as the way macros are
included in (ns ...).
(2) ClojureScript macro files, AFAICT, really a
On Jan 19, 12:55 pm, Dave Sann wrote:
> If you are referring to (2), I agree.
>
> But marking the type of a file by either path or extension is not a hack,
> in my opinion. (3)
> I was suggesting that ideally this would be better.
I meant it for #2. Thanks for clarifying the details.
Shantanu
If you are referring to (2), I agree.
But marking the type of a file by either path or extension is not a hack,
in my opinion. (3)
I was suggesting that ideally this would be better.
To justify this statement I would claim that:
jvm clj files - using java platform specifics
clr clj fil
> * Explicitly declaring crossovers. I think that this is decouples the code
> from it's intended purpose. It will be easy to get out of sync and cause
> problems.
>
> As I see it, there are three solutions available for this problem
>
> 1. declare externally as you have done
> 2. declare internall
Hi,
There is one more thing that I am a little wary of.
Please don't take these comments as negative - I think that this project is
good and the community needs to get to a solid solution.
* Explicitly declaring crossovers. I think that this is decouples the code
from it's intended purpose. It
On Tuesday, 17 January 2012 20:35:17 UTC+11, Evan Mezeske wrote:
>
>
> >
> > 1. I am wary of the copying of cls -> cljs files in the src tree. Due to
> > the (inevitable at some point) confusion over which code is authored as
>
>
> I'd love to hear other ideas.
>
I have a version of cljs-wat
On Jan 16, 5:09 pm, Dave Sann wrote:
> This looks interesting.
>
> I have a couple of comments and questions:
>
> 1. I am wary of the copying of cls -> cljs files in the src tree. Due to
> the (inevitable at some point) confusion over which code is authored as
> cljs and which copied. I really thi
> 1. I am wary of the copying of cls -> cljs files in the src tree. Due to
> the (inevitable at some point) confusion over which code is authored as
> cljs and which copied. I really think that these need to be kept separate
> (somehow).
I think one clean solution may be to:
1. Split the common pa
This looks interesting.
I have a couple of comments and questions:
1. I am wary of the copying of cls -> cljs files in the src tree. Due to
the (inevitable at some point) confusion over which code is authored as
cljs and which copied. I really think that these need to be kept separate
(somehow
Hello,
I just pushed out the first release of my new lein plugin, lein-
cljsbuild. It adds a lein task that can either build your
ClojureScript one time, or watch for modifications and automatically
build it when necessary (like cljs-watch). It also has support for
hooking into the "lein compile
10 matches
Mail list logo
