Re: Why segfault and no NULL match in for loop?
- From: Keith Thompson <kst-u@xxxxxxx>
- Date: Wed, 02 May 2007 21:02:37 -0700
CBFalconer <cbfalconer@xxxxxxxxx> writes:
[...]
NEVER define an actual object in a .h file. Doing so will cause it
to be multiply defined, and result in link or run time errors. Add
the word "extrn" to the definition, and delete the initialization.
Put the above structure in ONLY one of the files in which you
#include "search.h".
It's "extern", not "extrn".
--
Keith Thompson (The_Other_Keith) kst-u@xxxxxxx <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."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
.
- References:
- Why segfault and no NULL match in for loop?
- From: somebody
- Re: Why segfault and no NULL match in for loop?
- From: CBFalconer
- Why segfault and no NULL match in for loop?
- Prev by Date: Re: How to pass various structures to function?
- Next by Date: Re: How to pass various structures to function?
- Previous by thread: Re: Why segfault and no NULL match in for loop?
- Next by thread: Re: Why segfault and no NULL match in for loop?
- Index(es):
Relevant Pages
|