:+DisableExplicitGC is because some software authors try to be
smart and insert System.gc() calls at appropriate points. They
tend to fail, so if you select a GC that actually does handle your
case with minimal pauses you also want to disable the artificially
induced full GC:s.
--
/ Peter Schuller
(such as
read-line).
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe
the case is with Python and Ruby.
I'd be interested in looking into getting some kind of draft
implementation of this, if people think it's a good idea (though I
can't make time commitments - busy busy busy).
--
/ Peter Schuller
--
You received this message because you are subscribed
demands are imposed on the blackbox in order for it to
play nice with the packaging infrastructure.
At this time I haven't thought this through enough in the case of
Clojure to offer a practical suggestion that does not involve
system-wide library paths.
--
/ Peter Schuller
--
You received
with in the Maven community?
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe
of not downloading during build.
One should probably look into doing something similar for other
packaging systems then.
Guess I need to bite the bullet and learn Maven ;)
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
will have changed since the original
publications of the papers, but they should offer good insight.
--
/ Peter Schuller
--
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
clojure).
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from
).
The simplest fix (assuming everyone agrees it's a problem) is to
simply change it not to, but I suggested the option to allow for both
- but the default should presumably be to *not* follow symlinks.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure
to
confirm it.
In that case, I suggest putting a huge warning in the documentation at
least, as to the potential destructiveness of the operation.
(Ant's trick with canonical names feels shaky in the context of
something as general-purpose as delete-file)
--
/ Peter Schuller
--
You received
/local/share/java/classes/clojure.jar clojure.main test.clj
test
--
/ Peter Schuller
--
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
not valid clojure, or was it just an empty file? If the
latter, no output is expected, as you point out.
--
/ Peter Schuller
--
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
used to
primarily sitting at the zsh command line,I would not be able to use
the plain REPL without it or I'd go nuts ;)
--
/ Peter Schuller
--
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
means to avoid deadlock, meaning that while you will
not deadlock in the message passing system you can cause memory
exhaustion.
Disclaimer: While I've played with erlang I'm not really that into it,
please correct me someone if I've misrepresented anything.
--
/ Peter Schuller
--
You received
. The claim is rather that
the intended fundamental model implemented by an actor is not one of
shared mutable state.
--
/ Peter Schuller
--
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
, with the originally posted article.
--
/ Peter Schuller
--
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 with your
first post
the perl (or whatever the original is) precedent
from chomp/chop, there is precedent for trim/left trim/right trim too.
What *would* one call trim/ltrim to make them consistent with chomp?
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group
() itself keeps itself running until it manages to empty the
queue, at which point a future enqueue() will once again re-start
execution.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
Unless I am misunderstanding the context in which the code runs, I
Which I was. Please ignore my previous post (sorry, think before I
post... think before I post...) and consider me joined in the OP's
question.
--
/ Peter Schuller
--
You received this message because you are subscribed
to great
effect.)
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from
(),
allowing it to determine whether or not it was responsible for such a
state transition, in which case it schedules the action for execution.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email
recommentation for GUI:s... I never got
that. I prefer just running with -server and perhaps turning on
CMS/G1. Maybe if I were severely memory constrained...)
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
Does anybody know how I can produce a sorted-set from a list without
overflowing the stack on a list of up to 20 items?
I'm thinking I must be misunderstanding the question, but (apply
sorted-set lst)?
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
about
the intent.
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe
that eliminating the overhead associated with a ref can be
considered an irrelevant overhead.
--
/ Peter Schuller
--
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
/syntax-and-semantics.html
--
/ Peter Schuller
--
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 with your
first post
And that should install (although it does so very silently) clojure
into your (user) local maven repository:
ls -ltr ~/.m2/repository/org/clojure/clojure/1.2.0-master-SNAPSHOT
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
, some performance for FreeBSD 8/x86-64 with:
openjdk6: 15 seconds slurp, 3.0 seconds slurp2
openjdk7 (fastdebug): 14.5 seconds slurp, 2.0 seconds slurp2
And slurp2 as a function of buffer size (single run each):
1: 17.8 seconds
128: 2.92 seconds
1024: 2.88 seconds
4096: 3.12 seconds
--
/ Peter
or not,
but in any case I think it is good default behavior to always strive
to do I/O chunk-wise, regardless of whether the expectation is that
the underlying stream is fast (for some definition of fast).
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
if you
consider that lists are not functions of indexes (while vectors and
java arrays are).
--
/ Peter Schuller
--
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
there on the fact that I wrote 'scode' on the contributor agreement I
mail:ed Rich?
--
/ Peter Schuller
--
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
I can register another account (no problem), but what implications are
there on the fact that I wrote 'scode' on the contributor agreement I
mail:ed Rich?
I just registered peterschuller.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups
/ruby situation is not very good there unless
you're heavily into cygwin or something.
--
/ Peter Schuller
--
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
, but if
it matters to you do have it be persistent/immutable...
--
/ Peter Schuller
--
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
. Take it with a grain of salt. But know that
I'm speaking *as a developer*, just not as a developer *of those
things* that I am trying to find/use/read about.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
FYI, the main page of ccw is manually maintained and contains up to date
information wrt current plugin status.
That's maybe why you didn't have to /specifically/ complain 'bout ccw itself
;-)
Yes, it seems more obviously maintained than most :)
--
/ Peter Schuller
--
You received
case (but I
am certainly no expert here).
Would not multimethods be the main candidate for invokedynamic?
--
/ Peter Schuller
--
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
://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
--
/ Peter Schuller
--
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
,
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from this group, send
* GC kicking in
-XX:+PrintGC
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
Will tell you immediately.
A couple of hundred ms seems very very plausible for GC. What is your
target/desired maximum pause time?
--
/ Peter Schuller
--
You received this message because you are subscribed
it.
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from this group, send
being, say, shift_JIS or something which is then
interpreted as, say, UTF-8 and luckily/unluckily not failing, instead
producing a valid unicode string of length 27.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
I'm on Snow Leopard. I think there's something wrong with Terminal
So my guess is that for some reason the terminal is not using the same
encoding as whatever is expected by Java (presumably Java looks at
LANG and friends).
--
/ Peter Schuller
--
You received this message because you
,
but I think it would be a good thing to have in cases where one might
now otherwise use (time ..).
--
/ Peter Schuller
--
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
WIth regards to benchmarking that accurately discounts loop overhead;
it seems to me that even if you apply elaborate logic, if the thing
you're benchmarking is so small that looping overhead becomes
significant, you risk making the benchmark subject to subtle
variations anyway,
--
/ Peter
. I started writing something and meant to discard it, but
accidentally hit send...
--
/ Peter Schuller
--
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
I don't disagree that links would be useful, FYI you can usually just do:
(doc X)
The exception seems to be special forms which give references to the web site.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
used
it enough to have a good feel for it. So my input above comes mostly
from a general perspective.
--
/ Peter Schuller
--
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
*while* also meaningful, structured and
non-clashing.
+1 for clojure :)
--
/ Peter Schuller
--
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
of stack sizes and in terms of switching
overhead). In other words, the day where having a few hundred thousand
concurrents connections does *not* imply that you must write your
entire application to be event based, is when I am extremely happy ;)
--
/ Peter Schuller
--
You received this message
and complexity
of the system grows?
--
/ Peter Schuller
--
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 with your
first post
.
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from this group
))]
...)
Instead of every potential caller having to do mostly the same thing
anyway. What do you think?
--
/ Peter Schuller
--
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
would provide a
side-effectful interface as its primary interface, but with the
specific ability to produce a persistent snapshot.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
structures though, with a similar inappropriateness for a functional
interface, where full participation as a persistent data structure
with respect to STM would be desirable.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
-typing lots of stuff (while clearly
not preserving actual state other than history)?
--
/ Peter Schuller
--
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
on.
--
/ Peter Schuller
--
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 with your
first post.
To unsubscribe from this group, send
You can build a scalable app with Conjure on Jetty. You don't need an
evented server like Aleph or node.js to build a scalable app.
Depends on what you mean by scalable. If you want to keep 250 000
concurrent mostly idle connections, you'll likely want to be event
based.
--
/ Peter Schuller
relevant to point out that no, clojure doesn't inherently
get you massive concurrency even if you can most definitely do
threading/asynch mixing with clojure like with most languages.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group
Is there a more terse way to express the same thing? I suspect there
is a mechanism similar to (or perhaps a generalization of) composition
for that, but I couldn't find it in the API docs.
http://stackoverflow.com/questions/2822140/function-composition-clojure
--
/ Peter Schuller
--
You
there will be the non-lazy return value of
Pattern.split() in memory.
Also, is it considered idiomatic to rely on lazyness in cases like this, anyone?
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
only apply to the list of list
that concat is supposed to be concatenating; the contents of *those*
lists would still be lazy (if the original list was lazy to begin
with).
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
to its
head, will result in memory use similar to that which you may have
expected if the data structure was not lazy to begin with.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
: http://tromey.com/elpa/
There is something similar for vim (I'm sure a vim user will chime in).
If you're rather looking for overall workflows/program structure/best
practices etc - good question. :)
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups
impacts which aren't fixed by just avoiding allocation as
is mentioned in the erjang wiki page. Or is this over-stating the
problem?
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
move) it
simply returns nil or some value associated with that key).
--
/ Peter Schuller
--
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
was not able to trigger any memory use
beyond what I expected.
Do you have a self-contained fully working example that you can point
to (preferably with your actual data files + code, but otherwise just
the code)?
--
/ Peter Schuller
--
You received this message because you are subscribed
cache locality, etc).
(Note that I'm not arguing the point of whether or not it should be
committed before 1.2, but I'm genuinely interested in why not reading
one character (or byte) at a time would be a controversial change.)
--
/ Peter Schuller
--
You received this message because you
is higher the
lower the pause time goal you specify. An starter command line to play
with (preferably with jdk 1.7) might be:
-XX:+UnlockExperimentalVMOptions -XX:+UseG1GC
-XX:MaxGCPauseMillis=15 -XX:GCPauseIntervalMillis=20
--
/ Peter Schuller
--
You received this message because you
+1 on improving stack traces (though I haven't had experience with
clj-stacktrace, other than what I have read on this list).
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure
at the heap size after a full collection.
--
/ Peter Schuller
--
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 with your
in terms of time spent doing GC
that the JVM throws an exception, yet bad enough to cause very
frequent full GC:s at considerable cost in CPU time.)
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email
For 30 second worth of calculations, this doesn't look to bad to me.
If that was for all of the 30 seconds then yeah, GC is not the issue.
--
/ Peter Schuller
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email
), but the
need to do so tends to be over-stated in my opinion. But if I'm
missing something I'd like to know about it :)
--
/ Peter Schuller
--
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
74 matches
Mail list logo