GC is not a problem if you are repeatedly allocating large objects. The
time to fill in the large objects massively dominates the GC time because GC
effort is proportional mostly to the *number* of objects, not the total
*size*.
That said, if you have large objects that vary in size you could be
On 5/10/11 9:47 PM, Sébastien Brisard wrote:
> Le 11/05/11 06:34, Phil Steitz a écrit :
>> On 5/10/11 9:18 PM, Sébastien Brisard wrote:
>>> Great!
>>> So we are more or less back to my initial proposition (see
>>> corresponding wiki).
>>> To sum up, we will define a new interface, called LinearOper
Le 11/05/11 06:34, Phil Steitz a écrit :
On 5/10/11 9:18 PM, Sébastien Brisard wrote:
Great!
So we are more or less back to my initial proposition (see
corresponding wiki).
To sum up, we will define a new interface, called LinearOperator
(should we make it RealLinearOperator? That would be consi
On 5/10/11 9:18 PM, Sébastien Brisard wrote:
> Great!
> So we are more or less back to my initial proposition (see
> corresponding wiki).
> To sum up, we will define a new interface, called LinearOperator
> (should we make it RealLinearOperator? That would be consistent
> with the hierarchy AnyMatr
Great!
So we are more or less back to my initial proposition (see corresponding
wiki).
To sum up, we will define a new interface, called LinearOperator (should
we make it RealLinearOperator? That would be consistent with the
hierarchy AnyMatrix/RealMatrix), with the following methods
LinearOpe
> >> [...]
> >> The question is thus: Is it OK to provide pointless methods?
> >> I also wonder whether it is reasonable to _generate_ state variables just
> >> so that the accessors can return them.
> >> Usually, when a exception is constructed, it is _passed_ data that provide
> >> the context of
On May 10, 2011, at 8:18 AM, "Sebastien Brisard"
wrote:
>> [...]
>> The question is thus: Is it OK to provide pointless methods?
>> I also wonder whether it is reasonable to _generate_ state variables just
>> so that the accessors can return them.
>> Usually, when a exception is constructed,
> [...]
> The question is thus: Is it OK to provide pointless methods?
> I also wonder whether it is reasonable to _generate_ state variables just
> so that the accessors can return them.
> Usually, when a exception is constructed, it is _passed_ data that provide
> the context of the failure (i.e.
> > [...]
> > > In fact, such an exception would be raised if the program stumbles
> > > upon to vectors x and y such as x'Ay differs from y'Ax. So, the
> > > existing NonSymmetricMatrixException would be a particular case of a
> > > more general (BasicNonSymetricMatrixException ?), with x = ei and
2011/5/10 Gilles Sadowski
>
> On Mon, May 09, 2011 at 08:52:57PM +0200, Sébastien Brisard wrote:
> > Le 09/05/11 17:31, Phil Steitz a écrit :
> > >On 5/9/11 4:27 AM, Gilles Sadowski wrote:
> > >>Hi.
> > >>
> > >>>I'm currently trying to integrate my implementation of iterative
linear
> > >>>solv
On Mon, May 09, 2011 at 08:52:57PM +0200, Sébastien Brisard wrote:
> Le 09/05/11 17:31, Phil Steitz a écrit :
> >On 5/9/11 4:27 AM, Gilles Sadowski wrote:
> >>Hi.
> >>
> >>>I'm currently trying to integrate my implementation of iterative linear
> >>>solvers in the commons-math architecture.
> >>Tha
Le 09/05/11 17:31, Phil Steitz a écrit :
On 5/9/11 4:27 AM, Gilles Sadowski wrote:
Hi.
I'm currently trying to integrate my implementation of iterative linear
solvers in the commons-math architecture.
Thanks for contributing.
Among other things, I want to reuse
as many existing exceptions a
On 5/9/11 4:27 AM, Gilles Sadowski wrote:
> Hi.
>
>> I'm currently trying to integrate my implementation of iterative linear
>> solvers in the commons-math architecture.
> Thanks for contributing.
>
>> Among other things, I want to reuse
>> as many existing exceptions as possible. I've come accross
Hi.
> I'm currently trying to integrate my implementation of iterative linear
> solvers in the commons-math architecture.
Thanks for contributing.
> Among other things, I want to reuse
> as many existing exceptions as possible. I've come accross the following
> points
> 1. naming the parameters
Dear all,
I'm currently trying to integrate my implementation of iterative linear
solvers in the commons-math architecture. Among other things, I want to reuse
as many existing exceptions as possible. I've come accross the following
points
1. naming the parameters in the constructor of NonSquareMat
15 matches
Mail list logo