🚀 go-pugleaf

Oops.
My previous message was in error in a detail which looks like it might
be the whole crux of the problem.

In article <1991Oct28.215929.4475@viewlogic.com>, I write
> 
> I commonly create artificial argc/argv arg lists, which act like main's
> argc/argv.  This is so the readers of the implementation of individual
> commands of a program can understand what's happening.
> 
> Anyhow, code like this looks something like
> ----------------
> static int
> go_figure(int argc, char *argv[]);
> ....

It turns out that my problem only occurs when this declaration is
----------------
static int
go_figure(int argc, const char *argv[]);
----------------

Then I get the warning as stated before on the line
>...
>     did_it_work = go_figure(argc, argv);
>

about incompatible pointer types.
> lala.c: In function a_function:
> lala.c:13: warning: argument passing between incompatible pointer types

Removing const makes the pointers compatible -- implying that
const char *[] is incompatible with char **.   This seems wrong,
since one should be able to call a function with a parameter
having const pointers and arrays -- that just restricts the called
function from changing the array address or what it points to.

Is this a bug or a "feature"?

Again, apologies about the former omission.
-- 
Bob Davis (bobdavis@viewlogic.com)
hmmmming along