help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: is octave-3.0.4 production-worthy ?


From: Sergei Steshenko
Subject: Re: is octave-3.0.4 production-worthy ?
Date: Wed, 8 Apr 2009 08:40:57 -0700 (PDT)



--- On Wed, 4/8/09, Jaroslav Hajek <address@hidden> wrote:

> From: Jaroslav Hajek <address@hidden>
> Subject: Re: is octave-3.0.4 production-worthy ?
> To: "Sergei Steshenko" <address@hidden>
> Cc: address@hidden
> Date: Wednesday, April 8, 2009, 7:08 AM
> On Wed, Apr 8, 2009 at 3:50 PM,
> Sergei Steshenko <address@hidden>
> wrote:
> >
> > Hello,
> >
> > I've built recently octave-3.0.4 using the same tools
> I used for
> > octave-3.0.3, and after doing with it some simple
> things I have a feeling
> > something is wrong, for example, max(max(matr))
> produces different results
> > on octave-3.0.4 and octave-3.0.3, and the latter
> results appear to be
> > correct. The matr is a difference of two WAV files.
> >
> > Also, it may be that octave-3.0.3 is faster - my
> subjective feeling.
> >
> > This Email is not an official bug report - obviously,
> I need to provide
> > the exact details, and maybe the problems were due to
> my mistakes, but I
> > decided to ask.
> >
> > If octave-3.0.4 is really considered to be OK, I will
> recheck myself, and if
> > the problems persist, I'll file the reports with full
> details.
> >
> > Thanks,
> >  Sergei.
> >
> >
> >
> 
> there is a known serious bug in octave 3.0.4 regarding
> loading ASCII
> files - 3.0.5 is on the way (tarballs already made).
> maybe this relates to some of your trouble. I'd be very
> skeptical
> about the speed difference.
> 
> cheers
> 
> -- 
> RNDr. Jaroslav Hajek
> computing expert & GNU Octave developer
> Aeronautical Research and Test Institute (VZLU)
> Prague, Czech Republic
> url: www.highegg.matfyz.cz
> 

Sorry, false alarm on my side - both versions show the same.

And I wasn't dealing with ASCII loading.

Please announce in this list when 3.0.5 is released.

Thanks,
  Sergei.


      



reply via email to

[Prev in Thread] Current Thread [Next in Thread]