C
cverbiest
Guest
On linux pro -basekey ini -s 500 shows following error 'The -s parameter requires a numeric argument. (11996)' I spent the better part of an hour debugging and trying to figure out why 500 wasn't numeric. The error should have been "-basekey is not supported on this platform" or "unknown option -basekey" pro -basWhateverImistypehere ini nonnumerric 500 t.txt 500 -p echoparam.p should show "unknown option -basWhateverImistypehere" but also shows "The -s parameter requires a numeric argument. (11996)" This kind of unclear errors will occur each time Progress identifies part of a parameter as valid. pro -basekey ini 500 500 t.txt 500 is also pro -b -a ini -s 500 -e 500 -k t.txt -e 500 I understand this kind of parsing is kept in place because it used to work in the past. But I think the error reporting should show the entire parameter it cannot parse and not a single option that also happens to exist on its own. Personally I don't mind if the concatenating of parameters is dropped altogether as , I consider "-LnB 10000 25 1000" instead of "-L 10000 -n 25 -B 1000" as very unclear.
Continue reading...
Continue reading...