That was what I figured. However Clojure currently makes certain kinds of
interop extremely painful, which makes it hard to integrate into existing
frameworks. I'm not proposing anything that would encourage concrete
derivation in pure Clojure programs, but I think that facilitating that
interop is
I think not too favorably. :) See http://clojure.org/datatypes where Rich says
"concrete derivation is bad." I do not think he would be interested in adding
anything to Clojure that included concrete derivation.
--
You received this message because you are subscribed to the Google
Groups "Clo
Alex, what's your feeling about how a reify-like form and a deftype-like
form that supported concrete class extension (as detailed in the other
thread) would be received? If you think there might be interest I can start
a proposal and possibly write the patch as well.
On 15 April 2014 14:32, Alex
It is a non-goal for gen-class (and reify, proxy, etc)to support the
construction of any possible Java class or to fully support every possible
Java feature. That said, particular extensions to existing features might
be useful in reasonable use cases.
On Monday, April 14, 2014 7:56:21 PM UTC-
Well, I'm a bit torn on this one. On the one hand, I'd love to have
something that meets my particular use case (of course!) which I wrote
about here: https://groups.google.com/d/topic/clojure/MznBwxZt4cY/discussion.
I think that case can be met while still keeping the API fairly simple. But
once y
This is unfortunate. I certainly can write a Java class and I expected
that would be the answer. The question for me is whether, as a group, we
see any value in having a consistent interface with the JVM. One could
argue that Clojure does not need any of the interop features it already
has.
gen-class really isn't suitable for doing complicated interop like
annotating fields. It's heavily oriented towards a single means of managing
state, which is a single field generally containing an atom, which in turn
contains your actual state in a map or similar. If you really need multiple
field
On 24 April 2010 10:06, Rich Hickey wrote:
> I've started adding some support for Java annotations,
> Feedback welcome
Neato! I've been hoping for this - thanks :)
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email t
Thank you very much for this new feature. I was able to use it
successfully to create and test a simple EJB. I wrote about this on my
blog and put a demo up on GitHub.
Blog entry:
http://www.deepbluelambda.org/programming/clojure/building-ejbs-with-clojure
GitHub link:
http://github.com/satt
Looks nice from just looking at the gists - I have a small project
where annotations support would actually come in handy as well so will
definitely give this a try shortly.
mark
--
Pull me down under...
On Sat, Apr 24, 2010 at 12:06 PM, Rich Hickey wrote:
> It supports annotations for definte
I've started adding some support for Java annotations, as of this
commit:
Fantastic! I'm just about to do some JAX-WS stuff (which requires
annotations), so this is a welcome change.
The syntax looks no worse than Java's, so no comment on that...
--
You received this message because you are
2010/4/24 Rich Hickey :
> I've started adding some support for Java annotations, as of this
> commit:
>
> http://github.com/richhickey/clojure/commit/fa899d22dceb531d9f5af833ac6af0d956e6bdc7
>
> Example of use:
>
> http://gist.github.com/377213
>
> It supports annotations for definterface/type/reco
On Mon, Aug 24, 2009 at 3:00 AM, ngocdaothanh wrote:
>
> I'm new to Clojure. How can I add @ChannelPipelineCoverage("one")
> annotation to a proxy as in?
>
> http://viewvc.jboss.org/cgi-bin/viewvc.cgi/netty/trunk/src/main/java/org/jboss/netty/example/http/snoop/HttpResponseHandler.java?view=markup
A couple of months late to this discussion, but I thought I'd throw in
my 2¢: annotations are pretty important for more things than just
filling in deficiencies in Java.
For example, SIP Servlets 1.1 — finalized in August 2008 — actively
discourages the use of deployment descriptor entries in fav
On Mar 24, 10:19 am, Sean wrote:
> Some working code would make it a lot easier to understand *exactly*
> what you're looking for. Do you think you could post a few quick
> methods on github?
No need for gist, this will do as an example:
(ns some.namespace
(:gen-class
:methods [^#{:annota
Some working code would make it a lot easier to understand *exactly*
what you're looking for. Do you think you could post a few quick
methods on github? If memory serves, the reflections package should
be a good place to start.
However, you'd need to ask *why* you need this.
If the answer is "
16 matches
Mail list logo
