Hi all,
I just published the second part of the tutorial - learn by contributing.
https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-21.md
Here I started from where I leaft the previous tutorial-20 by revisiting again
the Enfocus directories layout and its project.clj to make it
Hi all,
I just published the 20th Tutorial - Learn by Contrbuting - of the modern-cljs
series.
https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-20.md
In this tutorial, while studying the very interesting and promising Enfocus
lib, I'll started collaborating with Creighton Kirk
o know in detail *why* it saves him
> time, I don't have an answer for that question.
The page above was renamed to be shorter. The new link is
http://dev.clojure.org/display/design/Contributing+FAQ
Andy
--
--
You received this message because you are subscribed to the Google
Groups &
Michael, I would also love it if bugs got fixed in master more quickly. I've
done some things to try to make that happen, but for all I know I've only
exacerbated the issue. I'm still searching for ways to improve that.
One thing I know at the base of all such suggestions is: I am not going to
Clojure implementations evolve, fewer and fewer people will
> discover issues large enough to justify diving into the code base to fix
> them. Most people just work around the issues. If somebody takes the
> initiative to properly fix an issue, we shouldn't add yet another hurdl
On Jan 20, 2013, at 7:49 AM, Anthony Grimes wrote:
>
>
> In closing, I propose the following. If we're going to continuously deny
> people things they are accustomed to, instead of treating them like angry
> children having tantrums, why don't we get a response from clojure/core and
> have it
On Sunday, 2013-01-20 at 14:27 , Michał Marczyk wrote:
> On a separate note, if there are indeed "tons of bugs when it comes to
> cross-browser compatibility" in ClojureScript, pointing (as many as
> possible of) them out would be extremely helpful, indeed more than
> submitting the actual patch
On a separate note, if there are indeed "tons of bugs when it comes to
cross-browser compatibility" in ClojureScript, pointing (as many as
possible of) them out would be extremely helpful, indeed more than
submitting the actual patches. That would also not require going
through the patch submission
Clojure and contrib have long had extremely thorough CI in place,
including matrix testing with multiple JVM implementations:
http://build.clojure.org/
Cheers,
M.
On 20 January 2013 22:04, Brandon Bloom wrote:
> I think the inflammatory thread subject didn't help...
>
> Java and cross-browser
I think the inflammatory thread subject didn't help...
Java and cross-browser CI both sound great. I don't know if Clojure/core
already has CI or what, but maybe you should take these ideas over to
another thread? Possibly on the Dev mailing list. Because of the
intentionally slow pace of Cloju
I just wanted to mention that pull request was one of the several notes I've
made, but looks like it's being irritating enough people that it completely
took over this thread. The problem itself is not a JIRA or that sending patches
is too hard (even though I think it's too much incidental compl
On Sunday, January 20, 2013 11:33:56 AM UTC-6, Fogus wrote:
>
>
>
>> To make matters worse, Clojure/core consistently avoids discussing these
>> issues in public
>>
>
> I would guess because their position hasn't changed since the last time.
> This is only speculation. A page like what Anth
> I'm sorry but given Clojure/core's track record of *actions* (or lack of
> them, rather) this
> sounds a bit offensive to people who are not Clojure/core members, Clojure
> committers or "screeners".
>
Adding source annotations to a Github project's source base and starting an
IRC channel have n
On Sunday, January 20, 2013 10:22:04 AM UTC-6, Fogus wrote:
>
>> Please don't ask people to not rehash this discussion. Don't tell them
>> that it is a 'weak reason' for not contributing and 'not worth fighting
>> over'.
>>
>
>
2013/1/20 Michael Fogus
> We're all friends here. Everyone wants to help. There are ways to
> help that do not involve endless mailing list threads and personal
> distaste of process.
>
Michael,
I'm sorry but given Clojure/core's track record of *actions* (or lack of
them, rather) this
sounds
>
>
> Please don't ask people to not rehash this discussion. Don't tell them
> that it is a 'weak reason' for not contributing and 'not worth fighting
> over'.
>
Well, that's only my opinion. I happen to think it's not worth fighting
o
It makes more sense to compare language projects. I note that ClojureScript
does about as well as Scala in this comparison and much better than
CoffeeScript. Scala and CoffeeScript use pull requests.
I also do not like JIRA. But I think the happiness of contributing to
ClojureScript far outweighs
On Sunday, January 20, 2013 9:16:35 AM UTC-6, Fogus wrote:
> I'll just add a few points:
>
> Pull requests are not likely to happen. It's not worth fighting over.
> However, I think that is a weak excuse for not contributing. If you
> want to contribute a comple
Well said, Fogus, well said.
On Sunday, January 20, 2013 9:16:35 PM UTC+6, Fogus wrote:
>
> I'll just add a few points:
>
> Pull requests are not likely to happen. It's not worth fighting over.
> However, I think that is a weak excuse for not contributing. If yo
I'll just add a few points:
Pull requests are not likely to happen. It's not worth fighting over.
However, I think that is a weak excuse for not contributing. If you
want to contribute a complex bug fix, then the patch process is
trivial by comparison. If you want to contribute doc
definitely less easy to make than to
> projects that willy-nilly accept any pull request.
>
Who says any pull request should be accepted? It is pretty widely accepted
that contributing to Clojure and anything Clojure/core
touches is needlessly hard. That's what this thread is about, n
is created,
create also the JIRA issue with the patch added, then add a github comment
pointing to the JIRA issue and close the pull request. This is not perfect,
but IMO better than the current state...
Another, even easier would be just to autopost a github comment, stating
that pull reques
There are 176 forks on GitHub. Even assuming that all 51 contributors have
a public fork (most probably do), that's 125 potential contributors
unaccounted for. Only 29% of those forks account for an accepted
contribution. What portion of the remainder might have been contributors?
I was curious
It is great that questions are being asked about how things do, might or
should work - but tone of the original question and the ensuing discussion,
in my view, unfortunate.
On Sunday, 20 January 2013 17:36:11 UTC+11, Irakli Gozalishvili wrote:
>
> Anyway it's seems to me that message in this t
Anyway it's seems to me that message in this thread is pretty clear:
"We're just doing fine without people like you"
It's a shame, but whatever I'll just shut up and let you guys roll as you
pleased
Regards
--
Irakli Gozalishvili
Web: http://www.jeditoolkit.com/
On Saturday, 2013-01-19 at 22:
I would be curious to also see number of lost contributors.
Regards
--
Irakli Gozalishvili
Web: http://www.jeditoolkit.com/
On Saturday, 2013-01-19 at 22:00 , David Nolen wrote:
> I have nothing to add to this thread beyond pointing out that ClojureScript
> has had _51_ contributors in the sho
I have nothing to add to this thread beyond pointing out that ClojureScript
has had _51_ contributors in the short year and a half of its existence:
http://github.com/clojure/clojurescript/graphs/contributors.
Via JIRA.
David
--
You received this message because you are subscribed to the Google
Than Sean for pointing to that thread that's helpful although that got me
wondering if Rich is only one
doing the reviews ? If that's not the case maybe there at least on maintainer
that is willing to bridge the
gap here ?
I really hope someone will step up to bridge the gap, maybe setup a fork
On Saturday, 2013-01-19 at 11:56 , Andy Fingerhut wrote:
> Irakli:
>
> I am curious about the possibility of auto-creating patches from git pull
> requests, in case that would bridge the divide between people that would
> prefer submitting pull requests, and Clojure screeners that would prefer
As of comments related to projects that also make contributions hard that's
their choice, and I really hope clojure community will do better than that. I
also know that sometimes rewriting patch is a lot less work than making
someones contribution acceptable, my day job involves all of that, but
fix an issue, we shouldn't add yet another hurdle discouraging them
> from contributing.
>
> --
> 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
>
Yep, tools to maintain tickets suck, Jira, Mantis,...
However, having Clojure code in production 24/7 and ClojureScript code
reaching production status in a month or so, I feel reassured that a
maintenance process
is in place and that patch screening is tight.
We have enough doing the same thin
Aaron, please forgive my failure at formalities: Allow me to add that I
agree with the rest of your post.
The Linux kernel and Guava guys are absolutely right about patches
defaulting to the rejected state. I'm a big believer in the "minus 100
points" philosophy.
It's just that I just really h
properly fix an issue, we shouldn't add yet another hurdle discouraging
them from contributing.
--
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 me
Also, another blog post dealing with the open source code contribution
issue: http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/
On Sat, Jan 19, 2013 at 5:38 PM, Aaron Cohen wrote:
> Being the maintainer of an open source problem is a hard task.
>
> Contributing to a proje
Being the maintainer of an open source problem is a hard task.
Contributing to a project is not a process that begins and ends with code
submissions. In fact, it's often more work for a maintainer to accept a
patch or pull request than it is for him or her to write the equivalent
code hi
+1
On Saturday, January 19, 2013 11:47:56 PM UTC+4, Andy Fingerhut wrote:
>
>
> On Jan 18, 2013, at 3:52 PM, Sean Corfield wrote:
>
> > On Fri, Jan 18, 2013 at 1:33 PM, Andy Fingerhut
> > > wrote:
> >> The issue that Clojure, its contrib libraries, and ClojureScript do not
> accept github pull
Irakli Gozalishvili:
>
> If these things are intentionally made hard to stop new people with more
> clojurescipt interests then please
> make it more clear, cause otherwise it just a motivation killer.
>
>
Irakli,
Over the years, many people have tried raising the question of
Irakli:
I am curious about the possibility of auto-creating patches from git pull
requests, in case that would bridge the divide between people that would prefer
submitting pull requests, and Clojure screeners that would prefer evaluating
patches and JIRA tickets.
Causing a new git pull reques
On Jan 18, 2013, at 3:52 PM, Sean Corfield wrote:
> On Fri, Jan 18, 2013 at 1:33 PM, Andy Fingerhut
> wrote:
>> The issue that Clojure, its contrib libraries, and ClojureScript do not
>> accept github pull requests has been brought up several times before on this
>> email list in the past. Fe
BTW also as hugo pointed out with http://www.clahub.com/ one could just reject
pull requests if any of the commit included
is from author who have not signed CLA yet. So looks like CLA problem can be
also easily solved.
Regards
--
Irakli Gozalishvili
Web: http://www.jeditoolkit.com/
On Frida
cited and I'm trying to get
involved
again. Luckily he's being awesome to work with & has no problems accepting pull
requests. But if the process of contributing
is more work than I can keep up with I'll have to turn away again :(
I also don't quite see the point of b
On Friday, 2013-01-18 at 18:03 , Sean Corfield wrote:
> Because by submitting a JIRA patch explicitly, you are taking the
> legal responsibility for the contents of the patch as being a change
> that you are authorized to submit under the CA...
>
You can in fact do similar with
For what it's worth, I've submitted 20+ patches to ClojureScript and one or
two to Clojure proper. I still find the process to be extremely unpleasant.
I consistently avoid interacting with JIRA until the last possible minute:
That software is actively user-hostile. Without naming names, I've sp
Because by submitting a JIRA patch explicitly, you are taking the
legal responsibility for the contents of the patch as being a change
that you are authorized to submit under the CA...
I'm not sure that you can even attach a patch to a Clojure ticket in
JIRA without being given permission to modif
One could also copy attach patch with lines that belong to someone else. How is
that different ?
Pull requests are just a tool for working with patches nothing else
Regards
--
Irakli Gozalishvili
Web: http://www.jeditoolkit.com/
On Friday, 2013-01-18 at 16:18 , Sean Corfield wrote:
> That wil
At mozilla we also require signing CA but do accept pull requests and there are
whole team of legal people that
makes sure things like that don't raise any legal concerns. After all it's just
.patch to the pull request url gives you
an actual change patch so if reviewing patches is desired it's e
That will depend on whether it traces the origin of each line in the
patch - just relying on the pull request originator is not sufficient
(unfortunately).
On Fri, Jan 18, 2013 at 4:11 PM, Hugo Duncan wrote:
> Sean Corfield writes:
>
>> My understanding is that with pull requests it becomes much
Sean Corfield writes:
> My understanding is that with pull requests it becomes much harder to
> provide accountability for Intellectual Property which is a legal
> concern, and that's why we have a Contributor's Agreement.
I wonder if the availability of http://www.clahub.com/ changes anything.
On Fri, Jan 18, 2013 at 1:33 PM, Andy Fingerhut
wrote:
> The issue that Clojure, its contrib libraries, and ClojureScript do not
> accept github pull requests has been brought up several times before on this
> email list in the past. Feel free to search the Google group for terms like
> "pull
One process that could be made a little easier is the contribution of code
documentation and suggested improvements of doc-strings.
New or improved doc-strings do not change any functionality, impact any tests,
require peer review…
If we could simply suggest new doc-strings for example in the J
The issue that Clojure, its contrib libraries, and ClojureScript do not accept
github pull requests has been brought up several times before on this email
list in the past. Feel free to search the Google group for terms like "pull
request". Short answer: Rich Hickey prefers a workflow of evalu
I'm not sure I've ever sent an email where the entire content should
be "+1", but this is the one where it felt most compelling.
Please split the list.
Sent from my iPhone
On Jan 18, 2013, at 4:25 PM, Phil Hagelberg wrote:
>
> Irakli Gozalishvili writes:
>
>> - I do understand that most of the
Irakli Gozalishvili writes:
> - I do understand that most of the clojurescript audience is probably
> also interested in clojure, but please don't enforce that. Have a
> separate mailing list so that people interested in clojurescript and
> not clojure could follow relevant discussions without ma
I have being trying to engage community and to contribute to clojurescript for
a while already,
but so far it's being mostly frustrating and difficult. I hope to start
discussion here and maybe
get some constructive outcome.
## Rationale
I'm primarily interested in clojurescript and not at al
Thanks, If I'd read that page carefully & done a search in JIRA I
would've seen that CLJS-24 already addresses this. Doh!
On Sep 1, 4:26 pm, Luc Prefontaine
wrote:
> Look at this:
>
> http://clojure.org/contributing
>
> Luc P.
>
> On Thu, 1 Sep 2011 04:53:20
Look at this:
http://clojure.org/contributing
Luc P.
On Thu, 1 Sep 2011 04:53:20 -0700 (PDT)
Ralph Moritz wrote:
> Hi Clojurians!
>
> I created my first JIRA issue today (CLJ-834), but I didn't assign it
> to anyone, because I didn't know who to assign it to! Also, I
Hi Clojurians!
I created my first JIRA issue today (CLJ-834), but I didn't assign it
to anyone, because I didn't know who to assign it to! Also, I'm not
sure what the procedure is for submitting code - do you generally post
to this group & JIRA or just create an issue? Any guidelines would be
welc
Hi,
Am 21.12.2010 um 22:00 schrieb Laurent PETIT:
> Now yes, and no, no more chances :-(
Seems the link is fixed? http://oss.oracle.com/oca-faq.pdf
Sincerely
Meikel
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email
39 pm, Mike Meyer wrote:
> The link to the SCA FAQ on the page at clojure.org/contributing now
> returns a document not found page. Given that the Clojure CA is based
> on the Sun Contributor Agreement and what Oracle has since done with
> NotQuiteSoOpenSolaris, this would seem to be an i
2010/12/21 Ken Wesson
> On Tue, Dec 21, 2010 at 3:43 PM, Laurent PETIT
> wrote:
> > Indeed, this has been a problem for me too. I also tried to get it via
> the
> > backdoors, e.g. via the Open JDK, Netbeans, etc., websites, but they did
> > respect the "DRY" principle correctly, and all I found
On Tue, Dec 21, 2010 at 3:43 PM, Laurent PETIT wrote:
> Indeed, this has been a problem for me too. I also tried to get it via the
> backdoors, e.g. via the Open JDK, Netbeans, etc., websites, but they did
> respect the "DRY" principle correctly, and all I found was just links to the
> missing pag
o the SCA FAQ on the page at clojure.org/contributing now
> returns a document not found page. Given that the Clojure CA is based
> on the Sun Contributor Agreement and what Oracle has since done with
> NotQuiteSoOpenSolaris, this would seem to be an important document to
> have avai
The link to the SCA FAQ on the page at clojure.org/contributing now
returns a document not found page. Given that the Clojure CA is based
on the Sun Contributor Agreement and what Oracle has since done with
NotQuiteSoOpenSolaris, this would seem to be an important document to
have available
On 11 February 2010 00:44, Sean Devlin wrote:
> Take a look here:
>
> http://clojure.org/contributing
Um... I strongly suspect that this may be a supremely silly question,
but I can't seem to figure out what's supposed to go in some of the
fields.
Does one specify "Cloju
Hi,
On Feb 11, 12:57 am, Wardrop wrote:
> As part of my second question, could someone take a look at the code
> I've posted and tell me if it's a good implementation and follows
> clojure idioms and standards.
I haven't checked the algorithm itself, but just some random notes
after skimming th
>
> Cheers
>
> On Feb 11, 9:44 am, Sean Devlin wrote:
>> Take a look here:
>>
>> http://clojure.org/contributing
>>
>> On Feb 10, 6:38 pm, Wardrop wrote:
>>
>> > I've written a function which I think would be a good inclusion into
>>
standards, like what to call function arguments (e.g. idx for indexes
and coll for collections to name the more obvious ones).
Cheers
On Feb 11, 9:44 am, Sean Devlin wrote:
> Take a look here:
>
> http://clojure.org/contributing
>
> On Feb 10, 6:38 pm, Wardrop wrote:
>
> &g
Take a look here:
http://clojure.org/contributing
On Feb 10, 6:38 pm, Wardrop wrote:
> I've written a function which I think would be a good inclusion into
> the Clojure.Contrib library. I have two questions though, the first is
> how? How do I go about adding a single function
http://clojure.org/contributing
seq-utils was recently renamed:
http://groups.google.com/group/clojure-dev/browse_thread/thread/49068754a8c2efb9#
On Wed, Feb 10, 2010 at 3:38 PM, Wardrop wrote:
> I've written a function which I think would be a good inclusion into
> the Clojure.Cont
I've written a function which I think would be a good inclusion into
the Clojure.Contrib library. I have two questions though, the first is
how? How do I go about adding a single function to an existing
namespace; in this case, seq-utils, and what are the pre-requisites?
My second question is, wha
CA = Contributor Agreement.
See http://clojure.org/contributing
Github help is fairly extensive: http://github.com/guides/home
On Jun 11, 8:28 pm, mmwaikar wrote:
> What is CA? I've never used GitHub too so any help is greatly
> appreciated.
>
> On Jun 11, 3:24 pm, Da
What is CA? I've never used GitHub too so any help is greatly
appreciated.
On Jun 11, 3:24 pm, David Miller wrote:
> Yes to all of the above.
>
> Github will always be the most current version. I'm rolling changes
> out to contrib on a less frequent basis.
>
> for, improve, post a pull on gith
Yes to all of the above.
Github will always be the most current version. I'm rolling changes
out to contrib on a less frequent basis.
for, improve, post a pull on github is way to go.
And CA definitely required.
On Jun 11, 10:14 am, Rich Hickey wrote:
> On Jun 11, 9:57 am, Paul Stadig wro
On Jun 11, 9:57 am, Paul Stadig wrote:
> I believe David Miller is the one who wrote the CLR code, and he is still
> hacking on it when he has time.
>
> In addition to what is checked into contrib there is also this:
>
> http://github.com/dmiller/ClojureCLR/tree/master
>
> I'm not sure if they
I believe David Miller is the one who wrote the CLR code, and he is still
hacking on it when he has time.
In addition to what is checked into contrib there is also this:
http://github.com/dmiller/ClojureCLR/tree/master
I'm not sure if they are in sync or which is the most current (github may be
Hi,
How can one contribute to the development of Clojure on CLR?
I was trying the following - (.ToString DateTime/Now) and was getting
- "System.Exception: Unable to find static field: Now in
System.DateTime".
I added some code in Reflector.cs, Compiler.cs and StaticFieldExpr.cs
and got it work
l rule to contribute, you need to fill-in and mail the CA:
> >http://clojure.org/contributing
>
> > When Rich receives your CA and updates the clojure.org website, you
> > can start creating issues in clojure-contrib and attaching patches to
> > it. Example:
> >http:
> As a general rule to contribute, you need to fill-in and mail the CA:
> http://clojure.org/contributing
It's in the mail today.
> Files in test_clojure represent different areas - feel free to take
> your pick and do whatever you like :-)
Great! Looking forward t
Frantisek Sodomka writes:
> As a general rule to contribute, you need to fill-in and mail the CA:
> http://clojure.org/contributing
>
> When Rich receives your CA and updates the clojure.org website, you
> can start creating issues in clojure-contrib and attaching patches t
Hello Richard,
any contributions to test_clojure are very welcome!
As a general rule to contribute, you need to fill-in and mail the CA:
http://clojure.org/contributing
When Rich receives your CA and updates the clojure.org website, you
can start creating issues in clojure-contrib and attaching
is that
> there seems to be a sizable group of people who are keen on
> contributing to Clojure, including basic "drudge" work. It also seems
> apparent that having a decent test suite is valuable (if only for the
> sake of appearances and adoption), though I tend to agree tha
One of the things that occurred to me at last night's Meetup is that
there seems to be a sizable group of people who are keen on
contributing to Clojure, including basic "drudge" work. It also seems
apparent that having a decent test suite is valuable (if only for the
sake of
Thanks.
Joshua
On Feb 28, 2009, at 8:16 AM, Rich Hickey wrote:
>
> On Feb 27, 2009, at 10:59 PM, Joshua wrote:
>
>>
>> I have started looking into Issue 34 and I have some questions.
>>
>> Link:
>> http://code.google.com/p/clojure/issues/detail?id=34&colspec=ID%20Type%20Status%20Priority%20Repo
On Feb 27, 2009, at 10:59 PM, Joshua wrote:
>
> I have started looking into Issue 34 and I have some questions.
>
> Link:
> http://code.google.com/p/clojure/issues/detail?id=34&colspec=ID%20Type%20Status%20Priority%20Reporter%20Owner%20Summary
>
> Is the desired syntax to match the CL version?
>
On Sat, Feb 28, 2009 at 6:13 AM, Stephen C. Gilardi wrote:
>
> On Feb 27, 2009, at 10:59 PM, Joshua wrote:
>
>> Is the desired syntax to match the CL version?
>
> Following CL's lead by implementing a *read-eval* var as Stuart suggested
> looks like a good way to do this to me.
So, I suppose the
On Feb 27, 2009, at 10:59 PM, Joshua wrote:
Is the desired syntax to match the CL version?
Following CL's lead by implementing a *read-eval* var as Stuart
suggested looks like a good way to do this to me.
Should I create a separate reader for the read-only version or just
use an if state
I have started looking into Issue 34 and I have some questions.
Link:
http://code.google.com/p/clojure/issues/detail?id=34&colspec=ID%20Type%20Status%20Priority%20Reporter%20Owner%20Summary
Is the desired syntax to match the CL version?
Should I create a separate reader for the read-only version
I haven't read _The Reasoned Schemer_, but I have read the logic programming
sections of SICP and Norvig .. as well as some non-lispy texts. I *suspect*
TRS's material is at a similar weight. What I'm trying to do now goes quite
a bit beyond those implementations. Plus, they are all use a top-do
There's a logic programming module in the files section. It
implements the system found in "The Reasoned Schemer".
On Feb 18, 2:59 pm, Jeffrey Straszheim
wrote:
> Did you cover logic programming? Any bottom up logic query techniques?
> (My motives are probably transparent.)
>
> On Wed, Feb 18,
ua
>
> > On Feb 19, 9:47 am, Shawn Hoover wrote:
>
> > > On Thu, Feb 19, 2009 at 9:44 AM, Joshua wrote:
>
> > > > Thanks, Ill see what I can do.
>
> > > > Joshua
>
> > > If you decide to pitch in, be sure to readhttp://clojure.org/c
ll send in my CA.
>
> Joshua
>
> On Feb 19, 9:47 am, Shawn Hoover wrote:
>
> > On Thu, Feb 19, 2009 at 9:44 AM, Joshua wrote:
>
> > > Thanks, Ill see what I can do.
>
> > > Joshua
>
> > If you decide to pitch in, be sure to readhttp://clojure.
to pitch in, be sure to readhttp://clojure.org/contributing.
> Discuss on this list before getting too far into something, to make sure the
> direction is acceptable and that there's no duplicate effort.
--~--~-~--~~~---~--~~
You received this message beca
On Thu, Feb 19, 2009 at 9:44 AM, Joshua wrote:
>
> Thanks, Ill see what I can do.
>
> Joshua
>
If you decide to pitch in, be sure to read http://clojure.org/contributing.
Discuss on this list before getting too far into something, to make sure the
direction is acceptable and
No, we have not covered logic programming yet.
Joshua
Jeffrey Straszheim wrote:
> Did you cover logic programming? Any bottom up logic query techniques?
> (My motives are probably transparent.)
>
> On Wed, Feb 18, 2009 at 2:34 PM, Joshua wrote:
>
> >
> > I am currently in a masters level Compi
Thanks, Ill see what I can do.
Joshua
On Feb 18, 4:02 pm, Chouser wrote:
> On Wed, Feb 18, 2009 at 2:34 PM, Joshua wrote:
>
> > I am currently in a masters level Compiler class. We have a final
> > project for the class and I was wondering if there would be any
> > defects/enhancements that I
On Wed, Feb 18, 2009 at 2:34 PM, Joshua wrote:
>
> I am currently in a masters level Compiler class. We have a final
> project for the class and I was wondering if there would be any
> defects/enhancements that I could do in Clojure. I have about 5 years
> of professional Java experience with dab
Did you cover logic programming? Any bottom up logic query techniques?
(My motives are probably transparent.)
On Wed, Feb 18, 2009 at 2:34 PM, Joshua wrote:
>
> I am currently in a masters level Compiler class. We have a final
> project for the class and I was wondering if there would be any
>
I am currently in a masters level Compiler class. We have a final
project for the class and I was wondering if there would be any
defects/enhancements that I could do in Clojure. I have about 5 years
of professional Java experience with dabbling with some other
languages. (not an expert, but prett
99 matches
Mail list logo
