Hi Arthur,
I don't have any principle objections against your implementation.
I just don't want it as a replacement for the AtomicSafeInitializer
class. The latter was designed and announces itself to use only atomic
variables for its synchronization and no other types of locks. This
premise no l
A few questions coming to mind here:
- First off, how do we move this forward?
- What do we do with the new implementation?
- What is a good way to address the busy-wait in the original code?
- What is a good way to address the fact that all threads will
busy-wait in the
Hi.
See
https://issues.apache.org/jira/browse/MATH-1206
The "getChiSquare()" was in the older API (in "o.a.c.m.optim)
but not in the refactored one (in "o.a.c.m.fitting.leastsquares").
I suppose that it was deemed obvious that the chi2 could be
obtained as the square of the value returned by
Hi all,
Le 25/02/2015 20:24, Thomas Neidhart a écrit :
> On 02/25/2015 04:37 PM, Phil Steitz wrote:
>> Seems a little silly to be spending time debugging openjdk bugs.
>> Can we just set Jenkins up to use an Oracle released JDK?
>
> Yeah sure, it might be a waste of time, it is still annoying to
Dave, we'd still appreciate your comment on BCEL-209 if you can take a look:
https://issues.apache.org/jira/browse/BCEL-209
Thanks,
Ben
On Mon, Feb 23, 2015 at 5:51 AM, Emmanuel Bourg wrote:
> Le 23/02/2015 14:11, Dave Brosius a écrit :
>
> > One specific case is that annotations are now comin
2015-02-25 15:20 GMT+01:00 Benedikt Ritter :
>
>
> 2015-02-23 21:47 GMT+01:00 Oliver Heger :
>
>>
>>
>> Am 23.02.2015 um 21:35 schrieb Benedikt Ritter:
>> > Oliver Heger has raised concerns about this commit in JIRA [1]:
>> >
>> >> This is a strong change in the behavior of this class. The main
>>
