id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
404	Consider expanding $? to hold the number of errors of each type	Ian Culverwell	Ian Culverwell	"ROPP8.0 beta reviewer Axel von Engeln (EUM) found:
{{{
The other issue I noted, we run ropp_fm_bg2ro_1d with some ""expert"" 
flags, that also cause a warning (e.g. range checking disabled). So 
for now I don't check for warning messages, and only print out 
messages with exit codes > 1. So I might miss something else (as I 
actually did, when I changed my IDL code, messed up the undulation, 
and then didn't catch the warning of ROPP until I really looked at 
it).
}}}

So the ''number'' of each type of error could be useful. We could store this as, for example, 

Z = 2^(no of warnings)^ * 3^(no of errors)^ * (-1)^(no of fatal errors)^.

Then (no of warnings) etc could be unravelled from Z.

There's a risk of overflow if Z is an integer, so perhaps we it could be real, with 

(no of warnings) = log2(|Z|) mod log2(3)

(no of errors) = log3(|Z|) mod log3(2) (ish)

and

(no of fatals) = sign(-Z).

Or something like that.
"	enhancement	new	minor	Whenever	ROPP (all)	7.1		error