Reports of the death of ClojureCLR are greatly exaggerated.
The newframework branch in the repo has a completed 1.10 version running on
.Net Core 3.1 and 5.
Should be released 'soon'.
On Wednesday, November 18, 2020 at 1:20:54 AM UTC-6 oleksand...@zalando.de
wrote:
> On Tue, Nov 17, 2020 at
As mentioned, you likely will get more respone on the clojure-clr group.
The subject of this post mentions .net core. From my understanding, you
will not get ClojureCLR working on .Net Core on any platform due to Core's
lack of support for System.Reflection.Emit.
Alan correctly mentions Arcadi
Most documentation, such as it is, is on the github wiki:
https://github.com/clojure/clojure-clr/wiki
Nothing written recently on such things as deploying web services.
There is a separate list for ClojureCLR where you might get more
answers: https://groups.google.com/forum/#!forum/clojure-clr
Not completely functional and not thoroughly tested.
Several tests still fail -- the most important one being interrupting an
eval. (I know what the fix is, but haven't had the time.)
On Wednesday, May 6, 2015 at 3:58:34 PM UTC-5, Alex Miller wrote:
>
> https://github.com/clojure/clr.tools.nrep
>
>
> Also, how does this work on ClojureCLR or ClojureScript? Neither of those
> platforms has a java.io.PushbackReader, and I'm not even sure what the
> equivalent of the clojure.java.io namespace is for them, unless the
> "java" in that name is misleading.
>
>
ClojureCLR implements Pushback
The slower startup time has nothing to do with DLR, I think. It is all
about doing JIT on load and loading full assemblies.
ClojureCLR starts VERY quickly if you NGEN it.
This was addressed
here:http://clojureclr.blogspot.com/2011/12/using-ngen-to-improve-clojureclr.html
And more recently on
Re versions: look at the tags, not the branches. The 1.4.1 branch was
anomalous, due to needing to get out a bug fix.
On Tuesday, November 11, 2014 2:17:29 PM UTC-6, Aaron wrote:
>
> Hi Adrian,
>
> I'll share some of my experiences.
>
> * Is Clojure CLR production ready?
> Yes, I have been usin
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 th
his is http://dev.clojure.org/jira/browse/CLJ-1298
>
> In any case, if you want to go ahead and start porting t.a.jvm to
> t.a.clr until we wait for 1.7 and feature-expressions or `c.c/pattern?`,
> feel free to contact me privately and we can discuss this further.
>
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
ClojureCLR now has its own Google group for discussions.
https://groups.google.com/forum/#!forum/clojure-clr
Please use this new forum for ClojureCLR-specific questions, suggestions,
requests related to usage, development, tooling etc.
ClojureCLR-specific announcements will be the new list.
Not functional yet. About 50-60% completed.
I ran into some bugs -- it turns out that sockets in JVM and CLR are not
exactly identical, no great surprise -- and got distracted by versions 1.5
and 1.6alpha and support for mono and nuget for ClojureCLR.
I plan to finish the core.async port (it's a
On Sunday, November 24, 2013 6:56:07 AM UTC-6, Shantanu Kumar wrote:
>
> I am trying to run some tests (that worked fine with Mono+ClojureCLR
> 1.4.1) in Mono+ClojureCLR 1.5.0 from SourceForge and finding the below
> exception:
>
> $ # CLOJURE_LOAD_PATH is configured properly
> $ mono "/path/to/c
I guess it doesn't matter that it works fine for me if it doesn't for you.
:)
I'll post an issue.
Along with many other Clojure projects, issues and related items are on the
JIRA site under dev.clojure.org.
For ClojureCLR, that is at http://dev.clojure.org/jira/browse/CLJCLR
-David
On Tuesday,
1.5.0 of Clojure CLR includes the one fix in 1.5.1. I got excited and went
one too far. Normally, the version numbers match exactly.
I tagged 1.5.0 a little prematurely. We had some troubles on the NuGet
release and on the mono build. I wasn't really ready for an official 1.5.0
release, so I
ClojureCLR follows ClojureJVM in translating hyphens in namespace names to
underscores in filenames.
-David
On Tuesday, November 19, 2013 11:00:37 AM UTC-6, Frank Hale wrote:
>
> Thanks Shantanu, I will look into lein-clr.
>
>
> On Tue, Nov 19, 2013 at 11:57 AM, Frank Hale
> > wrote:
>
>> Ugh,
On Thursday, June 6, 2013 1:55:13 AM UTC-5, Zed Becker wrote:
>
> Why do the languages running on the CLR (ironRuby, ironPython, ironScheme,
> ScalaCLR) do not get to live long enough in the sunshine, whereas same
> languages get embraced by the Java runtime, and live in the limelight?
>
Many
>
> Thanks,
> Ambrose
>
> On Fri, Mar 22, 2013 at 8:11 PM, dmiller
> > wrote:
>
>> I've not seen that behavior on ClojureCLR/Mono before.
>>
>> What ClojureCLR commit are you using?
>>
>>
>> On Thursday, March 21, 2013 10:42:52 PM
il.com > wrote:
>
>> Hi David,
>>
>> Excellent work so far!
>>
>> I'll have a dig around and see what I find.
>>
>> Thanks,
>> Ambrose
>>
>>
>> On Fri, Mar 22, 2013 at 10:53 AM, dmiller
>> > wrote:
>>
>
Last update on this here:
The port of core.logic to ClojureCLR that resides here:
https://github.com/dmiller/clr.core.logic
the datomic piece is not ported.
All tests run EXCEPT:
test-binding-map-*
test-binding-map-as-1
test-binding-map-constraints-1
test-unifier-constraints-*
test
I started a port of core.logic to ClojureCLR.
Repo: https://github.com/dmiller/clr.core.logic
It is not finished yet. All files load with two exceptions.
(1) I have not ported clojure.core.logic.datomic
(2) there is a problem in the finite domain code with extending fd to the
integer types
core.logic should be trivial to port to ClojureCLR.
Based on a quick scan, a few changes to JVM lib calls, mostly .write =>
.Write, a few type hints, UUID => GUID.
Could be done in short order.
This would be an easy example to play with a common source for Clojure(JVM
| CLR).
-David
On Tuesd
Fixed in master.
> On Tuesday, March 12, 2013 11:43:58 PM UTC-5, FC wrote:
>>
>> Hi,
>>
>> I'm trying to build ClojureCLR from the latest clojure-clr-master.ZIP
>> file I downloaded from GitHub.
>>
>> With "Debug 3.5" as the build configuration I get a compilation error in
>> Clojure\lib\RT.c
Oops. Forgot to do a test build on 3.5 for that one. I need to
conditionalize that call.
I'll try to commit a patch for that tonight.
-David
On Tuesday, March 12, 2013 11:43:58 PM UTC-5, FC wrote:
>
> Hi,
>
> I'm trying to build ClojureCLR from the latest clojure-clr-master.ZIP file
> I downl
Judging from the transcript, there is something not right in your
ClojureCLR setup.
protocols.clj should not be loading. It should be AOT-compiled.
We can work from the JIRA ticket.
-David
On Wednesday, February 20, 2013 3:30:52 PM UTC-6, Frank Hale wrote:
>
> Thank you. New ticket created.
>
ClojureCLR abides by the same restrictions on submitting code as the main
Clojure project. Meaning that contribute code directly to ClojureCLR, you
need a Contributor Agreement with Rich Hickey.
Check out http://clojure.org/contributing.
Doing so will allow you access to the JIRA site, which is
That most likely is due to NUnit not being installed in lib/ properly.
--
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 wit
*
If you are running into this problem with 1.5RC1 under Mono 3, let me know.
This would be anomalous. (but the step above should make it work)
-David
On Thursday, January 3, 2013 2:26:37 AM UTC-6, Konrad Hinsen wrote:
>
> dmiller writes:
>
> > Building from souce on *nix/M
I believe RobertJ and some others are looking into automating this.
A real solution needs to coordinate nuget in Visual Studio versus nuget in
mono-land (the build scripts already handle mono vs ms) and bring lein-clr
along so that building clojure-clr itself is not too distinct from building
ap
atform="Any CPU"
After the build the binaries will be located in
"clojure-clr/bin/4.0\{Release || Debug}"
Do
mono Clojure.Main.exe
to run.
-David
On Tuesday, January 1, 2013 10:31:33 AM UTC-6, Konrad Hinsen wrote:
>
> dmiller writes:
>
> > A casualty of
I can tell, getting
nuget running in a *nix/Mono environment is still not trivial.
-David
On Monday, December 31, 2012 8:25:28 AM UTC-6, Konrad Hinsen wrote:
>
> dmiller writes:
>
> > The executables and DLLs under the regular binary download will work
> just fine under
>
The executables and DLLs under the regular binary download will work just
fine under Mono.
On Saturday, December 29, 2012 2:06:31 AM UTC-6, Shantanu Kumar wrote:
>
>
>
> On Thursday, 27 December 2012 23:15:04 UTC+5:30, dmiller wrote:
>>
>> ClojureCLR is caught up with a
ClojureCLR is caught up with all changes to ClojureJVM up to 1.5.0-RC1.
This includes all relevant bug fixes, the reducers library, reader literal
improvements, new threading macros and other goodness. See changes.md.
The only change not yet implemented is the new reliance on the
test.generativ
>>
>> I will post the exact steps in the evening on how to replicate the issue
>> on 32-bit Ubuntu.
>>
>> Shantanu
>>
>> On Wednesday, 19 December 2012 02:00:53 UTC+5:30, dmiller wrote:
>>>
>>> Shantanu,
>>>
>>
Shantanu,
I created an Ubuntu 12.10 VM running in VirtualBox on my Win7 PC.
I installed Mono 2.10.8.
I downloaded the zip for ClojureCLR 1.4.0 Debug-4.0.
Extracted.
> mono Clojure.Main.exe
Runs with no problem.
> mono Clojure.Compile.exe test.junk
Runs with no problem.
>From the errors you r
Shantanu,
I don't have a Linux box available at this point to test, but I'll try it
on Mac w/ Mono when I get a chance.
I don't have a clue how a field disappears between platforms.
-David
On Saturday, December 15, 2012 10:15:21 PM UTC-6, Shantanu Kumar wrote:
>
> Hi,
>
> I noticed the followi
Aaron,
tools.logging and nrepl are important. I'm glad to see the effort.
I haven't forgotten about your single-DLL work.
I'm going to have plenty of time next week if you can get something to me.
-David
On Saturday, December 15, 2012 5:15:16 PM UTC-6, Aaron wrote:
>
> Cool. I'm just seeing
On Saturday, December 15, 2012 3:27:26 PM UTC-6, Shantanu Kumar wrote:
>
> Hi,
>
> Thought to bring up the recent ClojureCLR binary download issue:
>
> 1. The http://clojure.org/ homepage links ClojureCLR to the old Github
> repo.
>
Whoever maintains the homepage will have to fix this. Note: t
Patched in master branch.
Clojure 1.5.0-master-SNAPSHOT
user=>
user=> (defn bar [^Double d] d)
#'user/bar
user=> (defn baz [^System.Double d] d)
#'user/baz
user=> (bar 1.2)
1.2
user=> (baz 1.2)
1.2
user=> (defprotocol FP (foo [_]))
FP
user=> (extend-protocol FP System.Double (foo [d] d))
nil
user=
user=> (defn f [^Double x] x)
#'user/f
user=> (defn g [^double x] x)
#'user/g
user=> (f 1.0)
2.15078317008181E-316# GASP!
user=> (g 1.0)
1.0# CROWD APPLAUDS!
As you can see, there is a workaround: use ^double, not ^Double. This
Robert, Scott:
Fixed on the master branch.
Tripped up by CLR's strange convention for indicating method accessibility.
[sotto voce]: Just because a method has the Private flag set, don't think
the IsPrivate property is true. It can be IsAssembly instead.
[Deeply felt]: Sigh.
-David
On T
, November 16, 2012 8:46:01 AM UTC-6, ffailla wrote:
>
> Thank you David for looking into this so quickly. For now I am working
> around this by not destructuring, but I look forward to the patch. Thanks.
>
> -Frank
>
> On Thursday, November 15, 2012 7:41:39 PM UTC-5, dmi
Fiel,
Fixed on the master branch as of this morning.
-David
On Saturday, November 17, 2012 7:46:47 AM UTC-6, FC wrote:
>
> Hi DavidM and ClojureCLR users,
>
> In ClojureCLR built using .NET 3.5 framework, with-open needs some help
> finding the .Dispose method on IDisposable objects:
>
> It oc
The compiler uses recursive descent in its analysis. Given a VM call stack
that does not grow, there will always been some input that causes the
compiler to blow stack. In the case of cond, the macro expands into a
nested if statements. Given enough clauses, you get the result you have
exper
Shantanu,
This has been much requested. I plan to give a test-drive over the
imminent holiday weekend.
-David
On Sunday, November 18, 2012 3:03:03 PM UTC-6, Shantanu Kumar wrote:
>
> Hi,
>
> I pushed lein-clr 0.2.0 https://github.com/kumarshantanu/lein-clr JARs to
> Clojars a little while
The difference is that the JVM version is correct and the CLR
implementation has a bug.
I'll fix it in the current branch and try to get a patched 1.4 out as soon
as I can.
-- Above is all you really need to know, but I find myself forced to
continue. :) --
This bug has sitting there from the
On Thursday, April 19, 2012 11:20:05 AM UTC-5, tbc++ wrote:
>
> If you AOT compile the ClojureCLR code, will it still depend on
> Reflection.Emit?
>
> Timothy
>
Yes, it will still depend on Reflection.Emit. If you eval, you need it.
Also, any place where ClojureJVM does runtime reflection, Clo
I believe that Reflection.Emit is not available in .Net Compact Framework.
This is essential for the ClojureCLR. This also prevents DLR-based
languages such as IronPython from running on .Net CF.
-David
On Thursday, April 19, 2012 3:11:02 AM UTC-5, David Jagoe wrote:
>
> Hi all,
>
> Does any
We discovered this was due to building on the beta of .Net 4.5. ClojureCLR
has not been updated to 4.5 yet.
In this case, a new method was introduced in an interface, causing the
proxy to have a missing method.
4.5 support coming 'real soon now'.
-David
On Tuesday, April 17, 2012 10:04:14 A
On Friday, April 6, 2012 6:23:43 PM UTC-5, Aaron wrote:
>
> I think it's a goal to get Clojure.dll on nuget soon, but it hasn't
> happened yet. Hopefully soon. Still, we'll need a good build system for
> ClojureCLR that does everything that lein does. But, I don't think that
> should be tha
On Jan 19, 10:25 pm, jayvandal wrote:
> Why does the clr point to d: work?
> user=> (use :reload 'ui)
> FileNotFoundException Could not locate db.mysql.clj.dll or db/
> mysql.clj on load
> path. clojure.lang.RT.load (d:\work\clojure-clr\Clojure\Clojure\Lib
> \RT.cs:3065)
It is not looking in d:\
It shouldn't, obviously. It appears to be holding on to a compile-
time value somewhere. I'll track it down this weekend.
-David
On Jan 19, 10:25 pm, jayvandal wrote:
> Why does the clr point to d: work?
> user=> (use :reload 'ui)
> FileNotFoundException Could not locate db.mysql.clj.dll or d
Thanks.
I hope 2012 is the year for community building for ClojureCLR, And
maybe some IDE building.
-David
On Jan 1, 12:32 pm, rippinrobr wrote:
> I would also like to thank David for his work on ClojureCLR.
> ClojureCLR is going to make
> for a great 2012 for me!
>
> -Rob Rowe
>
> On Jan 1,
>
> [1] Mono –http://www.mono-project.com/Main_Page
>
> Regards,
> Shantanu
>
> On Dec 30, 9:41 pm, dmiller wrote:
>
>
>
>
>
>
>
> > As noted, the biggest difference is interop. I've started posting on
> > such matters athttp://clojure
arted with
ClojureCLR.
-David
On Dec 30, 12:20 am, 王亚平 wrote:
> Why God like dmiller don't write such a book? It must be very interesting.
>
>
>
>
>
>
>
> On Tue, Nov 29, 2011 at 8:45 AM, dmiller wrote:
> > The wiki on the github repo has some information about gettin
ClojureCLR has a new home!
Code repo: https://github.com/clojure/clojure-clr
JIRA: http://dev.clojure.org/jira/browse/CLJCLR
Old binary distributions for versions 1.1 and 1.2 will continue to be
available at the old repo (https://github.com/richhickey/clojure-clr)
for the time being.
The new re
Fiel's problem was a little simpler -- his dllimport method was out in
C# class that was imported. The problem appears to be that reflection
is not finding the method. That is likely either a signature-matching
problem (declared args vs supplied params) or even just having the
flags set a little w
Not supported at present.
I'd have to think a little about it, but at first glance, it seems
doable. I've not look under the surface at how the CLR handles
PInvoke via DLLImport, so some investigation is required.
Attributes are supported on method defs in various places (but not yet
documented)
The wiki on the github repo has some information about getting started
and how to accomplish some interop that is special to CLR.
https://github.com/richhickey/clojure-clr/wiki
and make sure to look at
https://github.com/richhickey/clojure-clr/wiki/_pages
for the complete list.
Rob Rowe (http:
On Nov 17, 10:07 am, Timothy Baldridge wrote:
> > With the clojureclr for example, it
> > supports pretty much everything clojure does sans java, and gains all the
> > .net interop.
>
> True...true, it supports it, but it's still a "2nd class citizen". For
> instance, we don't have lein, ring, p
I'm sure CL syntax will work for my needs.
I'm not sure that anyone will like how I might use it to make code
more portable. :)
That could also stand some discussion.
Almost OT, ClojureCLR already extends the reader syntax to accommodate
symbols naming types with really bad characters in them, us
against java.io have helped. Not
much. Copy and edit is about the only real solution.
I've probably said too much already.
-David
On Nov 3, 12:54 pm, Sean Corfield wrote:
> On Thu, Nov 3, 2011 at 10:35 AM, dmiller wrote:
> > An analysis of the 2011 ClojureCLR survey and a plan o
An analysis of the 2011 ClojureCLR survey and a plan of action is now
available here:
http://clojureclr.blogspot.com/2011/11/survey-says-call-to-action.html
Consider this also notification that the ClojureCLR blog exists. You
can turn your dial there for future updates.
-David
--
You received
A summary of the responses to the recent ClojureCLR survey is
available at
http://clojureclr.blogspot.com/2011/11/results-of-2011-clojureclr-survey.html
This is only a summary of the data. Editorializing, conclusion-izing
and other opinion-izing will come later.
-David
--
You received this me
ClojureCLR survey closing tonight at midnight my time (Central
Daylight Time).
On Oct 26, 12:22 pm, dmiller wrote:
> Keep those cards and letters coming.
>
> Just a reminder that time is running out on participating in the
> ClojureCLRsurvey.
>
> I put in a BOF request for
That is an side effect of changes that were made to naming/location of
the assemblies output from compilation.
Whether it's a feature or bug depends on how hard it is to change. :)
Issue posted.
-David
On Oct 29, 6:58 am, Ian wrote:
> Hi all,
>
> In Clojure 1.2.0, if I run a command like:
>
help drive the conversation.
-David
On Oct 22, 11:43 pm, dmiller wrote:
> Inspired by Chas Emerick's Clojure surveys, I have created a survey to
> assess the experiences and needs of (potential or actual) users of
> ClojureCLR. Building community and lowering barriers to ad
Inspired by Chas Emerick's Clojure surveys, I have created a survey to
assess the experiences and needs of (potential or actual) users of
ClojureCLR. Building community and lowering barriers to adoption have
to be priorities for this project. I hope this survey will provide
some guidance for this
ClojureCLR 1.3.0 is now available.
Same updates as Clojure 1.3.0.
Same acknowledgments, as this depends on the work of all those fine
people who bring you Clojure on the JVM.
Additional acknowledgments:
- Kurt Schelfthout
- Shawn Hoover
- David Powell
- Alan Salewski
To get started with a binar
I would be concerned about this group, if there was any evidence of
existence.
On Aug 19, 2:59 am, Ken Wesson wrote:
> And, maybe, the ones who have to go and reconfigure everything when
> they upgrade ...
>
--
You received this message because you are subscribed to the Google
Groups "Clojure"
Several comments:
(a) 'clojure.load.path' is not new in 1.3. It's been in the code
since at least May, 2009.
(b) Regarding Dimitre's comment below, I probably did have Java system
properties on my mind at the time. I guarantee that I was not
thinking of picking Bash-compliant names. I doubt tha
It is the same for ClojureCLR.
-David
On Aug 2, 8:22 am, "Meikel Brandmeyer (kotarak)"
wrote:
> Hi,
>
> Am Dienstag, 2. August 2011 11:03:31 UTC+2 schrieb Ralph Moritz:
>
>
>
> > (defn details []
> > (let [hash (System.Collections.Hashtable.)]
> > (doto hash
> > (. Ad
Reloading will definitely cause a problem.
According to MS docs:
"Only one instance of the Application class can be created per
AppDomain, to ensure shared access to a single set of application-
scope window, property, and resource data. Consequently, the default
constructor of the Application cl
No signed assemblies.
What got you below the reported JIT activity into the real problem?
On Mar 18, 11:37 am, Scott Thoman wrote:
> I've had a similar issue unrelated to clojure. In my case we had some
> signed assemblies and the CLR was taking a long time, in certain
> environments, to go ou
core.clj and company are AOT-compiled. The dll's are loaded during
startup, not the clojure source.
When I run a profiler on it during startup, it reports almost all time
being taken by the JITter.
I'm open to suggestions on improving this. In particular, more
detailed profiling information woul
I hesitate to modify the inheritance structure of Clojure's
interfaces.
ClojureCLR does follow ClojureJVM in providing support for these
interfaces in the abstract base classes underlying things such as
PersistentTreeMap.
In ClojureCLR 1.3-alpha:
public class PersistentTreeMap : APersistentMap, I
into clojure.core.clj.dll. This dll can go directly into the
application's base directory. This change solves some problems that
I won't bore anyone with.
-David
On Mar 3, 8:23 pm, Timothy Pratley wrote:
> On Wed, Mar 2, 2011 at 8:39 AM, dmiller wrote:
> > (1) I think the copy solutio
(1) I think the copy solution is the easiest. ClojureCLR deals with
its dependencies on the DLR dlls exactly as you describe, with custom
build step to copy DLLs from a lib directory. You will need a project
reference at least to Clojure.dll. You will need the files in
clojure/ subdirectory co
Done.
Thanks for pointing this out.
-David
On Feb 10, 3:42 pm, Robin Munn wrote:
> I just ran into an interesting problem installing the Clojure-CLR 1.3
> alpha
> (https://github.com/downloads/richhickey/clojure-clr/clojure-clr-1.3.0...)
> on an XP machine with .Net 4.0 installed. Downloading
I've made a change to the naming and location of AOT-compiled
assemblies generated by ClojureCLR.
Previously, ClojureCLR had followed the conventions of ClojureJVM in
naming/locating class files (assemblies in CLR-land) generated by AOT-
compilation. Thus, doing (compile 'a.b.c) would find sourc
Specifically, in ClojureCLR< property access in CLR interop is treated
in the same way as fields and zero-arity methods.
For class properties, ClassName/PropertyName works.
For instance properties, (.PropertyName instance) or (. instance
PropertyName)
In essence, fields, properties and zero-arit
On Nov 24, 1:24 pm, Ken Wesson wrote:
> I gave some thought to the Integer vs. Int32 issue.
>
> I think what would help here is a way to alias classes when :importing them.
>
> It would require tweaking the ns macro and possibly parts of the
> runtime. The outcome would be to allow something lik
9:08 am, Sean Devlin wrote:
> What is the full path of that program in the 1.2.0 bundle? I can't
> seem to find it.
>
> On Oct 27, 4:23 pm, dmiller wrote:
>
> > Let me know on the error.
>
> > Re REPL: run Clojure.Main.exe to start.
>
> > -David
>
>
Let me know on the error.
Re REPL: run Clojure.Main.exe to start.
-David
On Oct 27, 2:54 pm, Sean Devlin wrote:
> So, I just started running w/ Clojrue CLR. I'm trying to get 1.2 up
> and running. I followed the instructions here:
>
> http://github.com/richhickey/clojure-clr/wiki/Getting-star
ClojureCLR can now be compiled to run under either .NET 3.5 or .NET
4.0. To support this, development is now under Visual Studio 2010.
The build process has been improved (thanks to Kurt Schelfthout).
Among other improvements, it will be easier for those wanting to play
to get started.
To get st
dates on this?
>
> Mike
>
> On Sep 24, 8:24 am, dmiller wrote:
>
> > Just waiting for that person's CA to be processed by Rich.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email
I tagged a 1.2 release on the site.
I have not put a separate 1.2 download or a binary release out there
yet. Someone has contributed an entirely new build process for
ClojureCLR that includes support for either 3.5 or 4.0 builds, better
binary managment on the builds and some other goodies. Jus
I have two things left to do to bring ClojureCLR mostly up to 1.2RC3:
implement gvec and one other commit on map/record equality. The
latter is 20 minutes. The former, gvec, is mostly done, but I ran
into a little compiler glitch I have to fix.
At the moment, I run all relevant clojure-test test
I'm in favor of any discussion that yields more support for Clojure on
CLR. :)
- David
On Aug 13, 3:36 pm, Seth wrote:
> Sorry all -- I think my original message went slightly awry. The
> announcement was a shock and quickly followed by waves of grumbling
> from devs I follow on Twitter. While
We have a ten-week program for experienced developers moving to
the .NET platform. Our recommended text is Troelson's "Pro C# 2010
and the .NET 4 Platform, Fifth Edition".
http://www.apress.com/book/view/1430225491
All 1752 pages of it.
It has a lot of things you won't need for understanding
eferences to my VS project, and compile,
> > much like I do with NetBeans and the JVM clojure.
>
> > I have to admit that I haven't tried ClojureCLR since right around the
> > 1.1 release, so I don't remember the details of the problems that I
> > encountered. I am in
I can move creating a binary distribution to the to top of the list.
I could use some guidance from the interested on what would serve the
purpose on this and other things mentioned here.
on the distribution: Do you want just a zip of of DLLs? An
installer? Do you want installation to the GAC?
> Yes, it's easy to imagine a world where people who want efficient code
> have to jump through hoops to get it. OTOH, you can just say (num some-
> expr) to force it to be boxed, if you want assurance of an Object
> initializer. Which will be the more common need?
>
>From the wiki page "Enhanced
o compile
> without issue.
>
> I still have the several second delay, and from what little I kind
> find around I suppose that is typical. Is that correct? Is there any
> way to bring that down?
>
> Thank you,
> Joerthan
>
> On Apr 23, 9:45 pm, dmiller wrote:
>
&
I haven't compiled under a release in a while. Recent changes to the
build system may have messed it up. I'll check it out.
David
On Apr 23, 2:11 am, Joerthan Panest wrote:
> Hello,
>
> I am considering ClojureCLR for embedding in an application, but it appears
> as though it takes ~4secs to
Two factors:
(1) I'm working on deftype/protocols/reify and related things. This
requires some non-trivial re-engineering of the compiler (based on non-
trivial reverse-engineering of all the changes made to Clojure JVM).
(2) I'm up to my nostrils on a little pro bono web site development I
fooli
Parallel to proxy, clojure-clr adds a gen-delegate. Example code is
in
http://github.com/richhickey/clojure-clr/blob/master/Clojure/Clojure.Source/clojure/samples/celsius.clj
Specifically, for adding an EventHandler:
(.add_Click button
(gen-delegate EventHandler [sender args]
(let [c (Dou
There is no other place.
On Feb 23, 1:16 am, adam11235 wrote:
> Hi,
>
> Is this group an appropriate place to post clojure-clr questions?
>
> Is there a more relevant place to ask clojure-clr questions?
>
> Thanks, Adam
--
You received this message because you are subscribed to the Google
Group
if
> it had ToolsVersion="3.5"'.. I don't know if it has anything to do
> with it.
>
> There are also some 'reference component not found' warnings in the
> DLR project. Would that be a problem ?
>
> thanks,
> sriram.
>
> On Fri, Dec 25, 200
Wow, Google only gets nine hits on MSB3075. One, possibly relevant,
solved by moving to admin privilege. One, yours. Others, not
relevant. Thus ends my error-resolution attempt!
>From the message, I'm assuming .net 3.5. What flavor of VS?
-David
On Dec 23, 9:21 pm, sriram p c wrote:
> I wa
1 - 100 of 121 matches
Mail list logo
