you can use the *compile-files* flag
if you need to differentiate compiling versus running contexts.
This will be useful if you use AOT to create class files for later packaging.
This flag is useful to avoid global code chunks to run when they create
side effects (runtime inits, ...). You do not w
Hi,
Clojure reads a file toplevel expression after toplevel expression and
compiles and executes them separately (exception: toplevel "do" is split
into its sub-expressions). The fact that things are stored in a file is
just a coincidence. You can just as well type everything into the repl
man
On Thu, Feb 23, 2012 at 8:23 PM, Andreas Kostler
wrote:
> Bump...I'm interested in this, too...
>
> On 21 February 2012 12:29, T.Y Chew wrote:
>>
>> Hi all,
>>
>> I had a question about clojure's compilation model, which my co-worker
>> suggest to redirect here :-)
>>
>> I wonder what clojure doe
Bump...I'm interested in this, too...
On 21 February 2012 12:29, T.Y Chew wrote:
>
>
> Hi all,
>
> I had a question about clojure's compilation model, which my co-worker
> suggest to redirect here :-)
>
> I wonder what clojure does during compilation of a file? Can
> side-effects occur (definiti
