Re: [ANN] 'Elements of Clojure' is complete

Hey, glad to hear it. Excited to read the completed version over the holidays. On Sunday, December 2, 2018 at 4:25:42 PM UTC-7, Zach Tellman wrote: > > I'm very happy to announce, only two and a half years after the release of > the first chapter, that Elements of Clojure is completely

Re: Confusing Regex Behavior

See also Java's regex "Comparison to Perl 5" at https://docs.oracle.com/javase/9/docs/api/java/util/regex/Pattern.html. However, you are in for a treat! Perl is insanely great. Clojure is simply great. -- You received this message because you are subscribed to the Google Groups "Clojure"

RE: [ANN] Clojure 1.10.0-RC3

We have 1.10 RC 3 in production. So far, so good. Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: clojure@googlegroups.com on

Re: Confusing Regex Behavior

Oh, handy to know. Thanks. (I come from a mostly Perl background, where regular expressions are first-class objects and operations on/with them are baked in. The Java approach to regexp that Clojure builds on is a little odd to me. But then, Perl is more than a little odd to a lot of people...)

[ANN] com.walmartlabs/schematic 1.2.0

Schematic is a Clojure library which aids in assembling Component systems from configuration data. * Expects components to implement the Component/Lifecycle protocol * Prefers pure data for declaring dependencies * Provides a simple mechanism for assembling/starting just a subset of Components *

Re: GraalVM's native-image incompatible with Clojure's eval?

Thanks a lot for the links. Indeed it seems that parts of Clojure inevitably end up using reflections unless anotated. -- 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

Re: Confusing Regex Behavior

You don't need to use re-matcher in that example - the output of re-find with the regex and the string is identical. If you are using the matcher to collect a series of matches in one string, you can also uses re-seq which returns a lazy-seq of the matches of your regex in the string. On Tue, Dec

Re: Confusing Regex Behavior

Oh, that might be it. The newline at the end of the string might be what is throwing a wrench into things. Though, to be fair, when I used re-matches yesterday the newline wasn't an issue. Nonetheless, I can work with re-find/re-matcher for now. On Tue, Dec 4, 2018 at 11:28 AM Andy Fingerhut

Re: Confusing Regex Behavior

The doc string for re-matches says that it uses java.util.regex.Matcher.matches(). The Java doc page for the class java.util.regex.Matcher [1] says "The matches method attempts to match the entire input sequence

Confusing Regex Behavior

I must be doing something wrong here, but I cannot figure this out. The following results in "nil" from re-matches: (re-matches #"\[((\d+)-(\d+)-(\d+) (\d\d):(\d\d))\] (.*)" "[1518-05-27 00:42] falls asleep\n") This, however, properly matches the line and produces the backreferences: (re-find