I was trying to compile a .c source file using bcc on my winxp system but
the only way this would work is if I put the stdio.h file in the same folder
as the source file, even though my include statement said this #include
<c:\myfiles\include> which I thought would solve the "can't find error" I
was getting for my printf statements etc. etc.

On Oct 18, 8:31 pm, "don" <d...@panix.com> wrote:
> I was trying to compile a .c source file using bcc on my winxp system but
> the only way this would work is if I put the stdio.h file in the same folder
> as the source file, even though my include statement said this #include
> <c:\myfiles\include> which I thought would solve the "can't find error" I
> was getting for my printf statements etc. etc.

If you want to include stdio.h you should just be able to write
#include <stdio.h>

If you want #include to find files other than the Standard headers
then read your compiler documentation to find out how it handles files
and paths. This is officially implementation-defined, ie, the
implementation is required to document it.

-thomas

On Oct 18, 8:31 pm, "don" <d...@panix.com> wrote:
> I was trying to compile a .c source file using bcc on my winxp system but
> the only way this would work is if I put the stdio.h file in the same folder
> as the source file, even though my include statement said this #include
> <c:\myfiles\include> which I thought would solve the "can't find error" I
> was getting for my printf statements etc. etc.

See section 10 of the C-FAQ.

Do you have a link for this C FAQ?

"user923005" <dcorbit@connx.com> wrote in message
news:1192774349.176536.17760@y27g2000pre.googlegro ups.com...
> On Oct 18, 8:31 pm, "don" <d...@panix.com> wrote:
>> I was trying to compile a .c source file using bcc on my winxp system
>> but
>> the only way this would work is if I put the stdio.h file in the same
>> folder
>> as the source file, even though my include statement said this #include
>> <c:\myfiles\include> which I thought would solve the "can't find error"
>> I
>> was getting for my printf statements etc. etc.
>
> See section 10 of the C-FAQ.
>

don wrote:

> Do you have a link for this C FAQ?

http://www.c-faq.com/

There used to be regular reminders posted to the group.
What happened to them?

don wrote:

Please don't top post.

>
> "user923005" <dcorbit@connx.com> wrote in message
> news:1192774349.176536.17760@y27g2000pre.googlegro ups.com...
>> On Oct 18, 8:31 pm, "don" <d...@panix.com> wrote:
>>> I was trying to compile a .c source file using bcc on my winxp system
>>> but
>>> the only way this would work is if I put the stdio.h file in the same
>>> folder
>>> as the source file, even though my include statement said this #include
>>> <c:\myfiles\include> which I thought would solve the "can't find error"
>>> I
>>> was getting for my printf statements etc. etc.
>> See section 10 of the C-FAQ.
>>
>
> Do you have a link for this C FAQ?

Have you looked? The first hit on a google of "c faq" looks good to me.

--
Ian Collins.

>>> See section 10 of the C-FAQ.
>>>
>>
>> Do you have a link for this C FAQ?
>
> Have you looked? The first hit on a google of "c faq" looks good to me.
>
> --
> Ian Collins.

There were so many hits that I wanted to narrow it down - the fastest way to
an answer is to ask the Right question.

"Peter Pichler" <usenet@pichler.co.uk> schrieb im Newsbeitrag
news:471924b6$1_2@mk-nntp-2.news.uk.tiscali.com...
> don wrote:
>
>> Do you have a link for this C FAQ?
>
> http://www.c-faq.com/
>
> There used to be regular reminders posted to the group.
> What happened to them?
They still happen about once a month (or fortnight?) and there was one
resently, earlyier this week or near the end of the week before

Bye, Jojo