Re: Automatically generate variables
- From: rlb@xxxxxxxxxxxxxxxxxxxxxx (Richard Bos)
- Date: Mon, 26 Feb 2007 09:13:33 GMT
Keith Thompson <kst-u@xxxxxxx> wrote:
Beej Jorgensen <beej@xxxxxxx> writes:
7.1.2 paragraph 3:
If a file with the same name as one of the above < and > delimited
sequences, not provided as part of the implementation, is placed in
any of the standard places that are searched for included source
files, the behavior is undefined.
Interesting. That says that if I place a "stdlib.h" file in one of
the places searched for a
#include "stdlib.h"
directive but *not* for a
#include <stdlib.h>
directive, then the behavior is undefined. I suspect that wasn't the
intent.
I suspect that the intent was that if you place a new stdlib.h in one of
the <> places, you're effectively creating a new C _implementation_, not
a new C source program. If you place a stdlib.h in one of the "" places,
you're doing the latter, trying to create a different program in C, but
one that has undefined behaviour.
Richard
.
- Follow-Ups:
- Re: Automatically generate variables
- From: *** T. Winter
- Re: Automatically generate variables
- From: Keith Thompson
- Re: Automatically generate variables
- References:
- Re: Automatically generate variables
- From: Mark McIntyre
- Re: Automatically generate variables
- From: Mark McIntyre
- Re: Automatically generate variables
- From: Yevgen Muntyan
- Re: Automatically generate variables
- From: Mark McIntyre
- Re: Automatically generate variables
- From: Beej Jorgensen
- Re: Automatically generate variables
- From: Keith Thompson
- Re: Automatically generate variables
- Prev by Date: Re: why learn C?
- Next by Date: Re: Structure Pointer
- Previous by thread: Re: #include behavior
- Next by thread: Re: Automatically generate variables
- Index(es):