Error message may confuse users

[DarkElvenAngel]

I may have found a bug, when you have a short argument that takes a value and you don't put a space between it and the value and you then have another argument that needs to take a value the error generated isn't correct.

$./a.out -l6
error: missing argument for 'l' in -l6
$./a.out -Fl6 --long 10
error: cannot parse '--long' as an integer

I see what is happening the parser is trying to convert '--long' to an int and that's not working. Is there a way to parse the value in this way or would it be possible to generate the error missing argument message rather that the cannot parse message?

I'm trying to replace argp and this project is spot on for my needs

[DarkElvenAngel]

I found a work around

args/src/args.c

Lines 1235 to 1237 in ee4a67b

	if (strlen(arg) > 1) {
	exit_with_error("missing argument for '%c' in -%s", arg[i], arg);
	}

I replaced this with the following code

        if (strlen(arg) > 1) {
            //exit_with_error("missing value for '%c'", arg[i], arg);
            if (!option_try_set(option, (char*)(arg + i + 1))) {
                ap_set_memory_error_flag(parser);
            }
            break;
        }

This will allow short options to accept values with out a space or equals just like argp does. thus a -l6, -l 6 or -l=6 are all treated the same, and I get a proper missing value error. I won't open a pull request for this as I don't believe this is how you intended short arguments to get their values, it's more a hack to be compatible what I used before.

Thank you again for this wonderful project!