Re: Please try the alphas and betas!

2011-10-31 Thread Joel Gluth
Worth pointing out that the Clojure team don't have to do this
necessarily - a motivated person could set up a CI server that
monitors pre-release SNAPSHOTS on one side, and takes code
snippets/lein projects/gists/test-is packages on the other?

On Sun, Oct 30, 2011 at 4:04 PM, Colin Yates colin.ya...@gmail.com wrote:
 Whacky idea - is there a way for people to submit snippets which are
 run as part of the CI process?
-- 
[what were the skies like when you were young?]

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: Is there a reader setting support BigDecimal by default?

2011-10-20 Thread Joel Gluth
On Tue, Oct 18, 2011 at 3:47 PM, Tassilo Horn tass...@member.fsf.org wrote:
 Scott Hickey jscotthic...@gmail.com writes:
 And usually, you should refrain from using floating points at all, no
 matter if BigDecimal or Double.

I thought BigDecimal with was not a floating point in the traditional
sense (ie., subject to all of the usual rounding horror, unless you
ask it to be)? That is, you can do decimal calculations exactly using
it.
-- 
[what were the skies like when you were young?]

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: sharing multiple jogl opengl contexts in clojure

2010-04-21 Thread Joel Gluth
On Apr 20, 4:46 pm, Josh Stratton strattonbra...@gmail.com wrote:
 But I can't seem to call createGLPbuffer w/o getting an exception.
SNIP/
 Caused by: java.lang.IllegalArgumentException: No matching method:
 createGLPbuffer

This one is because the createGLPbuffer method is not static; you need
to have created a GLDrawableFactory first using getFactory():

(.createGLPbuffer (GLDrawableFactory/getFactory (GLProfile/
getDefault)) nil nil 1 1 nil)

The GLCapabilities argument needs to be set, otherwise you'll get a
NullPointerException at this point.

The simplest invocation I could come up with that returned a
GLPbufferImpl was this:

(let [profile (GLProfile/getDefault)]
(.createGLPbuffer (GLDrawableFactory/getFactory profile)
(GLCapabilities. profile) nil 1 1 nil))

You can take it from here with different profiles, capabilities,
choosers etc.

J

PS I'm using Clojure 1.1 and JOGL 2.0.

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: sharing multiple jogl opengl contexts in clojure

2010-04-20 Thread Joel Gluth
 Right now it seems calling (.getContext (new GLCanvas)) returns nil

Right. The context doesn't get set at construction, but will be set by
the time the canvas gets passed to any of the GLEventListener methods.

The Javadoc mentions that the underlying context may need to get
created and destroyed multiple times as components get added and
removed, but it seems to imply that the GLContext object itself
provides a stable handle to whatever the current underlying context
is. So you might be able to share them.

Another possibility though is that you don't *need* to share them...
and looking at what's in the one I get back, I notice that it has AWT
window handles in its members, so maybe that's not intended after all.

 I'm curious in general how an OpenGL program should properly be
 written when dealing with multiple windows.

So am I, now :)

J

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: sharing multiple jogl opengl contexts in clojure

2010-04-20 Thread Joel Gluth
Further, from the JOGL user guide:

In the JSR-231 abstractions, a context is always associated with
exactly one drawable.

I guess that answers that question. So, while we certainly might want
to share some of our GLish state between windows, the Context is not
the right vehicle...

J

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


primitive arrays, am I reading this right?

2010-04-19 Thread Joel Gluth
Hi all,

(There is an old thread on a similar topic to this, but I seem to be
unable to reply to the group about it, only to the author).

I've been using Clojure this last week, and in general enjoying it
very much. There have been a small number of jarring moments though,
to do with Java interop, so I thought I'd check in with my questions.

The main one comes from having a (third-party) Java class that has
methods a bit like this:

class C {
public void floatMethod(float f) { /* ... */ }
public void floatArrayMethod (float[] argv, int flags) { /* ...
*/ }
}

The argument unboxing that Clojure does with method calls means that
this worked fine:

(.floatMethod (C.) (float 1))

So, lulled into a false sense of knowing what was going on, I tried
this:

(.floatArraymethod (C.) (into-array [(float 1) (float 2)]) 0)

..and got a ClassCastException. The right method gets found,
presumably just by arity, but the array that gets passed has type
java.lang.Float[] (which I would have known had I RTFM properly).

It turns out that the unboxing doesn't extend to array types. Which I
can understand as a design decision, though it would certainly be nice
and sugary otherwise. However, it leaves me doing things like this:

(def floatarray (make-array Float/TYPE 2))
(for [i (range (alength floatarray))] (aset floatarray i (float ([1 2]
i

Aside from the misuse of 'for' (which then needs to be iterated to
cause the side-effects), what am I missing here? Hints on idiomatic
Clojure as well as my primitives question are most welcome.

J

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: primitive arrays, am I reading this right?

2010-04-19 Thread Joel Gluth
 Did you try (into-array Float/TYPE [(float 1.0) (float 2.0)])? I'm not
 sure it works, though. I haven't much done with primitives up to now.

Aha. It does work. The key bit of information being that there was
another way to call into-array (which I actually speculated about
being a good addition - next time I have that thought, I'll bash it
straight into the REPL and see if someone else has had it too).

The page I had been looking at (http://clojure.org/java_interop#Java
%20Interop-Arrays-%28into-array%20coll%29) didn't mention a way of
specifying the element type explicitly with into-array, which was
exactly what I needed :)

And the happy clojure experiences continue... thanks very much.

J

PS Clojure 1.1 seems happy to make floats from [1.0 2.0], hurrah.

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en


Re: Any Clojure job out there?

2010-04-19 Thread Joel Gluth
On Apr 18, 11:23 pm, Steven Shaw stes...@gmail.com wrote:
 You could see each of those jobs saying Java Developer as a potential
 Clojure job :).

In particular, I'd be thinking that places who use Hadoop (and similar
things) would be the kind of jobs to look at, with a view to bringing
your new favourite language in through the back door.

J

-- 
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en