Alright Phil! Thunder and Lightening! I like it. ;-)
On Mon, Aug 22, 2011 at 10:55 PM, Phil Steitz wrote:
> On 8/22/11 8:42 PM, Greg Sterijevski wrote:
> > If no one has objections, I would like to harmonize simpleregression with
> > the Regression Interfaces. What is the best way to proceed?
>
I think this is already implemented as
walkInXXXOrder(RealMatrixChangingVisitor). I thought it would be handy
(and consistent with RealVector) to have this very method, but it's
true a RealMatrixChangingVisitorFactory would do very nicely.
Sébastien
2011/8/24 Greg Sterijevski :
> Why not use Ted's
Should I open a ticket, or do you want to handle this?
On Tue, Aug 23, 2011 at 5:47 PM, Luc Maisonobe wrote:
> Le 24/08/2011 00:44, Greg Sterijevski a écrit :
>
> I understand you want to support the general case, but why should it
>> necessitate instantiating a ref.
>>
>
> You are right, we cou
Why not use Ted's insight? Instead of a bunch of these "setDiagonal",
"setAll", "setFirstN", ... why not just have a set( MatrixFunction mf ). The
MatrixFunction delegate could handle whatever we want. It would keep the
objects very clean. You could even have a class factory of commonly used
Matrix
Le 24/08/2011 00:44, Greg Sterijevski a écrit :
I understand you want to support the general case, but why should it
necessitate instantiating a ref.
You are right, we could go with an array allocated only upon request.
Luc
On Tue, Aug 23, 2011 at 5:29 PM, Luc Maisonobewrote:
Le 23/08/201
I understand you want to support the general case, but why should it
necessitate instantiating a ref.
On Tue, Aug 23, 2011 at 5:29 PM, Luc Maisonobe wrote:
> Le 23/08/2011 20:45, Greg Sterijevski a écrit :
>
> Hello All,
>>
>> Since math gives eigendecomposition for symmetrics, why even allocate
Le 23/08/2011 20:45, Greg Sterijevski a écrit :
Hello All,
Since math gives eigendecomposition for symmetrics, why even allocate the
array imagEigenvalues ?
What am I missing?
For now, we are limited to symmetric matrices because we did not
implement anything else. However, we did prepare the
Final classes don't always play well with things like aspects and dependency
injection and other things that mangle bytecode or dynamically introduce
subclasses/proxies (I'm thinking SPRING). Perhaps this is not an issue here.
Should these classes be final? Taking the example of FoldLeft - are the
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=11651&projectId=108
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 23 Aug 2011 22:22:39 +
Finished at: Tue 23 Aug 2011 22:27:17 +
Total time: 4m 38s
Build Trigger: Schedule
Hi all guys,
in [functor] component there are several classes with checkstyle
errors[1] of the type
Method '' is not designed for extension - needs to be
abstract, final or empty.
My opinion is that such classes should be final - but what someone
else thinks about it?
TIA, all the best!!
Hello All,
Since math gives eigendecomposition for symmetrics, why even allocate the
array imagEigenvalues ?
What am I missing?
Thanks,
-Greg
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
My vote (not that I have one) would be for 1.6, and to keep 2.0 as the
release when the breaking changes are introduced.
Matthew
On 23 August 2011 09:18, Simone Tripodi wrote:
> Hi all guys,
> I'd suggest to go through 1.6 too, even if we have a precedence in the
> past (before I joined as comm
Hello,
I never contributed to any opensource project (except opening some tickets)
but i think i could help here,
have some experience with the subject, was working on a kind of "recursive
tostringbuilder"
2011/8/23 Henri Yandell
> Switching over to the dev list.
>
> Anyone available to work
Hi Matt,
your suggestion makes indeed a lot of sense! I'll copy the /trunk to a
branch and publish the site, once applied the patch, on my home@asf as
soon as I have spare time today, so we can discuss together clirr
report results.
Many thanks for your hint, have a nice day!!!
Simo
http://people.
Hi all guys,
I'd suggest to go through 1.6 too, even if we have a precedence in the
past (before I joined as committer) when the Digester version was
promoted from 1.8 to 2.0 just switching to JVM and added Generics...
So my "concern" is just make sure we adopt a common policy for every
component a
Switching over to the dev list.
Anyone available to work with Barrie on this?
Thanks,
Hen
-- Forwarded message --
From: Barrie Treloar
Date: Mon, Aug 22, 2011 at 11:39 PM
Subject: [lang] Dev support for LANG-378 new ToStyle to support
MultiLine with Indent
To: u...@commons.apac
17 matches
Mail list logo
