ARGF must be called just once for each option that takes an argument.
that means you cannot get the same argument (parameter value) twice,
so you'd better save it if you need it.
According to arg(2), that's not a good idea.
ARGF must be called just once for each option that takes an
argument.
Who are you going to believe? Me or that lying man page?
See if your code works.
I'm not your code monkey. You mentioned that you
didn't know how to do something; I
Hello.
My next experiment in learning libraries, as well as my next project,
is a reimplementation of the first and second edition raster graphics
manipulation tools. These use libmemdraw, which provides Memimage.
Since I only have a working first edition manual, the program I will
The first edition specified the arguments to -o as two values - this
cannot be done
due to idiosyncrasies with args(2).
case 'o':
arg1 = EARGF(usage());
arg2 = EARGF(usage());
break;
russ
On Jun 11, 2008, at 11:46 PM, Russ Cox wrote:
The first edition specified the arguments to -o as two values -
this cannot be done
due to idiosyncrasies with args(2).
case 'o':
arg1 = EARGF(usage());
arg2 = EARGF(usage());
break;
russ
According to