headers
James R. Phillips | 1 Dec 2005 17:44
Picon
Favicon

Fwd: Updated: octave-2.1.72-1


--- "James R. Phillips" <antiskid56-cygwin <at> yahoo.com> wrote:

> Date: Thu, 1 Dec 2005 08:28:38 -0800 (PST)
> From: "James R. Phillips" <antiskid56-cygwin <at> yahoo.com>
> Subject: Updated: octave-2.1.72-1
> To: cygwin-announce <at> cygwin.com
> 
> INFO
> ====
> The cygwin octave package has been updated to release 2.1.72-1.
> 
> Changes:
> + Update to new upstream release 2.1.72.  This is the latest release in the
> "testing" branch of octave development.  The release incorporates important
> bug
> fixes.  Further information on the octave release branches is available at
> http://www.octave.org.
> 
> More information on the cygwin 2.1.72-1 release is in the
> octave-2.1.72.README
> file.
> 
> GNU Octave is a (mostly Matlab (R) compatible) high-level language, primarily
> intended for numerical computations.  It provides a convenient command-line
> interface for solving linear and nonlinear problems numerically.
> 
> Octave Home Page: http://www.octave.org
> 
> UPDATE
(Continue reading)

Permalink | Reply | 0 comments |
headers
James R. Phillips | 1 Dec 2005 17:44
Picon
Favicon

Fwd: Updated: octave-forge-2005.06.13-5


--- "James R. Phillips" <antiskid56-cygwin <at> yahoo.com> wrote:

> Date: Thu, 1 Dec 2005 07:52:00 -0800 (PST)
> From: "James R. Phillips" <antiskid56-cygwin <at> yahoo.com>
> Subject: Updated: octave-forge-2005.06.13-5
> To: cygwin-announce <at> cygwin.com
> 
> INFO
> ====
> The cygwin octave-forge package has been updated to release 2005.06.13-5.
> 
> Changes:
> 
> + Modified installation directory structure to remove  dependence on
> installed
> version of octave
> 
> More information in the octave-forge-2005.06.13-5.README file.
> 
> The octave-forge project contains over 500 contributed functions for GNU
> Octave
> which are not in the main distribution. These functions are grouped according
> to the following subdirectories: audio, comm, control, general, geometry,
> ident, image, io, linear-algebra, miscellaneous, optim, path, plot,
> set,signal,
> sparse, specfun, special-matrix, splines, statistics, strings, struct,
> symbolic, time. The Cygwin distribution of octave-forge also incorporates
> m-files from the octave-ci collection.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
John W. Eaton | 6 Dec 2005 21:18
Picon

message ids for warnings and errors

I've started to implement the

  warning (msgid, fmt, ...)
  error (msgid, fmt, ...)

feature.  This will allow us to also do things like

  warning off MATLAB:divideByZero

and (probably) eliminate all the warn_* built-in variables.  I would
rather not tag our warning and error messsages internally with
"MATLAB:", and I'm not a big fan of StudlyCaps so perhaps we would
have message IDs like "Octave:divide_by_zero" instead, with a lookup
table so that this is equivalent to MATLAB:divideByZero (unless we can
rely on a uniform translation like Octave -> MATLAB and _[a-z] ->
[A-Z]).  Does anyone know of a comprehensive list of IDs that Matlab
uses for warnings?

Thanks,

jwe
Permalink | Reply | 19 comments |
headers
Stefan van der Walt | 6 Dec 2005 22:32
Picon
Picon
Favicon

Re: message ids for warnings and errors

On Tue, Dec 06, 2005 at 03:18:50PM -0500, John W. Eaton wrote:
> I've started to implement the
> 
>   warning (msgid, fmt, ...)
>   error (msgid, fmt, ...)
> 
> feature.  This will allow us to also do things like
> 
>   warning off MATLAB:divideByZero
> 
> and (probably) eliminate all the warn_* built-in variables.  I would
> rather not tag our warning and error messsages internally with
> "MATLAB:", and I'm not a big fan of StudlyCaps so perhaps we would
> have message IDs like "Octave:divide_by_zero" instead, with a lookup
> table so that this is equivalent to MATLAB:divideByZero (unless we can
> rely on a uniform translation like Octave -> MATLAB and _[a-z] ->
> [A-Z]).  Does anyone know of a comprehensive list of IDs that Matlab
> uses for warnings?

I wonder how consistent they are in the usage of these strings. The
best description I could find is at

http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_prog/ch12_er7.html#prog_message_identifiers

and it doesn't refer to a list of pre-defined identifiers.

My vote goes for the lookup-table, rather than the string translation.

Regards
Stéfan
(Continue reading)

Permalink | Reply | 18 comments |
headers
Bill Denney | 6 Dec 2005 23:21
Favicon

Re: message ids for warnings and errors

On Tue, 6 Dec 2005, Stefan van der Walt wrote:

> I wonder how consistent they are in the usage of these strings. The
> best description I could find is at
>
> http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_prog/ch12_er7.html#prog_message_identifiers
>
> and it doesn't refer to a list of pre-defined identifiers.
>
> My vote goes for the lookup-table, rather than the string translation.

That looks like what I see as well.  These identifiers are written in by 
the coders of the individual functions (you can add one yourself as part 
of your warning).  I would say that the warning types should be added as 
they are found, and I don't think that they are standard.

Bill

--

-- 
Warning label at MIT's Junior Lab:
"WARNING: Do not look into laser with remaining eye"
   -- /usr/bin/fortune
Permalink | Reply | 17 comments |
headers
Søren Hauberg | 6 Dec 2005 23:28

Re: message ids for warnings and errors

tir, 06 12 2005 kl. 17:21 -0500, skrev Bill Denney:
> On Tue, 6 Dec 2005, Stefan van der Walt wrote:
> 
> > I wonder how consistent they are in the usage of these strings. The
> > best description I could find is at
> >
> > http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_prog/ch12_er7.html#prog_message_identifiers
> >
> > and it doesn't refer to a list of pre-defined identifiers.
> >
> > My vote goes for the lookup-table, rather than the string translation.
> 
> That looks like what I see as well.  These identifiers are written in by 
> the coders of the individual functions (you can add one yourself as part 
> of your warning).  I would say that the warning types should be added as 
> they are found, and I don't think that they are standard.
Some can be found by typing

warning query all

in the matlab prompt. Although this will only give you the warnings with
preset defaults.

/Søren 

> Bill
> 
> -- 
> Warning label at MIT's Junior Lab:
> "WARNING: Do not look into laser with remaining eye"
(Continue reading)

Permalink | Reply | 4 comments |
headers
John W. Eaton | 6 Dec 2005 23:37
Picon

Re: message ids for warnings and errors

On  6-Dec-2005, Søren Hauberg wrote:

| Some can be found by typing
| 
| warning query all
| 
| in the matlab prompt. Although this will only give you the warnings with
| preset defaults.

Try

  warning query all
  warning on all
  warning query all

Do you get different lists for the first and second query?

jwe
Permalink | Reply | 3 comments |
headers
John W. Eaton | 6 Dec 2005 23:39
Picon

Re: message ids for warnings and errors

On  6-Dec-2005, Bill Denney wrote:

| On Tue, 6 Dec 2005, Stefan van der Walt wrote:
| 
| > I wonder how consistent they are in the usage of these strings. The
| > best description I could find is at
| >
| > http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_prog/ch12_er7.html#prog_message_identifiers
| >
| > and it doesn't refer to a list of pre-defined identifiers.
| >
| > My vote goes for the lookup-table, rather than the string translation.
| 
| That looks like what I see as well.  These identifiers are written in by 
| the coders of the individual functions (you can add one yourself as part 
| of your warning).  I would say that the warning types should be added as 
| they are found, and I don't think that they are standard.

Yes, I'm not proposing that we implement them all at once, even if we
could find a list.  I was more interested in seeing whether there was
a uniform naming scheme and about how many there are.

I suppose the first thing to do is eliminate all the warn_* built-in
variables in favor of controlling warnings with warning [on|off] ID.

Thanks,

jwe
(Continue reading)

Permalink | Reply | 11 comments |
headers
Søren Hauberg | 6 Dec 2005 23:42

Re: message ids for warnings and errors

tir, 06 12 2005 kl. 17:37 -0500, skrev John W. Eaton:
> Try
> 
>   warning query all
>   warning on all
>   warning query all
> 
> Do you get different lists for the first and second query?
Matlab is to "smart":

>> warning query all
The default warning state is 'on'. Warnings not set to the default are

  State  Warning Identifier

    off  MATLAB:UsingLongNames
    off  MATLAB:intConvertNaN
    off  MATLAB:intConvertNonIntVal
    off  MATLAB:intConvertOverflow
    off  MATLAB:intMathOverflow
    off  MATLAB:max:mixedIntegerScalarDoubleInputs
    off  MATLAB:max:mixedSingleDoubleInputs
    off  MATLAB:min:mixedIntegerScalarDoubleInputs
    off  MATLAB:min:mixedSingleDoubleInputs
    off  MATLAB:mir_warning_unrecognized_pragma
    off  MATLAB:nonScalarConditional

>> warning on all
>> warning query all
The default warning state is 'on'. Warnings not set to the default are
(Continue reading)

Permalink | Reply | 1 comment |
headers
Quentin Spencer | 6 Dec 2005 23:50
Picon

Re: message ids for warnings and errors

John W. Eaton wrote:

>On  6-Dec-2005, Søren Hauberg wrote:
>
>| Some can be found by typing
>| 
>| warning query all
>| 
>| in the matlab prompt. Although this will only give you the warnings with
>| preset defaults.
>
>Try
>
>  warning query all
>  warning on all
>  warning query all
>
>Do you get different lists for the first and second query?
>  
>

Yes, but unfortunately not what I think you were hoping for:

 >> warning query all
The default warning state is 'on'. Warnings not set to the default are

  State  Warning Identifier

    off  MATLAB:UsingLongNames
    off  MATLAB:intConvertNaN
(Continue reading)

Permalink | Reply | 0 comments |

Gmane