Why does cups pass the device URL to backends as ARGV[0]?

[Hadmut Danisch]

Hi,

just a question. I sometimes need to debug problems with printing with cups.

And in most cases I run against the same problem again and again, i.e. that the backend drivers can't be used from the command line for debugging, because the device URL is to be passed as ARGV[0] (where usually the path of the program resides) instead of ARGV[1] (where the parameters usually starts).

This looks like a silly, if not one of the worst ever, design decisions.

Is there any good reason at all for doing so?

regards
Hadmut