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

[John W. Eaton]

On 02/23/2015 11:57 AM, Michael Godfrey wrote:
> On 02/23/2015 11:53 AM, Carnë Draug wrote:

> > Should I replace the warning name then? I don't really mind it, but I
> > guess others
> > may be counting on it. Also, if we break backwards compatibility on the warning
> > names like that, then there's no point on having automatic broadcasting throwing
> > both "broadcast" and "language-extension" while we deprecate the first. We might
> > as well only have it throwing "language-extension" warnings.
> >
> > Is this ok?
> >
> > Carnë
> I think that this is OK, but maybe you should wait a bit for other comments.
> Michael

I don't think it's necessary to deprecate a warning ID, so I would just 
change it and disable the warning by default.

I'll leave it up to someone else whether we add warnings for other 
language extensions like ++, +=, unwind_protect.  I don't object to such 
warnings, but I have no particular interest in adding them myself.

Also, for them to be useful, we need a way to exempt code in the Octave 
core from being subject to such warnings.  Perhaps some kind of 
per-directory switch along with a #pragma-like switch for individual 
files?  Note that the per-file switch can't be a run-time thing as some 
language extensions are syntax and should be warned about when the code 
is parsed.

jwe