On 21.04.2009, at 00:26, Mark Volkmann wrote:
> Is it correct to say that macros are expanded at read-time?
No. Only reader macros are expanded at read time, standard macros are
expanded at compile time.
A more subtle point concerns the distinction between compile time and
run time, because
I suppose you could always just use plain old java threads and avoid
the thread-pool, or futures which have the advantage of being cancel-
able?
On Apr 21, 11:57 am, billh04 wrote:
> In my application, I can open several windows. Each window is an
> independent unit and will send-off three agen
On 21.04.2009, at 00:19, Michael Hunger wrote:
>
> Is it possible to use :while to shortcut a for macro when a certain
> number of yiels have happened?
>
> e.g. (for [x (range 1000) :when (= (rem x) 1) :while (number of
> yields <= 10)]
>
> so i want only the first 10 results.
you could:
(d
I've done a little comparing to sorted-set as recommended. The following
test (in case there is anything bogus about it) is checked in with the java
project:
http://code.google.com/p/jc-pheap/source/browse/trunk/jc-pheap/src/persistent_heap/testing/test.clj?spec=svn8&r=8
deduping 2,000,000 nums
s
I blindly tried printing out stuff from matrixMultiply, and found out
that if I print matrixA and matrixB it doesn't run out of stack, so I
guess I was "forcing" them to "work", here is a version with (dorun)
that has the same side effect, without printing:
(defn matrixMultiply [matrixA matrixB]
There are some precedents - the acquisition of SleepyCat (berkeley db,
et al) - still readily available under GPL compatible licenses.
On Tue, Apr 21, 2009 at 7:47 AM, AlamedaMike wrote:
>
>>> I can see a lot of technologies that drive the open source world, and this
>>> group, being compromise
>> I can see a lot of technologies that drive the open source world, and this
>> group, being compromised
Nothing's going to happen, for the simple reason that the cost to
Oracle's reputation would far outweigh anything they might gain from
charging for open-source products. The ultimate effect
Daniel,
I have not followed maven2 concerning this "qualifier" thing.
Would it be corrrect to say that, to further extend you examples, one
the qualifiers could be "slim", since clojure ant already has such a
target.
Or would a "slim" jar of clojure have to had another artifactId ? (I
don't thi
I posted this a couple of weeks ago and haven't seen it updated on the
clojure
website. Maybe it got lost in the shuffle.
Name: clj-web-crawler
URL: http://github.com/heyZeus/clj-web-crawler/tree/master
Author: Brian Doyle
Categories: Web, Automation
License: MIT
Dependencies: clojure, clojure-c
Hi David,
Those two are not recursive, but they call into other functions that
are. Do I need to make sure that all recursive functions use the loop/
recur pattern? Or should I not nest recursive calls like this?
Here is the whole source:
;; Neuron Activation Functions
;threshold
(defn thresho
Hi David,
Those two are not recursive, but they call into other recursive
functions. Do I need to make sure all recursive functions use the loop/
recur pattern? Or maybe not nest recursive calls like this?
Here is the whole source:
;threshold
(defn threshold [x] (if (>= x 0) 1 0))
;signum (thr
It would be fun to have a team of clojure programmers work on the ICFP '09
contest. Has this been done previously? Anybody interested? I'm new to
clojure and to lisps in general, but have a pretty good grasp of functional
programming (mostly from haskell). It would be great fun to work with some
mo
On Apr 20, 2:17 pm, Mark Engelberg wrote:
> On Mon, Apr 20, 2009 at 1:27 PM, Bradbev wrote:
> > If you promise that
> > functions will accept and return maps with certain keys, then you must
> > keep that promise moving forward.
>
> I think you're missing part of the point of the original post.
In my application, I can open several windows. Each window is an
independent unit and will send-off three agents to do background work.
When I close a window, I stop the three threads from running, but the
thread count never goes down when I display it by (println "Thread
count is" (Thread/activeC
For a 1.0 release I'd love to see some support for JDK annotations
somehow, at both the gen-class and method level at least.
Mark
On Fri, Apr 17, 2009 at 4:53 AM, Rich Hickey wrote:
> This is mostly about - does it work? Is it relatively free of bugs? Is
> it free of gaping holes in core funct
Rich Hickey wrote:
> I'm unfamiliar with the POM version coordinate system - any hints?
Maven takes the version as whatever-formatted string, but recognizes a
conventional (.endsWith "1.0.0-SNAPSHOT" "-SNAPSHOT"), like described
by Laurent PETIT. So "whatever-SNAPSHOT" means we're going someday t
On 21/04/2009, at 10:51 AM, Antony Blakey wrote:
> On 21/04/2009, at 10:22 AM, Rich Hickey wrote:
>
>> I'm unfamiliar with the POM version coordinate system - any hints?
>
> My comment was in support of Laurent's proposal. I'm a relative
> maven newb, but this is my take:
>
> POMs use the conc
On 21/04/2009, at 10:22 AM, Rich Hickey wrote:
> I'm unfamiliar with the POM version coordinate system - any hints?
My comment was in support of Laurent's proposal. I'm a relative maven
newb, but this is my take:
POMs use the concept of a coordinate, which is
::: to identify a particular
On Apr 20, 2009, at 7:02 PM, Antony Blakey wrote:
>
>
> On 21/04/2009, at 5:12 AM, Laurent PETIT wrote:
>
>> To give you more ideas, there is a convention in tools like maven/ivy
>> that when you're starting the hack on a branch targeting some version
>> M.m.r , you immediately rename the place
On Mon, Apr 20, 2009 at 6:12 PM, Greg Harman wrote:
>
> > Has anyone here been able to install Clojure on IcedTea?
>
> For what it's worth, I run Clojure on SoyLatte and have never had a
> problem.
I never had any problem on IcedTea.
--~--~-~--~~~---~--~~
You re
As far as I know the number of yields is not available for testing, so
you have to use take
user=> (take 10 (for [x (range 1000) :when (= (rem x 2) 1)] x))
(1 3 5 7 9 11 13 15 17 19)
On Apr 21, 8:19 am, Michael Hunger wrote:
> Is it possible to use :while to shortcut a for macro when a certain n
Laurent PETIT wrote:
> > I'd suggest calling :release something else, like :revision
> > or :patch.
> I like the term "service" used in Eclipse terminology:
> "the service segment indicates bug fixes"
>
> (The numbering scheme for Eclipse uses major, minor, service and
> qualifier : "the qualifier
On Apr 20, 4:17 pm, Mark Engelberg wrote:
> On Mon, Apr 20, 2009 at 1:27 PM, Bradbev wrote:
> > If you promise that
> > functions will accept and return maps with certain keys, then you must
> > keep that promise moving forward.
>
> I think you're missing part of the point of the original post
On 21/04/2009, at 5:12 AM, Laurent PETIT wrote:
> To give you more ideas, there is a convention in tools like maven/ivy
> that when you're starting the hack on a branch targeting some version
> M.m.r , you immediately rename the place in code where you maintain
> the version number by appending
But "reader macros" *are* expanded at read-time (as their name
indicates, BTW) :
1:91 user=> (read-string "'quoted-symbol")
(quote quoted-symbol)
1:92 user=>
HTH,
--
Laurent
2009/4/21 Laurent PETIT :
> 2009/4/21 Mark Volkmann :
>>
>> I didn't explain my question well enough. Suppose I define
2009/4/21 Mark Volkmann :
>
> I didn't explain my question well enough. Suppose I define a macro
> with defmacro and have several calls to it in my code. When are those
> calls expanded to the code inside the macro? Is that at read-time?
Maybe the example I gave (by using the macro 'defn) was not
Hi Mark,
Am 21.04.2009 um 00:40 schrieb Mark Volkmann:
I didn't explain my question well enough. Suppose I define a macro
with defmacro and have several calls to it in my code. When are those
calls expanded to the code inside the macro? Is that at read-time?
As Laurent said: No. Macro expansi
I didn't explain my question well enough. Suppose I define a macro
with defmacro and have several calls to it in my code. When are those
calls expanded to the code inside the macro? Is that at read-time?
On Mon, Apr 20, 2009 at 5:34 PM, Laurent PETIT wrote:
>
> Hello,
>
> Apparently, no:
>
> 1:8
Hello,
Apparently, no:
1:85 user=> (macroexpand-1 '(defn hello [] "world"))
(def hello (clojure.core/fn ([] "world")))
1:86 user=> (read-string "(defn hello [] \"world\")")
(defn hello [] "world")
1:87 user=>
read-string did not expand defn.
I think it's 'eval that expands macros and compiles
In my Clojure article at http://ociweb.com/mark/clojure/article.html I say:
"Clojure code is processed in three phases: read-time, compile-time
and run-time. At read-time the Reader reads source code and converts
it to a data structure, mostly a list of lists of lists At
compile-time this da
Is it possible to use :while to shortcut a for macro when a certain number of
yiels have happened?
e.g. (for [x (range 1000) :when (= (rem x) 1) :while (number of yields <= 10)]
so i want only the first 10 results.
Or should I just use (take 10 ) on the for ?
Michael
--~--~-~--~~
> Has anyone here been able to install Clojure on IcedTea?
For what it's worth, I run Clojure on SoyLatte and have never had a
problem.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this
On Apr 5, 1:32 pm, dlb wrote:
> I have the same problem on my Mac as well, i.e. if clojure.jar is
> loaded from ~/Library/Java/Extensions rather than from the classpath,
> then clojure does not find files on the classpath. I did some poking
> around and on my Mac OS X 10.5.6 with Java 6.
> ...
On Mon, Apr 20, 2009 at 1:59 PM, David Nolen wrote:
> Maps aren't ordered so this isn't a good idea anyway.
It's a good idea if you have a sorted map. My example should have used
sorted-map.
> The reason first/second work is because they call seq on the collection.
> (key (nth (seq {:a 1 :b 2 :
On Mon, Apr 20, 2009 at 1:27 PM, Bradbev wrote:
> If you promise that
> functions will accept and return maps with certain keys, then you must
> keep that promise moving forward.
I think you're missing part of the point of the original post. You
don't really want to promise that your functions
I read the rest of this thread, and thought I'd throw in my two cents.
It seems to me that you are mostly concerned with being able to
provide a stable external API to clients while allowing the internal
data structures to change. As a library designer you need to choose
which parts of your API a
Using something like this run-slime wrapper to start slime may be
useful to others. It helps me avoid some issues when moving from
project to project without restarting emacs. Assuming jar files reside
in each separate project's own "lib" directory, Clojure source in its
"src" directory, and compi
Hi David,
2009/4/20 David Nolen :
> A couple of things. In your initial example, you conflated some things. One
> issue is simply a matter of convenience- defining a getter so that you can
> use Python object property access (via the dot operator). Personally I don't
> like this idiom at all (you
2009/4/20 Rich Hickey :
> If there is just a (def *version* {:major 1 :minor 0 :release 0})
>
> my questions are:
>
> What happens after release to keep subsequent interim versions from
> having the same 'version' as a release? Should we have a :status
> attribute that is :release for releases an
2009/4/20 Stuart Sierra
>
> On Apr 20, 1:48 pm, Rich Hickey wrote:
> > I imagine a (clojure-version) function returning:
> >
> > {:major 1 :minor 0 :release 0}
>
> I'd suggest calling :release something else, like :revision
> or :patch. "release" sounds like a bigger number than major/minor.
>
On 20.04.2009, at 20:00, Timo Mihaljov wrote:
> Is the concept of Abstract Data Types [1] useful in Clojure?
Yes, although the abstraction is necessarily leaky in that you cannot
enforce it in the absence of static typing.
> If yes, how would you implement one?
Like in any other language: by
Konrad added an early implementation of abstract data types to
clojure-contrib (types.clj) you might want to check that out.
I also did some work on supporting more traditional style OO with Spinoza
(structural+behavioral inheritance), but I've sidelined it for the time
being until I find that I ac
Maps aren't ordered so this isn't a good idea anyway.
The reason first/second work is because they call seq on the collection.
(key (nth (seq {:a 1 :b 2 :c 3}) 1)) -> :b
On Mon, Apr 20, 2009 at 2:51 PM, hughw wrote:
>
> Hi all,
>
> Why should 'first and 'second work on maps, but not 'nth?
>
> u
Hi all,
Why should 'first and 'second work on maps, but not 'nth?
user> (key (first {:a 1 :b 2 :c 3}))
:a
user> (key (nth {:a 1 :b 2 :c 3} 0))
; Evaluation aborted.
java.lang.UnsupportedOperationException: nth not supported on this
type: PersistentArrayMap (NO_SOURCE_FILE:0)
[Thrown class clo
Stuart Sierra writes:
> On Apr 20, 1:48 pm, Rich Hickey wrote:
>> I imagine a (clojure-version) function returning:
>>
>> {:major 1 :minor 0 :release 0}
>
> I'd suggest calling :release something else, like :revision
> or :patch. "release" sounds like a bigger number than major/minor.
> Other
On Apr 20, 12:32 pm, Laurent PETIT wrote:
> I think you Timo ask here a very interesting and important question.
>
> It's not just about having encapsulation or not. It's really about designing
> the code so that the library internals can evolve without impact on the user
> part.
In general, Lis
On Apr 20, 1:48 pm, Rich Hickey wrote:
> I imagine a (clojure-version) function returning:
>
> {:major 1 :minor 0 :release 0}
I'd suggest calling :release something else, like :revision
or :patch. "release" sounds like a bigger number than major/minor.
Other than that, makes sense to me.
Maybe
Rich Hickey writes:
> If there is just a (def *version* {:major 1 :minor 0 :release 0})
>
> my questions are:
>
> What happens after release to keep subsequent interim versions from
> having the same 'version' as a release? Should we have a :status
> attribute that is :release for releases and :
I think Konrad's and David's replies confirm my suspicion that I'm
trying to find a solution to a problem that one does not encounter in
Clojure. This makes my example irrelevant and a poor context for the
discussion, so I'm changing the subject and bombard you with a new set
of newbie questions.
On Apr 17, 5:21 pm, Tom Faulhaber wrote:
> Tom's 2 cents:
>
> I think Clojure is basically ready to go to 1.0. I like the idea of
> having a book about Clojure 1.0 go hand in hand with the release.
>
> While I agree that the library management problem is too hard for a
> 1.0 release (and also l
A couple of things. In your initial example, you conflated some things. One
issue is simply a matter of convenience- defining a getter so that you can
use Python object property access (via the dot operator). Personally I don't
like this idiom at all (you find it in Objective-C 2.0 and Javascript).
You can bet that regulatory agencies will look at this deal closely. Not
only in the US and not
only at the deal itself but also how Oracle will behave in the near
future.
Luc
On Mon, 2009-04-20 at 09:09 -0700, Phil Hagelberg wrote:
> Sean Devlin writes:
>
> > *Will Java continue to be open so
On Apr 20, 2009, at 18:13, Timo Mihaljov wrote:
> To put it another way, any answer involving custom support code (new
> macros or the like) is not the one I'm looking for. Being able to
> modify
> the language is very cool, but not being able to solve a simple
> problem
Macros are not "modi
I think you Timo ask here a very interesting and important question.
It's not just about having encapsulation or not. It's really about designing
the code so that the library internals can evolve without impact on the user
part.
Given that no "here is the standard clojure way" was called :
* ei
Hey Sean,
Thanks for the pointer here. There's a lot of commonality, but mostly
I think the products end up being different for two reasons:
1) For the moment, the contrib-autodoc stuff is targeting the
googlecode wiki, which is a weird and gross thing of its own. I've
been thinking of making so
I see the point about being able to add new functions. If you do
something like this, you still have defmonadfn available.
I also think that m-lift can be written so that you don't need to pass
it an argument count, which is another burr under my saddle.
Jim
--~--~-~--~~~
Matt Clark wrote:
> Maybe I'm missing something, but what is wrong with Stuart Sierra's
> solution? I quite like it, and it would probably be more appealing if
> it were encapsulated into a macro.
Frankly, it seemed like a good answer to the wrong question [1] instead
of being a recurring and wi
Sean Devlin writes:
> *Will Java continue to be open source?
It is simply not possible for this to go away. Future development on
Java _could_ be released under developer-hostile licenses, but this
would probably be a good thing if the license were bad enough since it
would make it obvious that
Laurent PETIT wrote:
> To simplify a little bit (both from a library implementor and user
> perspective), why not get rid of the appended dash - ?
>
> Indeed, having an appended dash suggests to me (so it's not apparent
> from the examples) that the user will have to access, for a same object,
I believe there is 0% chance that the JVM will be charged for. I don't
think there has ever been an example of an open source thing becoming
closed source. The JVM is a generic language spec that many people
have implemented. I dont see any changes to "JDBC". First it is not a
product but a spec.
Maybe I'm missing something, but what is wrong with Stuart Sierra's
solution? I quite like it, and it would probably be more appealing if
it were encapsulated into a macro.
(def-propholder person)
(def me (person {:name "Matt Clark"}))
(def-propholder person2
:name
{:getter (fn [record]
Hi again,
2009/4/20 Timo Mihaljov
>
> Laurent PETIT wrote:
> > What do others think about these 2 above statements ?
> >
> > The standard OO approach to information hiding would be private
> fields
> > and accessor methods. Any suggestions for the One True Clojure
> Pattern
> > that
I guess I should have stated my initial concern better. I've had to
use several Oracle products in the past (PL/SQL & 9i), and they
weren't developer friendly. I'm worried about the JVM becoming less
open than it currently is. I can see a lot of technologies that drive
the open source world, an
You have two other function calls
getAdaptedWeightVector
computeActualResponse
Are these recursive as well?
On Sun, Apr 19, 2009 at 11:26 PM, jleehurt wrote:
>
> Hi all, I have the following code that trains a perceptron with the
> given inputs and corresponding desired inputs. For input/output
Hi all, I have the following code that trains a perceptron with the
given inputs and corresponding desired inputs. For input/output
vectors, when the size gets to about 2000, I am getting a
java.lang.StackOverflowError in the following function:
(defn trainPerceptron [beginningWeightVector allInp
On Mon, Apr 20, 2009 at 9:13 AM, Sean Devlin wrote:
>
> Okay, I'm willing to bet this crowd has already seen this:
>
> http://www.sun.com/third-party/global/oracle/index.jsp
>
> Any thoughts on how this affects Clojure?
No effect.
> >
>
--
blog: whydoeseverythingsuck.com
--~--~-~--~
Okay, I'm willing to bet this crowd has already seen this:
http://www.sun.com/third-party/global/oracle/index.jsp
Any thoughts on how this affects Clojure?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" g
Laurent PETIT wrote:
> What do others think about these 2 above statements ?
>
> The standard OO approach to information hiding would be private fields
> and accessor methods. Any suggestions for the One True Clojure Pattern
> that addresses the same problem?
>
>
> I think accessor
On 20/04/2009, at 6:13 PM, fft1976 wrote:
> On Apr 19, 3:20 am, Antony Blakey wrote:
>
>> If I use Clojure commercially, I'll certainly pay for it.
>
> Please do not forget to pay for JVM, Java, Linux, tar and others.
When they start asking for donations, and don't use a GPL license
(which i
Hi,
2009/4/20 Timo Mihaljov
>
> Laurent PETIT wrote:
> > While interesting, this approach seems to me limited to simple cases :
> > * limited in possibilities: you are not able to directly use values of
> > other fields. So in more complex cases, you won't be able to combine
> > calculated valu
Laurent PETIT wrote:
> While interesting, this approach seems to me limited to simple cases :
> * limited in possibilities: you are not able to directly use values of
> other fields. So in more complex cases, you won't be able to combine
> calculated values without code repetition or preprarati
Hi,
Am 20.04.2009 um 08:32 schrieb Timo Mihaljov:
After a bit of googling I found what seems to be the perfect solution:
http://kotka.de/projects/clojure/lazy-map.html
(defn new-person [first-name last-name]
(lazy-struct-map person
:first-name first-name :last-name last-na
On Apr 19, 3:20 am, Antony Blakey wrote:
> If I use Clojure commercially, I'll certainly pay for it.
Please do not forget to pay for JVM, Java, Linux, tar and others.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Apologies for multiple postings
2nd European Lisp Symposium (ELS 2009)
Milan, Italy, May 27-29, 2009
Universita` degli Studi di Milano-Bicocca
www.european-lisp-symposium.org
Hi,
2009/4/20 Timo Mihaljov
>
> Timo Mihaljov wrote:
> > I'm wondering about how to change a data structure without breaking the
> > API used to access it. For example, let's assume that I have a library
> > for dealing with records of people and I'm storing them in structs.
> >
> > (defstru
75 matches
Mail list logo
