CODEWITHSUNDEEP
cgcc
ambika
ambika

Reputation: 1683

C .pc file warning

I have a RefTables.pc file.

When I execute the make command, I get this warning:

RefTables.c:109: warning: type defaults to `int' in declaration of `sqlcxt'
RefTables.c:111: warning: type defaults to `int' in declaration of `sqlcx2t'
RefTables.c:113: warning: type defaults to `int' in declaration of `sqlbuft'
RefTables.c:114: warning: type defaults to `int' in declaration of `sqlgs2t'
RefTables.c:115: warning: type defaults to `int' in declaration of `sqlorat'

How can I remove it?

I am using linux & gcc compiler.

Upvotes: 2

Views: 4186

Answers (3)

Simon Nickerson
Simon Nickerson

Reputation: 43157

It's been a while since I used Pro*C, but I think you can add a command line option to the proc command line

code=ANSI_C

which will give prototypes for the functions named.

Upvotes: 4

John Bode
John Bode

Reputation: 123558

In the future, provide a code snippet along with the warnings so that we have some context to work from. Otherwise we can only guess at what the real problem is.

I'm assuming that sqlcxt, sqlcx2t, etc., are functions. Without seeing the source code, it sounds like you don't have a declaration for those functions in scope before using them.

Here's a short example of what I mean:

int main(void)
{
  foo();
  return 0;
}

void foo(void)
{
  // do something interesting
}

When the compiler sees the call to foo in main, it doesn't have a declaration in scope, so it assumes that foo returns int, not void, and will return a warning similar to what you got above.

If your functions are defined in the same file as they are called, there are two ways around this problem. My preferred way is to define the function before it is used:

void foo(void)
{
  // do something interesting
}

int main(void)
{
  foo();
  return 0;
}

Another way is to have a declaration of the function in scope before calling it:

void foo(void);

int main(void)
{
  foo();
  return 0;
}

void foo(void)
{
  // do something interesting
}

It sounds like these functions are part of a database API; if so, there should be a header file that contains declarations for those functions, and that header should be included in your source file:

/** foo.c */
#include "foo.h"

void foo(void) 
{
  // do something interesting
}
/** end foo.c */

/** foo.h */
#ifndef FOO_H
#define FOO_H

void foo(void);

#endif
/** end foo.h */

/** main.c */
#include "foo.h"

int main(void)
{
  foo();
  return 0;
}
/** end main.c */

Hope that helps.

Upvotes: 0

Didier Trosset
Didier Trosset

Reputation: 37467

You can remove the warning by specifying the type of the 5 offending declarations. Actually, they must be declared with no type at all, which defaults to int in C (but generates a warning).

Edit: I found on Google this declaration.

extern sqlcxt (/*_ void **, unsigned int *, struct sqlexd *, struct sqlcxp * _*/);

The function has no return type. It should have one. Write it as follows.

extern int sqlcxt (/*_ void **, unsigned int *, struct sqlexd *, struct sqlcxp * _*/);

Or you can manually state in the compiler command line to ignore these warnings. They won't be displayed anymore.

Upvotes: 1

Related Questions