Passing pointer array to function

[Tatu Portin]

I have a struct:

typedef struct {
char **user_comments ;
int *comment_wds;
int comments;
char *vendor;
} vorbis_comment;
void func (char **table)
{
return;
}

int main (void)
{
vorbis_comment vc;
/* This part GCC doesn't like */

func (vc.user_commen ts);

return 0;
}

GCC (3.1) would say that

warning: passing arg 1 of 'func' from incompatible pointer type

But still my code in 'func' (not posted, above is an example) works correctly,
utilizing whole '**table'.

Now what I want to ask is that which is the legal way to make a call of this
kind? Or is it just a bug or "feature" of GCC?
I am compiling with a commandline:

gcc -Wall -pedantic -ansi -mcpu=athlon -ffast-math -O2

[Mike Wahler]

"Tatu Portin" <ax****@mbnet.f i> wrote in message
news:TE******** *******@read3.i net.fi...

I have a struct:

typedef struct {
char **user_comments ;
int *comment_wds;
int comments;
char *vendor;
} vorbis_comment;
void func (char **table)
{
return;
}

int main (void)
{
vorbis_comment vc;
/* This part GCC doesn't like */

func (vc.user_commen ts);

return 0;
}

GCC (3.1) would say that

warning: passing arg 1 of 'func' from incompatible pointer type
But still my code in 'func' (not posted,

Why not?
above is an example) works correctly,
utilizing whole '**table'.

Now what I want to ask is that which is the legal way to make a call of this kind? Or is it just a bug or "feature" of GCC?

We cannot tell you the correct form for calling a function whose
definition (at least declaration) that we cannot see. What is
the signature of 'func()'? Remember that an array is not a pointer,
and a pointer is not an array.

-Mike

[E. Robert Tisdale]

Tatu Portin wrote:

I have a struct:

cat main.c typedef struct {
char** user_comments;
int* comment_wds;
int comments;
char* vendor;
} vorbis_comment;
void func(char** table) {
return;
}

int main(int argc, char* argv[]) {
vorbis_comment vc;

/* GCC doesn't like this part. */

func(vc.user_co mments);

return 0;
}
gcc -Wall -ansi -pedantic -ffast-math -O2 -o main main.c
gcc --version gcc (GCC) 3.4.1

GCC (3.1) would say that

>warning: passing arg 1 of 'func' from incompatible pointer type

It seems to compile just fine for me.

[Joe Wright]

Tatu Portin wrote:

I have a struct:

typedef struct {
char **user_comments ;
int *comment_wds;
int comments;
char *vendor;
} vorbis_comment;
void func (char **table)
{
return;
}

int main (void)
{
vorbis_comment vc;
/* This part GCC doesn't like */

func (vc.user_commen ts);

return 0;
}

GCC (3.1) would say that

>warning: passing arg 1 of 'func' from incompatible pointer type

But still my code in 'func' (not posted, above is an example) works
correctly, utilizing whole '**table'.

Now what I want to ask is that which is the legal way to make a call of
this kind? Or is it just a bug or "feature" of GCC?
I am compiling with a commandline:

gcc -Wall -pedantic -ansi -mcpu=athlon -ffast-math -O2

Your code exactly as written here, pasted to tatu.c and compiled with ..

gcc -Wall -pedantic -ansi -mcpu=athlon -ffast-math -O2 tatu.c

... compiles here without error.

C:\work\c\clc>g cc --version
gcc.exe (GCC) 3.1
Copyright (C) 2002 Free Software Foundation, Inc.

--
Joe Wright mailto:jo****** **@comcast.net
"Everything should be made as simple as possible, but not simpler."
--- Albert Einstein ---

[Tatu Portin]

Ok. First post was wrong. (I thought that simplifying would do the same. It
didn't.)

Here we are:
42:int fprint_comments _formatted
43: ( FILE *tg
44: , const vorbis_comment *vc)
45:{
46: register int i;

....

69: if (flag) {

70: entry = has_str (s_album, vc->user_comment s, vc->comments);

71: val = strpbrk (vc->user_comment s[entry], "=");
72: val++;
73: fprintf (tg, "%s\n", val);
74:
75: flag = 0;
76: }

....

90: return 0;
91:}

gcc -Wall -pedantic -ansi -mcpu=athlon -ffast-math -O2 cdmaker.c cdmaker_1.o -o
cdmaker.exe
cdmaker.c In function 'fprint_comment s_formatted':
cdmaker.c:70 warning: passing arg 2 of 'has_str' from incompatible pointer type
Function prototypes:
int fprint_comments _formatted
( FILE *tg
, const vorbis_comment *vc);

int has_str
( const char *str
, const char **table
, int ent); /* Number of entries in '**table' */
Struct definition:
typedef struct {
char **user_comments ;
int *comment_wds;
int comments;
char *vendor;
} vorbis_comment;

[Raymond Martineau]

On Sun, 12 Dec 2004 03:43:16 GMT, Tatu Portin <ax****@mbnet.f i> wrote:

Ok. First post was wrong. (I thought that simplifying would do the same. It
didn't.)

Here we are:
42:int fprint_comments _formatted
43: ( FILE *tg
44: , const vorbis_comment *vc)
45:{
46: register int i;

...

69: if (flag) {

70: entry = has_str (s_album, vc->user_comment s, vc->comments);

You might get a bit more help compiling it with a C++ compiler:

E:\temp>gpp -Wall a.cpp
a.cpp: In function `int main()':
a.cpp:27: error: invalid conversion from `char**' to `const char**'
a.cpp:27: error: initializing argument 2 of `int has_str(const char*,
const char**, int)'

It's valid in C, but GCC decides it's worth raising a warning about
converting 'char**' to 'const char**'. You can get rid of the warning by
doing a type cast, but there may be better methods of dealing with it.

[Chris Torek]

In article <o7***********@ read3.inet.fi> Tatu Portin <ax****@mbnet.f i> wrote:

Ok. First post was wrong. (I thought that simplifying would do the same. It
didn't.)

Always test the simplified-for-post version. :-)

Without quoting a lot, your problem is the "const" qualifier,
which does not work right in C. Stop using it, and the problem
will go away (this is not necessarily the best solution, but is
certainly the easiest to describe).

See also the comp.lang.c FAQ, question 11.10.
--
In-Real-Life: Chris Torek, Wind River Systems
Salt Lake City, UT, USA (40°39.22'N, 111°50.29'W) [phone]
email: forget about it http://web.torek.net/torek/index.html
Reading email is like searching for food in the garbage, thanks to spammers.

[CBFalconer]

Mike Wahler wrote:

"Tatu Portin" <ax****@mbnet.f i> wrote in message
news:TE******** *******@read3.i net.fi...

I have a struct:

typedef struct {
char **user_comments ;
int *comment_wds;
int comments;
char *vendor;
} vorbis_comment;
void func (char **table)
{
return;
}

int main (void)
{
vorbis_comment vc;
/* This part GCC doesn't like */

func (vc.user_commen ts);

return 0;
}

GCC (3.1) would say that

warning: passing arg 1 of 'func' from incompatible pointer type

But still my code in 'func' (not posted,

Why not?

above is an example) works correctly,
utilizing whole '**table'.

Now what I want to ask is that which is the legal way to make a call of

this

kind? Or is it just a bug or "feature" of GCC?

We cannot tell you the correct form for calling a function whose
definition (at least declaration) that we cannot see. What is
the signature of 'func()'? Remember that an array is not a pointer,
and a pointer is not an array.

Er - he gave the full definition of func. What he didn't do was
initialize vc, which should not cause a compile error.

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!

[Mike Wahler]

"CBFalconer " <cb********@yah oo.com> wrote in message
news:41******** *******@yahoo.c om...

Mike Wahler wrote:

We cannot tell you the correct form for calling a function whose
definition (at least declaration) that we cannot see. What is
the signature of 'func()'? Remember that an array is not a pointer,
and a pointer is not an array.

Er - he gave the full definition of func. What he didn't do was
initialize vc, which should not cause a compile error.

Um, yes, it seems that it's me who can't see today. :-)

-Mike

[Chris Torek]

In article <8e************ *************** *****@4ax.com>
Raymond Martineau <bk***@ncf.ca > wrote:

You might get a bit more help compiling it with a C++ compiler:

E:\temp>gpp -Wall a.cpp
a.cpp: In function `int main()':
a.cpp:27: error: invalid conversion from `char**' to `const char**'
a.cpp:27: error: initializing argument 2 of `int has_str(const char*,
const char**, int)'

It's valid in C ...
Actually, it is *not* valid in C either.
but GCC decides it's worth raising a warning about converting
'char**' to 'const char**'.
GCC simply chooses to complain-and-keep-going in this case, rather
than complain-and-stop-compiling. GCC calls the former a "warning"
and the latter an "error", but the C standard says only that the
conversion is incorrect and must elicit a "diagnostic ".

The set of things-that-cause-stopping is different for GCC's C
compiler than for GCC's C++ compiler, partly because they are
maintained by different people, partly because C compilers have
traditionally accepted all kinds of invalid source and generated
machine code anyway (which promptly core-dumps, in many cases),
and of course partly because the languages are different (although
in this case, the semantics actually match up, for once).
You can get rid of the warning by doing a type cast, but there may
be better methods of dealing with it.

In C++, if you made has_str() take a "const char *const *" parameter,
the problem would go away, but it would remain a problem in C.
--
In-Real-Life: Chris Torek, Wind River Systems
Salt Lake City, UT, USA (40°39.22'N, 111°50.29'W) [phone]
email: forget about it http://web.torek.net/torek/index.html
Reading email is like searching for food in the garbage, thanks to spammers.