Re: reported a iconv improvement and now feel bad

[Dan Jacobson]

>> iconv: conversion from `big5' to `gb2132' not supported
>> 
>> All I did was suggest that maybe iconv could tell the user which one
>> of the args caused the problem, since I bet it knows which.

P> Your suggestion is quite reasonable, but I suspect that your bet isn't
P> quite correct.  (The best way to settle the bet is to write the patch.  :-)

how about it reporting what argument it ran into trouble?  Certainly
it uses them one by one?

I mean, imagine if I have a command
$ xyz -a 435g -b awedq45f -c we43gvv -d 4ghywe -e qw4wgfa4 -g qw3tgq4
would you like:
xyz: -a 435g -b awedq45f -c we43gvv -d 4ghywe -e qw4wgfa4 -g qw3tgq4: wrong
or
xyz: ran into problems processing argument to -e
or:
xyz: 4ghywe: not supported
The last first is not as helpful as the 2nd or 3rd.

P.S. I don't think you want me coding your programs, unless you want
comp.risks headlines.
-- 
http://jidanni.org/ Taiwan(04)25854780