ANSI C?

[Billy Bong]

Is the following program considered ANSI C?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Thanks
--
Billy

[Ian Collins]

Billy Bong wrote:

Is the following program considered ANSI C?

Why shouldn't it be?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Thanks

--
Ian Collins.

[Richard]

Billy Bong <bi**********@aol.comwrites:

Is the following program considered ANSI C?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Thanks

What does "Thanks" do?

[Malcolm McLean]

"Billy Bong" <bi**********@aol.comwrote in message

Is the following program considered ANSI C?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Depends what you mean.

The language itself will almost certainly be ANSI C89. However you are
including a non-standard header. bar() itself could be implemented in any
language that provides facilities for C-style linking, and may or may not be
portable.

--
Free games and programming goodies.
http://www.personal.leeds.ac.uk/~bgy1mm

[santosh]

Malcolm McLean wrote:

>
"Billy Bong" <bi**********@aol.comwrote in message

>Is the following program considered ANSI C?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Depends what you mean.

The language itself will almost certainly be ANSI C89.

IME most C compilers seem to have implemented changes upto at least C95
with portions of C99.

However you are
including a non-standard header. bar() itself could be implemented in
any language that provides facilities for C-style linking, and may or
may not be portable.

Perhaps the OP is asking whether the forward slash in the header name is
portable.

[Mark Bluemel]

santosh wrote:

Malcolm McLean wrote:

>"Billy Bong" <bi**********@aol.comwrote in message

....

Perhaps the OP is asking whether the forward slash in the header name is
portable.

It's hard to know what the OP is interested in.

My impression is that he is mainly interested in increasing the
noise-to-signal ratio here, so I killfiled him some time ago.

[Jack Klein]

On Tue, 05 Feb 2008 08:17:58 GMT, Billy Bong <bi**********@aol.com>
wrote in comp.lang.c:

Is the following program considered ANSI C?

The following is NOT a program.

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

Thanks

What it is, together with the contents of "foo/foo_bar.h", plus the
inclusion of anything else that might be indicated by preprocessor
inclusion directives in "foo/foo_bar.h", is a "translation unit".

Once it has been compiled and combined with other appropriate
separately compiled translation units, it might become a program.

The part of the program you have shown is conforming, and it might or
might not be strictly conforming. There is no such thing as an "ANSI
C" program.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.club.cc.cmu.edu/~ajo/docs/FAQ-acllc.html

[Keith Thompson]

santosh <sa*********@gmail.comwrites:
[...]

The '-ansi' option tells gcc to adhere to the "C90" Standard, i.e.,
ISO:9899:1990. It's also called as "C89" or "ANSI C". But strictly
speaking the last one (ANSI C) is invalid as "ANSI C" now refers to the
Standard ratified by ANSI currently, which is ISO:9899:1999.

[...]

That's true, but in practice the term "ANSI C" almost always refers to
the language defined by the ANSI C89 standard (or, equivalently, by
the ISO C90 standard). I think that most people who know and care
about the difference use the term "ISO C" or, more commonly, refer
specifically to C89/C90 or to C99.

--
Keith Thompson (The_Other_Keith) <ks***@mib.org>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Peter 'Shaggy' Haywood]

Groovy hepcat Billy Bong was jivin' in comp.lang.c on Tue, 5 Feb 2008
7:17 pm. It's a cool scene! Dig it.

Is the following program considered ANSI C?

#include <foo/foo_bar.h/* has prototype void bar(void) */
int main(void)
{
bar();
return 0;
}

No. If foo/foo_bar.h is a user defined header, you should be including
it like so:

#include "foo/foo_bar.h"

Otherwise it is a header provided by the implementation, and is
therefore an extention. (Well, it could be a third party header stored
where the implementation stores its headers, but in either case it
isn't a portable header.)
And function bar() is non-standard, and must be provided by the author
of the code or the implementation's run time library (or a third party
library).

--
Dig the sig!

----------- Peter 'Shaggy' Haywood ------------
Ain't I'm a dawg!!

[pete]

Billy Bong wrote:

In other words, no ANSI C compiler, let alone any ANSI C compiler that
builds on a UNIX-like system, is obliged to accept this? [1]

The GSL code is inundated with code like this:

#include <gsl/gsl_errno.h>

In other words,
my ANSI C compiler does not compile
#include <gsl/gsl_errno.h>,
and the standard allows my ANSI C compiler to be that way;
if your ANSI C compiler does compile
#include <gsl/gsl_errno.h>,
the standard allows that too.

--
pete

[Robert Latest]

Richard Heathfield wrote:

The fact that they are not topical here does not make them
evil, any more than the fact that cheesecake is not topical here makes
cheesecake evil.

That's a relief, considering that I spent a couple of hours last night
baking two big cheesecakes for my colleagues, as today is the last day
for me on this job.

It would've been a pain to have to tell them: Sorry, guys, no
cheesecake today (or ever). Yup, that's right. Dick Heathfield said so.
Look it up on Usenet.

robert