For Groovy users, in the upcoming Groovy 2.5 release, Groovy's CliBuilder
provides an annotation-based layer on top of [cli]. Most of CliBuilder
relies heavily on Groovy being there but the annotation layer on top much
less so apart from the Closure converters. In any case, it's an example of
provi
For the curious,
I'd love to see [cli] evolve into something like JCommander [1] and it's
annotation-based system.
In the meantime, I use JCommander mostly but some [cli] in some old
projects that are in maintenance mode. JCommander is great but is not
perfect or complete, so I created some add-o
Hi B,
Random day today, I am not sure I can work on this. Feel free to proceed in
what ever way you best see fit. I trust you :-)
Gary
On Oct 30, 2016 10:57 AM, "Benedikt Ritter" wrote:
> Hello Gary,
>
> please see my comments in CSV-201.
>
> Thank you,
> Benedikt
>
> Gary Gregory schrieb am
Hello Gary,
please see my comments in CSV-201.
Thank you,
Benedikt
Gary Gregory schrieb am Fr. 28. Okt. 2016 um 17:05:
> I do not think reverting is right since the previous is obviously bogus, to
> me, that is. Throwing a RE is never useful, again IMO. We should just
> evolve the code from he
On Sun, 30 Oct 2016 00:40:47 -0700 (PDT), wilbur wrote:
I am fine to submit a PR that reverts LUDecomposition to the standard
method
used in Jama.
Is that method better in all cases (w.r.t. performance _and_
accuracy)? [If there are trade-offs, it might be interesting
to provide both alternat
I am fine to submit a PR that reverts LUDecomposition to the standard method
used in Jama.
--Wilhelm
--
View this message in context:
http://apache-commons.680414.n4.nabble.com/Re-Math-Re-LU-decomposition-very-SLOW-commons-math3-linear-tp4692297p4692305.html
Sent from the Commons - Dev mailin
