octave-maintainers
[Top][All Lists]
Advanced

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

Re: turning "Octave:broadcast" warning off by default


From: Olaf Till
Subject: Re: turning "Octave:broadcast" warning off by default
Date: Thu, 19 Feb 2015 19:07:58 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Feb 19, 2015 at 12:57:58PM +0000, Carnë Draug wrote:
> On 19 February 2015 at 12:36, Moreno Marzolla
> <address@hidden> wrote:
> > On 19/02/2015 11:59, Carnë Draug wrote:
> >>
> >> Hi
> >>
> >> automatic broadcast was introduced in 3.6 and at the time we enabled
> >> warnings by default because it was very new.  This is not true anymore.
> >> Should we turn it off by default for 4.0?
> >
> >
> > Will the "Octave:broadcast" warning ID be still available?
> 
> Yes.
> 
> > I am not very
> > good at keeping track whether long expressions return a row or column
> > vector, so automatic broadcasting introduced problems

Similarly to this, I had the impression that it's easy to trigger
broadcasting inadvertently. Maybe the warning should be left on by
default for this reason. Are you sure the warning was only there
because broadcasting was new?

Olaf

> in my queueing package
> > that I was able to track down by adding the line
> >
> > warning ("error", "Octave:broadcast");
> >
> > to my .octaverc.
> 
> If you do this, then your code will error when Octave functions themselves
> use broadcasting so you probably don't want to do it.  Using the warning
> "local" option will also not do it since it propagates up the stack, so if
> you add it to you octaverc file, it will still affect the whole Octave
> session.
> 
> Carnë
> 

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

Attachment: signature.asc
Description: Digital signature


reply via email to

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