> Second thing is your (ns ..) declarations.
>
I've updated it to use :require instead of :use.
--
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 moder
On Saturday, May 12, 2012 6:28:14 PM UTC-4, Moritz Ulrich wrote:
>
> Have you seen the recent buzz about java.net.URL's hashCode depending
> on the state of the internet[1]?
> Can Exploding Fish do something about this annoyance?
>
> [1]:
> http://michaelscharf.blogspot.de/2006/11/javaneturlo
Have you seen the recent buzz about java.net.URL's hashCode depending
on the state of the internet[1]?
Can Exploding Fish do something about this annoyance?
[1]:
http://michaelscharf.blogspot.de/2006/11/javaneturlequals-and-hashcode-make.html
On Sat, May 12, 2012 at 10:40 PM, Anthony Grimes
wro
Aha! Thanks for explaining this here as well as in detail on IRC and
working through it with me. It does indeed make sense.
Furthermore, we've already had this discussion on IRC, but at least one
person thought that my suggestions above were me being a jerk. Just wanted
to publicly state here t
> It looks like you have written a little mini-library for creating and
> working with association lists. Why on earth would you use association
> lists instead of mas? The seq representation of a map is basically the
> same.
>
> user=> (seq {"foo" "bar"})
> (["foo" "bar"])
> user=> (into {} (seq
Hey there! I was taking a look at the libraries implementation and have a
few suggestions/questions.
Most importantly, what is going on
here:
https://github.com/wtetzner/exploding-fish/blob/master/src/org/bovinegenius/exploding_fish/query_string.clj
It looks like you have written a little mini
Walter Tetzner:
> Maybe that "https" was important, and it
> should have been parsed as "https://broken-cms.com";. In some
> applications, it might make sense to have "https" always win. In
> others, like some sort of proxy, it might depend on the scheme of
> another URL, so you can keep the schem
>Provided examples look very much like
https://github.com/michaelklishin/urly. Does e-f handle
>relative resolution, parsing of broken (technically invalid) URLs?
Yes, it handles relative resolution, as well as normalizing paths:
user> (normalize-path "http://www.test.net/some/uri/../path/./her
Walter Tetzner:
> The source and some documentation (in the README) can be found at
> https://github.com/wtetzner/exploding-fish.
Provided examples look very much like https://github.com/michaelklishin/urly.
Does e-f handle
relative resolution, parsing of broken (technically invalid) URLs?
MK
Whoops. You're right.
On Sun, May 6, 2012 at 11:42 PM, Frank Siebenlist <
frank.siebenl...@gmail.com> wrote:
> … but dolphins are no fish…
>
> On May 6, 2012, at 5:25 PM, Sean Neilan wrote:
>
> > Perhaps a reference to PHP's explode function which is the java
> equivalent of String.split?
> > htt
… but dolphins are no fish…
On May 6, 2012, at 5:25 PM, Sean Neilan wrote:
> Perhaps a reference to PHP's explode function which is the java equivalent of
> String.split?
> http://php.net/manual/en/function.explode.php
> And then URI is the fish.
>
> Or it could be a reference to an unwritten s
Perhaps a reference to PHP's explode function which is the java equivalent
of String.split?
http://php.net/manual/en/function.explode.php
And then URI is the fish.
Or it could be a reference to an unwritten sequel to Hitchhiker's Guide To
The Galaxy where the Dolphins blew up Earth instead of the
But why "Exploding Fish", Walter?
Why? Why?
Poor fish.
--
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
13 matches
Mail list logo
