[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: warn when core functions are shadowed
From: |
John W. Eaton |
Subject: |
Re: warn when core functions are shadowed |
Date: |
Tue, 2 Feb 2010 02:13:53 -0500 |
On 2-Feb-2010, Jaroslav Hajek wrote:
| 2010/2/2 John W. Eaton <address@hidden>:
| > On 2-Feb-2010, Jaroslav Hajek wrote:
| >
| > | > If we do want to add a command-line option, then we can make it work for
| > | > all warning flags:
| > | >
| > | > --warning ID set warning state for ID to "on"
| > | > --no-warning ID set warning state for ID to "off"
| > |
| > | Cool idea.
| >
| > Thinking about this a little more, maybe it should be
| >
| > --warning-on ID
| > --warning-off ID
| > --warning-error ID
| >
|
| Perhaps. But I think the third one is mostly useless, because nobody
| in his right mind wants errors in startup files. Afterwards it can be
| done in .octaverc.
Maybe you want to be able to run Octave in an environment where it is
inconvenient to have a custom .octaverc file?
jwe
- warn when core functions are shadowed, Jaroslav Hajek, 2010/02/01
- Re: warn when core functions are shadowed, Dupuis, 2010/02/01
- Re: warn when core functions are shadowed, Robert T. Short, 2010/02/01
- Re: warn when core functions are shadowed, Jaroslav Hajek, 2010/02/01
- Re: warn when core functions are shadowed, Robert T. Short, 2010/02/01
- Re: warn when core functions are shadowed, John W. Eaton, 2010/02/01
- Re: warn when core functions are shadowed, Jaroslav Hajek, 2010/02/02
- Re: warn when core functions are shadowed, John W. Eaton, 2010/02/02
- Re: warn when core functions are shadowed, Jaroslav Hajek, 2010/02/02
- Re: warn when core functions are shadowed,
John W. Eaton <=
warn when core functions are shadowed, John W. Eaton, 2010/02/01