|
From: <kus...@sp...> - 2022-12-26 12:37:53
|
> On 26. Dec 2022, at 12.32, Rob Pearce <lis...@fl...> wrote: > > On 26/12/2022 12:06, kus...@sp... wrote: >> Maybe improve the ".cod range error" with something like: >> >> "cod range error. Too many code sections?" >> >> or something, lest some lonely future user fails to find the >> answer from the lis archives? > > Yes, but if I'm clarifying error messages then I'd want to produce the correct reason, not a potentially misleading one. The current test traps several possible illegal entries as well as the valid-but-unsupported one. It will need more careful error checking (and consultation of the COD format definition) to do that. That is the prudent approach and if you are up to it, then that is great. My approach was just to add the '?' at the end to indicate that the error message might not be accurate and still hint a possible cause. cheers Kusti |