>OK, that makes sense to me. How about if we put a test for MRAT into
>GREAT so that it triggers a more specific error. E.g. have it throw
>HEY-NO-MRATS-PLEASE or merror("GREAT: dunno about MRAT") or something.
Something like that would be OK. I think some calls to specrepcheck in nset need to be
$ratdisrep (or ratdisrep or $totalratdisrep, not sure). For 5.30, I think we can get this
figured out, and maybe an error checking (very modest time required) great might
help locate more bugs.
--bw