Re: Why segfault and no NULL match in for loop?
- From: CBFalconer <cbfalconer@xxxxxxxxx>
- Date: Thu, 03 May 2007 10:14:16 -0400
jaysome wrote:
CBFalconer <cbfalconer@xxxxxxxxx> wrote:.... snip ...
A .h file is NOT a place for headers, it is a place to define the
data you want to export from a .c file.
Saying a ".h file is NOT a place for headers" is like saying a
"house is not a place for a home". I think you meant "objects"
instead of "headers".
No, I wrote what I meant. I mean you don't just collect all the
headers and export them to a .h file. You only export those that
are needed elsewhere.
--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>
<http://www.aaxnet.com/editor/edit043.html>
<http://kadaitcha.cx/vista/dogsbreakfast/index.html>
cbfalconer at maineline dot net
--
Posted via a free Usenet account from http://www.teranews.com
.
- Follow-Ups:
- Re: Why segfault and no NULL match in for loop?
- From: Keith Thompson
- Re: Why segfault and no NULL match in for loop?
- References:
- Why segfault and no NULL match in for loop?
- From: somebody
- Re: Why segfault and no NULL match in for loop?
- From: CBFalconer
- Re: Why segfault and no NULL match in for loop?
- From: jaysome
- Why segfault and no NULL match in for loop?
- Prev by Date: Re: error
- Next by Date: Re: Skipping parameters in a printf()
- 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
|