FILE argument to a function

[fermineutron]

I seem to run into a funny problem,

basially i need to call a funcyon ReadGeometry and the only parameter
that i need to pass to that function is a file pointer, so my funtion
prototype looks like this:

void ReadGeometry(FI LE *ff1)

Now, my compiler gives a compile time error stating that "FILE can not
start a parameter declaration"

Probably the easiest way to fix this would be to just pass a constant
char as the first argument, but that just seems wrong to pass to a
function a parameter that i dont need.

Any ideas?

Also is it just my copiler specific problem or is it in C standard that
argument list can not start with FILE type?

[Eric Sosman]

fermineutron wrote:

I seem to run into a funny problem,

basially i need to call a funcyon ReadGeometry and the only parameter
that i need to pass to that function is a file pointer, so my funtion
prototype looks like this:

void ReadGeometry(FI LE *ff1)

Now, my compiler gives a compile time error stating that "FILE can not
start a parameter declaration"

You probably forgot to #include <stdio.hbefor e
declaring the function.

--
Eric Sosman
es*****@acm-dot-org.invalid

[Jordan Abel]

2006-11-08 <11************ **********@b28g 2000cwb.googleg roups.com>,
fermineutron wrote:

I seem to run into a funny problem,

basially i need to call a funcyon ReadGeometry and the only parameter
that i need to pass to that function is a file pointer, so my funtion
prototype looks like this:

void ReadGeometry(FI LE *ff1)

Now, my compiler gives a compile time error stating that "FILE can not
start a parameter declaration"

Did you include stdio.h?

>
Probably the easiest way to fix this would be to just pass a constant
char as the first argument, but that just seems wrong to pass to a
function a parameter that i dont need.

It wouldn't help. a "parameter declaration" is the declaration of
a single argument - i.e. int x(int y, int z) contains two parameter
declarations.

Any ideas?

Also is it just my copiler specific problem or is it in C standard that
argument list can not start with FILE type?

If you included stdio.h, and you get that error, your compiler is wrong.

[fermineutron]

Eric Sosman wrote:

You probably forgot to #include <stdio.hbefor e
declaring the function.

I did include it. I have a main function in main.c, i have readGeometry
function in ReadGeometry.c and i have stdio and other includes in NTC.h
file. All 3 files are a part of a project and NTC.h is included in
main.c
ReadGeometry is prototyped in the NTC.h file.

But it generates the compile error i described above. If i do not
include stdio.h a totaly different error is geerated.

Another question about header files,
I think the following is correct, but i'd appreciate is someone
veryfied it:
if i have 2 or more C files and i have a header file which contains all
of the globals and includes, i have to separately #include "MyHeader.h "
into each of my C files. Is this correct?

[Keith Thompson]

"fermineutr on" <fr**********@y ahoo.comwrites:

Eric Sosman wrote:

> You probably forgot to #include <stdio.hbefor e
declaring the function.

I did include it. I have a main function in main.c, i have readGeometry
function in ReadGeometry.c and i have stdio and other includes in NTC.h
file. All 3 files are a part of a project and NTC.h is included in
main.c
ReadGeometry is prototyped in the NTC.h file.

But it generates the compile error i described above. If i do not
include stdio.h a totaly different error is geerated.

Show us some actual code that exhibits the errors.

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[fermineutron]

I tried compiling using lcc-win32, it worked.

I guess the other compiler i used is too old, Borland C++ 5.02 is the
one which errors.

Ill just use lcc from now on for this project.

Thanks every body.

Sorry for such a meaningless post.

[Keith Thompson]

"fermineutr on" <fr**********@y ahoo.comwrites:

I tried compiling using lcc-win32, it worked.

I guess the other compiler i used is too old, Borland C++ 5.02 is the
one which errors.

Ill just use lcc from now on for this project.

Thanks every body.

Sorry for such a meaningless post.

For the Nth time, for some very large value of N, *please* show some
context when you post a followup.

Here's what you wrote upthread:

| void ReadGeometry(FI LE *ff1)
|
| Now, my compiler gives a compile time error stating that "FILE can not
| start a parameter declaration"

and you later said that you did have the required "#include
<stdio.h>". I don't believe that Borland C++ 5.02 (being used, I
presume, as a C compiler) would be so buggy as to reject such a simple
declaration. The only possibility I can think of is that it's so old
that it doesn't support prototypes.

Try compiling the following with your Borland compiler:

void func(int x);

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Richard Heathfield]

fermineutron said:

>
I tried compiling using lcc-win32, it worked.

If it didn't work with a C compiler, but did work with lcc-win32, then your
code is not C code but lcc-win32 code, in which case I suggest you ask
future questions about your code in an lcc-win32 newsgroup rather than
here.

I guess the other compiler i used is too old, Borland C++ 5.02 is the
one which errors.

Borland's C compiler - and yes, that specific version, works just fine on
correct parameter declaration, and rightly rejects those that are not
correct in form.

Ill just use lcc from now on for this project.

When even lcc rejects your code, which compiler will you then move to?
Wouldn't it be easier to learn C than to keep moving from compiler to
compiler as each of them in turn discovers gaps in your knowledge?

Thanks every body.

Sorry for such a meaningless post.

That's okay - we're getting used to it.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: normal service will be restored as soon as possible. Please do not
adjust your email clients.

[Richard Heathfield]

Keith Thompson said:

<snip>

Here's what you wrote upthread:

| void ReadGeometry(FI LE *ff1)
|
| Now, my compiler gives a compile time error stating that "FILE can not
| start a parameter declaration"

and you later said that you did have the required "#include
<stdio.h>". I don't believe that Borland C++ 5.02 (being used, I
presume, as a C compiler) would be so buggy as to reject such a simple
declaration. The only possibility I can think of is that it's so old
that it doesn't support prototypes.

It is not, it does not, it is not, and it does, in that order. In other
words, the problem here is not with the compiler, but with the source code
being supplied to it.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: normal service will be restored as soon as possible. Please do not
adjust your email clients.

[Serve Laurijssen]

"fermineutr on" <fr**********@y ahoo.comwrote in message
news:11******** **************@ b28g2000cwb.goo glegroups.com.. .

void ReadGeometry(FI LE *ff1)
Now, my compiler gives a compile time error stating that "FILE can not
start a parameter declaration"

only thing I can think of without seeing the real code is you forgot to put
a semicolon after the prototype declaration.
Although that doesnt compile in lccwin32 either and you said it does in that
compiler

Probably the easiest way to fix this would be to just pass a constant
char as the first argument, but that just seems wrong to pass to a
function a parameter that i dont need.

Any ideas?

Also is it just my copiler specific problem or is it in C standard that
argument list can not start with FILE type?