comp.lang.c

• Thread Index

---

• udp help plz
  • From: killua
• Re: the mystery of <ctrl-d>
  • From: Kevin Handy
• Re: break statement in a for loop
  • From: christian.bau
• Re: Ahead of "main"?
  • From: Harald van Dijk
• Re: Ahead of "main"?
  • From: Flash Gordon
• Re: Smart conversion from a string to different type of numbers
  • From: Martin Ambuhl
• Re: break statement in a for loop
  • From: Bart van Ingen Schenau
• Re: PPL
  • From: user923005
• Re: multiplication
  • From: user923005
• Re: String Comparision
  • From: Default User
• Re: Smart conversion from a string to different type of numbers
  • From: Eric Sosman
• Re: Smart conversion from a string to different type of numbers
  • From: Charlton Wilbur
• Smart conversion from a string to different type of numbers
  • From: d . avitabile
• Re: String Comparision
  • From: Default User
• Re: gets() is dead
  • From: JT
• Re: gets() is dead
  • From: Chris Dollin
• Re: String Comparision
  • From: Richard Heathfield
• Re: enum variables and extern
  • From: Charlie
• Re: enum variables and extern
  • From: Charlie
• Re: enum variables and extern
  • From: Charlie
• Re: enum variables and extern
  • From: Chris Dollin
• Re: enum variables and extern
  • From: Eric Sosman
• Re: long integer multiplication
  • From: Chris Dollin
• Re: enum variables and extern
  • From: Martin Ambuhl
• Re: String Comparision
  • From: user34
• Re: enum variables and extern
  • From: Harald van Dijk
• Re: String Comparision
  • From: Fred Kleinschmidt
• enum variables and extern
  • From: Charlie
• Re: long integer multiplication
  • From: Chris Dollin
• Re: programming-challenges
  • From: Richard Heathfield
• Re: programming-challenges
  • From: Ajinkya
• Re: long integer multiplication
  • From: Richard Heathfield
• Re: programming-challenges
  • From: Ajinkya
• Re: the mystery of <ctrl-d>
  • From: Richard Tobin
• Re: long integer multiplication
  • From: Chris Dollin
• Re: multiplication
  • From: Barry Schwarz
• Re: long integer multiplication
  • From: Richard Heathfield
• Re: the mystery of <ctrl-d>
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: Ahead of "main"?
  • From: Richard Tobin
• multiplication
  • From: helPlease
• long integer multiplication
  • From: helPlease
• Re: Encrypting only with Kernel Functions
  • From: Barry Schwarz
• Re: Ahead of "main"?
  • From: Barry Schwarz
• Re: String Comparision
  • From: Barry Schwarz
• Re: String Comparision
  • From: Barry Schwarz
• Want to be a Microsoft Student Partner?
  • From: Bijoy Thangaraj
• Re: gets() is dead
  • From: Richard Tobin
• Re: gets() is dead
  • From: Hallvard B Furuseth
• Re: gets() is dead
  • From: Malcolm McLean
• Re: break statement in a for loop
  • From: Richard Tobin
• Re: the mystery of <ctrl-d>
  • From: Nick Keighley
• Re: gets() is dead
  • From: Richard Heathfield
• Re: String Comparision
  • From: Aditya
• Re: gets() is dead
  • From: Malcolm McLean
• Re: A one's complement sanity check, please
  • From: Harald van Dijk
• Re: break statement in a for loop
  • From: a . mil
• Re: gets() is dead
  • From: Richard Heathfield
• Re: Ahead of "main"?
  • From: Chris Dollin
• Re: Ahead of "main"?
  • From: Richard Heathfield
• Re: the mystery of <ctrl-d>
  • From: Richard Heathfield
• Re: Ahead of "main"?
  • From: mdh
• Re: two meanings of a cast
  • From: Wade Ward
• Re: comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Wade Ward
• Re: Ahead of "main"?
  • From: Keith Thompson
• Re: gets() is dead
  • From: Richard Tobin
• Re: break statement in a for loop
  • From: Keith Thompson
• Re: gets() is dead
  • From: Keith Thompson
• [OT] Re: Ahead of "main"?
  • From: Eric Sosman
• Re: gets() is dead
  • From: Dave Vandervies
• Re: gets() is dead
  • From: Charles Richmond
• Re: String Comparision
  • From: CBFalconer
• Re: Trap representations for unsigned integers
  • From: Peter Nilsson
• Re: break statement in a for loop
  • From: J. J. Farrell
• Re: PPL
  • From: Ian Collins
• Re: String Comparision
  • From: Default User
• Re: the mystery of <ctrl-d>
  • From: Al Balmer
• Encrypting only with Kernel Functions
  • From: SiTTox
• PPL
  • From: SiTTox
• Re: Ahead of "main"?
  • From: mdh
• Re: Ahead of "main"?
  • From: mdh
• Re: syntax error with pointer to pointer
  • From: Old Wolf
• Re: A one's complement sanity check, please
  • From: Old Wolf
• Re: Ahead of "main"?
  • From: Flash Gordon
• Re: break statement in a for loop
  • From: Old Wolf
• Re: Ahead of "main"?
  • From: J. J. Farrell
• Re: two meanings of a cast
  • From: Old Wolf
• Re: String Comparision
  • From: Flash Gordon
• Re: Ahead of "main"?
  • From: J. J. Farrell
• Re: break statement in a for loop
  • From: Flash Gordon
• Re: Ahead of "main"?
  • From: Richard Tobin
• Re: Ahead of "main"?
  • From: Flash Gordon
• Re: gets() is dead
  • From: CBFalconer
• Re: String Comparision
  • From: Old Wolf
• Re: String Comparision
  • From: Default User
• Re: Ahead of "main"?
  • From: Barry Schwarz
• Re: String Comparision
  • From: Barry Schwarz
• Re: Initialization of an array and symbolic names for index
  • From: Barry Schwarz
• Re: Ahead of "main"?
  • From: Eric Sosman
• Re: break statement in a for loop
  • From: a . mil
• Re: Ahead of "main"?
  • From: Stephen Sprunk
• Re: the mystery of <ctrl-d>
  • From: Keith Thompson
• Re: Ahead of "main"?
  • From: mdh
• Re: Ahead of "main"?
  • From: mdh
• Re: Ahead of "main"?
  • From: Eric Sosman
• Re: Ahead of "main"?
  • From: Malcolm McLean
• Re: break statement in a for loop
  • From: Keith Thompson
• Re: gets() is dead
  • From: Harald van Dijk
• Re: String Comparision
  • From: Keith Thompson
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Harald van Dijk
• Re: the mystery of <ctrl-d>
  • From: Bill Pursell
• Re: gets() is dead
  • From: Flash Gordon
• Re: the mystery of <ctrl-d>
  • From: Keith Thompson
• Re: gets() is dead
  • From: Flash Gordon
• Ahead of "main"?
  • From: mdh
• Re: gets() is dead
  • From: Harald van Dijk
• Re: comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Jason Wang
• Re: gets() is dead
  • From: Keith Thompson
• Re: gets() is dead
  • From: Keith Thompson
• Re: break statement in a for loop
  • From: Malcolm McLean
• Re: gets() is dead
  • From: Malcolm McLean
• Re: String Comparision
  • From: Martin Ambuhl
• Re: String Comparision
  • From: Flash Gordon
• Re: gets() is dead
  • From: Flash Gordon
• Re: break statement in a for loop
  • From: christian.bau
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Walter Roberson
• Re: String Comparision
  • From: Flash Gordon
• Re: String Comparision
  • From: user34
• Re: String Comparision
  • From: jg
• Re: gets() is dead
  • From: Malcolm McLean
• Re: String Comparision
  • From: Flash Gordon
• Re: String Comparision
  • From: Flash Gordon
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Ben Pfaff
• Re: String Comparision
  • From: user34
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Dave Vandervies
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Stephen Sprunk
• String Comparision
  • From: user34
• Re: programming-challenges
  • From: Kenny McCormack
• Re: break statement in a for loop
  • From: Richard Tobin
• Re: Initialization of an array and symbolic names for index
  • From: pozz
• Re: Common Routine To Call (Almost) Identical Functions
  • From: Barry Schwarz
• Re: random password generator
  • From: Barry Schwarz
• Re: the mystery of <ctrl-d>
  • From: Joe Wright
• Re: programming-challenges
  • From: Barry
• Re: Initialization of an array and symbolic names for index
  • From: Barry Schwarz
• Re: the mystery of <ctrl-d>
  • From: Bill Pursell
• Re: long integer multiplication
  • From: CBFalconer
• Re: gets() is dead
  • From: Chris Dollin
• Re: How to call A variable parameter function
  • From: Ben Bacarisse
• Re: break statement in a for loop
  • From: CBFalconer
• Re: gets() is dead
  • From: Chris Dollin
• Re: gets() is dead
  • From: Harald van Dijk
• Re: the mystery of <ctrl-d>
  • From: Flash Gordon
• Re: gets() is dead
  • From: Flash Gordon
• Re: typecasting
  • From: Flash Gordon
• the mystery of <ctrl-d>
  • From: chandanlinster
• programming-challenges
  • From: Ajinkya
• Re: break statement in a for loop
  • From: Malcolm McLean
• Re: typecasting
  • From: Malcolm McLean
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: deostroll
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: deostroll
• typecasting
  • From: aki
• Re: gets() is dead
  • From: Harald van Dijk
• Re: long integer multiplication
  • From: Joe Estock
• Re: break statement in a for loop
  • From: Harald van Dijk
• Re: Common Routine To Call (Almost) Identical Functions
  • From: jaysome
• Re: break statement in a for loop - TPA
  • From: Default User
• Re: long integer multiplication
  • From: Martin Ambuhl
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: jaysome
• Re: two meanings of a cast
  • From: ¬a\\/b
• Re: gets() is dead
  • From: ¬a\\/b
• Re: break statement in a for loop
  • From: Richard Heathfield
• Re: C a Dead Language
  • From: ¬a\\/b
• Re: long integer multiplication
  • From: Keith Thompson
• Re: break statement in a for loop
  • From: a . mil
• Re: long integer multiplication
  • From: Richard Heathfield
• Re: break statement in a for loop
  • From: Richard Heathfield
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Keith Thompson
• Re: gets() is dead
  • From: Charles Richmond
• Re: long integer multiplication
  • From: Richard Heathfield
• Re: long integer multiplication
  • From: Wade Ward
• Re: break statement in a for loop
  • From: a . mil
• Re: long integer multiplication
  • From: Joe Estock
• Re: 2-d array using pointers
  • From: Joe Estock
• long integer multiplication
  • From: helPlease
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Malcolm McLean
• Re: comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Richard Heathfield
• Re: comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Wade Ward
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Walter Roberson
• Re: Utility to convert complex declarations into, well, lol, plain-text
  • From: Ben Pfaff
• Utility to convert complex declarations into, well, lol, plain-text
  • From: nospam
• Re: an example code of TPOP(the practice of programming),why cannot lookup
  • From: Barry Schwarz
• Re: Passing strings between functions question
  • From: Barry Schwarz
• Re: comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Jason
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Stephen Sprunk
• comment on my solution to exercise 3.3 in K&R's The C programming language
  • From: Jason
• Re: how much does free free?
  • From: Richard Tobin
• Re: how much does free free?
  • From: Richard Tobin
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Richard Tobin
• Load Testing tool
  • From: Ranjan.Das1978@xxxxxxxxx
• Re: break statement in a for loop
  • From: christian.bau
• Re: Sorting
  • From: Dave Vandervies
• Re: Anonymous functions in C.
  • From: Mark McIntyre
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Mark McIntyre
• Re: Reliably determine sign value of double in C90/C89
  • From: Keith Thompson
• Re: break statement in a for loop
  • From: Malcolm McLean
• Re: break statement in a for loop
  • From: Richard Heathfield
• Re: break statement in a for loop
  • From: klaushuotari
• break statement in a for loop
  • From: a . mil
• Re: A one's complement sanity check, please
  • From: Dan Henry
• Re: two meanings of a cast
  • From: Eric Sosman
• Re: A one's complement sanity check, please
  • From: Harald van Dijk
• Re: A one's complement sanity check, please
  • From: Harald van Dijk
• Re: random password generator
  • From: Richard Heathfield
• Re: A one's complement sanity check, please
  • From: CBFalconer
• A one's complement sanity check, please
  • From: Dan Henry
• Re: two meanings of a cast
  • From: ¬a\\/b
• Re: gets() is dead
  • From: ¬a\\/b
• Re: dijkstra algorithm
  • From: Martin Ambuhl
• Re: Sorting
  • From: Martin Ambuhl
• Re: How to call A variable parameter function
  • From: Bill Pursell
• Re: Sorting
  • From: Malcolm McLean
• Re: Common Routine To Call (Almost) Identical Functions
  • From: Malcolm McLean
• Re: Reliably determine sign value of double in C90/C89
  • From: CBFalconer
• Re: C a Dead Language
  • From: CBFalconer
• Re: Reliably determine sign value of double in C90/C89
  • From: Harald van Dijk
• Re: First n twin primes
  • From: Army1987
• Re: Common Routine To Call (Almost) Identical Functions
  • From: Eric Sosman
• Common Routine To Call (Almost) Identical Functions
  • From: gamename
• Re: Reliably determine sign value of double in C90/C89
  • From: jacob navia
• Re: First n twin primes
  • From: Army1987
• Re: dijkstra algorithm
  • From: jacob navia
• Re: First n twin primes
  • From: Army1987
• Re: First n twin primes
  • From: Army1987
• Re: C a Dead Language
  • From: Malcolm McLean
• Re: Sorting
  • From: Army1987
• random password generator
  • From: Army1987
• dijkstra algorithm
  • From: Gurpreet Singh
• Re: First n twin primes
  • From: Umesh
• Re: 2-d array using pointers
  • From: Flash Gordon
• Re: First n twin primes
  • From: Flash Gordon
• 2-d array using pointers
  • From: Bond
• Re: Sorting
  • From: Malcolm McLean
• Re: C a Dead Language
  • From: Douglas Eagleson
• Re: First n twin primes
  • From: Richard Heathfield
• Re: Trap representations for unsigned integers
  • From: Flash Gordon
• Re: Sorting
  • From: Bond
• First n twin primes
  • From: Umesh
• Re: syntax error with pointer to pointer
  • From: Ray Dillinger
• Re: gets() is dead
  • From: Army1987
• Re: Trap representations for unsigned integers
  • From: Army1987
• Initialization of an array and symbolic names for index
  • From: pozz
• Re: Sorting
  • From: Army1987
• Re: C a Dead Language
  • From: Malcolm McLean
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: deostroll
• Re: Style vs function? in arrays
  • From: mdh
• Re: Style vs function? in arrays
  • From: Richard Heathfield
• Re: Style vs function? in arrays
  • From: mdh
• Re: Style vs function? in arrays
  • From: Richard Heathfield
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Martin Ambuhl
• Re: Sorting
  • From: Malcolm McLean
• Re: Style vs function? in arrays
  • From: mdh
• Re: gets() is dead
  • From: Malcolm McLean
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Martin Ambuhl
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Chris Dollin
• Re: Sorting
  • From: Richard Harter
• Re: gets() is dead
  • From: Chris Dollin
• Re: Reliably determine sign value of double in C90/C89
  • From: Dave Vandervies
• Re: Style vs function? in arrays
  • From: Richard Heathfield
• Re: how much does free free?
  • From: Jack Klein
• Re: syntax error with pointer to pointer
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: how much does free free?
  • From: pete m
• Re: Reliably determine sign value of double in C90/C89
  • From: Richard Heathfield
• Style vs function? in arrays
  • From: mdh
• Re: how much does free free?
  • From: Jack Klein
• Re: how much does free free?
  • From: Jack Klein
• Re: Help to design a loader in C
  • From: Jack Klein
• Re: how much does free free?
  • From: pete m
• Re: Undefined Behavior
  • From: pete
• Re: how much does free free?
  • From: Wade Ward
• Re: Trap representations for unsigned integers
  • From: pete
• Re: how much does free free?
  • From: pete m
• Re: how much does free free?
  • From: Ian Collins
• how much does free free?
  • From: wojtek . fedorko
• Re: syntax error with pointer to pointer
  • From: Leo
• Re: syntax error with pointer to pointer
  • From: Ray Dillinger
• dynamic construction of va_list
  • From: pete m
• How to call A variable parameter function
  • From: CFAN
• Re: C a Dead Language
  • From: Douglas Eagleson
• Re: Reliably determine sign value of double in C90/C89
  • From: Keith Thompson
• Re: Sorting
  • From: Eric Sosman
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: syntax error with pointer to pointer
  • From: klaushuotari
• Re: Allocating memory aligned on a given boundary
  • From: Keith Thompson
• Re: Reliably determine sign value of double in C90/C89
  • From: Keith Thompson
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Richard
• Re: Reliably determine sign value of double in C90/C89
  • From: Keith Thompson
• Re: syntax error with pointer to pointer
  • From: klaushuotari
• syntax error with pointer to pointer
  • From: Ray Dillinger
• Re: Reliably determine sign value of double in C90/C89
  • From: Kenneth Brody
• Re: Reliably determine sign value of double in C90/C89
  • From: Keith Thompson
• Re: symbolic algebra computation with list
  • From: klaushuotari
• Re: C a Dead Language
  • From: Keith Thompson
• Re: gets() is dead
  • From: Keith Thompson
• Re: gets() is dead
  • From: Drew Lawson
• Re: Allocating memory aligned on a given boundary
  • From: CBFalconer
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: gets() is dead
  • From: CBFalconer
• Re: Reliably determine sign value of double in C90/C89
  • From: jacob navia
• Re: Reliably determine sign value of double in C90/C89
  • From: Dave Vandervies
• Re: calculator program with memory function
  • From: Joe Wright
• Re: C a Dead Language
  • From: Wade Ward
• Re: Sorting
  • From: Malcolm McLean
• Re: Reliably determine sign value of double in C90/C89
  • From: Flash Gordon
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• symbolic algebra computation with list
  • From: xhunga
• Re: Reliably determine sign value of double in C90/C89
  • From: Martin Ambuhl
• Re: C a Dead Language
  • From: Martin Ambuhl
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: Reliably determine sign value of double in C90/C89
  • From: Eric Sosman
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: Sorting
  • From: Martin Ambuhl
• Re: Allocating memory aligned on a given boundary
  • From: Keith Thompson
• Re: C a Dead Language
  • From: Wade Ward
• Re: C a Dead Language
  • From: Kenneth Brody
• Re: gets() is dead
  • From: Malcolm McLean
• Re: Reliably determine sign value of double in C90/C89
  • From: Army1987
• Re: C a Dead Language
  • From: Clever Monkey
• Re: Reliably determine sign value of double in C90/C89
  • From: Army1987
• Re: Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: Reliably determine sign value of double in C90/C89
  • From: Dave Vandervies
• Re: gets() is dead
  • From: Dave Vandervies
• Re: gets() is dead
  • From: Flash Gordon
• Re: C a Dead Language
  • From: Default User
• Re: Reliably determine sign value of double in C90/C89
  • From: Flash Gordon
• Reliably determine sign value of double in C90/C89
  • From: artifact . one
• Re: gets() is dead
  • From: Ian Collins
• Re: gets() is dead
  • From: Ian Collins
• Re: gets() is dead
  • From: Malcolm McLean
• Re: C a Dead Language
  • From: klaushuotari
• Re: C a Dead Language
  • From: Chris Dollin
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: two meanings of a cast
  • From: Eric Sosman
• Re: Operand of postfix operator ->
  • From: Flash Gordon
• Re: gets() is dead
  • From: Malcolm McLean
• Re: C a Dead Language
  • From: CBFalconer
• Re: NULL pointer internal representation.
  • From: christian.bau
• Re: two meanings of a cast
  • From: ¬a\\/b
• Re: Operand of postfix operator ->
  • From: CBFalconer
• Re: gets() is dead
  • From: Harald van Dijk
• Re: gets() is dead
  • From: Flash Gordon
• Re: Allocating memory aligned on a given boundary
  • From: CBFalconer
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Walter Roberson
• Re: gets() is dead
  • From: ¬a\\/b
• Re: C a Dead Language
  • From: Ivar Rosquist
• Re: struct declaration query
  • From: Kenneth Brody
• Re: Sorting
  • From: Roland Pibinger
• Re: C a Dead Language
  • From: Douglas Eagleson
• C a Dead Language
  • From: Douglas Eagleson
• Re: Allocating memory aligned on a given boundary
  • From: Kenneth Brody
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Al Balmer
• Re: gets() is dead
  • From: Richard Heathfield
• Re: NULL pointer internal representation.
  • From: Walter Roberson
• Re: gets() is dead
  • From: Default User
• Re: NULL pointer internal representation.
  • From: Drew Lawson
• Re: gets() is dead
  • From: Default User
• Re: struct declaration query
  • From: Drew Lawson
• Re: Sorting
  • From: Eric Sosman
• Re: Sorting
  • From: Umesh
• Re: gets() is dead
  • From: Dave Vandervies
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: gets() is dead
  • From: Harald van Dijk
• Re: Operand of postfix operator ->
  • From: Richard Tobin
• Re: Info about the GNU C Compiler...?
  • From: Kenny McCormack
• Re: Help to design a loader in C
  • From: Kenny McCormack
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Help to design a loader in C
  • From: paras sharma
• Re: Operand of postfix operator ->
  • From: Rajesh S R
• Re: NULL pointer internal representation.
  • From: CBFalconer
• Re: K&R2 exercise 1.13
  • From: Army1987
• Re: two meanings of a cast
  • From: Eric Sosman
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: CBFalconer
• Re: PDB File
  • From: CBFalconer
• Re: shared memory malloc library
  • From: CBFalconer
• Re: Allocating memory aligned on a given boundary
  • From: CBFalconer
• Re: string size greater than page size?
  • From: Army1987
• Re: two meanings of a cast
  • From: Chris Dollin
• Re: gets() is dead
  • From: CBFalconer
• Re: two meanings of a cast
  • From: Chris Dollin
• Re: two meanings of a cast
  • From: Army1987
• Re: gets() is dead
  • From: CBFalconer
• Re: K&R2 exercise 1.13
  • From: Army1987
• Re: gets() is dead
  • From: Richard Heathfield
• Re: K&R2 exercise 1.13
  • From: Army1987
• Re: gets() is dead
  • From: Christopher Benson-Manica
• Re: two meanings of a cast
  • From: Felix Kater
• Re: two meanings of a cast
  • From: Felix Kater
• Re: two meanings of a cast
  • From: Eric Sosman
• Re: two meanings of a cast
  • From: pemo
• Re: gets() is dead
  • From: Michael Brennan
• Re: two meanings of a cast
  • From: Charlton Wilbur
• Re: two meanings of a cast
  • From: Chris Dollin
• Re: NULL pointer internal representation.
  • From: Chris Dollin
• Re: NULL pointer internal representation.
  • From: christian.bau
• Re: NULL pointer internal representation.
  • From: christian.bau
• Re: NULL pointer internal representation.
  • From: Richard Bos
• Re: NULL pointer internal representation.
  • From: Richard Tobin
• Re: NULL pointer internal representation.
  • From: khan
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: Richard Tobin
• two meanings of a cast
  • From: Felix Kater
• Re: NULL pointer internal representation.
  • From: Chris Dollin
• NULL pointer internal representation.
  • From: khan
• Re: Measuring running time in a general + portable way
  • From: websnarf
• Re: Sorting
  • From: bytebro
• Re: Measuring running time in a general + portable way
  • From: Richard Bos
• Sorting
  • From: Umesh
• Re: Info about the GNU C Compiler...? (Then what about linux?)
  • From: arun
• Re: shared memory malloc library
  • From: llothar
• Re: string size greater than page size?
  • From: Chris Dollin
• Re: gets() is dead
  • From: Chris Dollin
• Re: gets() is dead
  • From: Chris Dollin
• Re: Search input string
  • From: Nick Keighley
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: ¬a\\/b
• Re: gets() is dead
  • From: ¬a\\/b
• Re: gets() is dead
  • From: Flash Gordon
• Re: output problem
  • From: Dietmar Schindler
• video lectures on C and other programming and Computer science.
  • From: AK444
• Re: output problem
  • From: Chris Torek
• Re: gets() is dead
  • From: jacob navia
• Re: gets() is dead
  • From: Richard Bos
• Re: PDB File
  • From: Tim Prince
• Re: gets() is dead
  • From: Richard Bos
• Re: Search input string
  • From: jaysome
• Re: Anonymous functions in C.
  • From: Richard Bos
• Re: PDB File
  • From: Vinoj
• Re: Info about the GNU C Compiler...?
  • From: Richard Heathfield
• Re: calculator program with memory function
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: shared memory malloc library
  • From: Walter Roberson
• Re: printf length modifier
  • From: Harald van Dijk
• Re: shared memory malloc library
  • From: llothar
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: calculator program with memory function
  • From: Joe Estock
• Re: printf length modifier
  • From: Jack Klein
• Re: shared memory malloc library
  • From: Walter Roberson
• Re: calculator program with memory function
  • From: CBFalconer
• Re: Info about the GNU C Compiler...?
  • From: CBFalconer
• Re: output problem
  • From: CBFalconer
• Re: gets() is dead
  • From: Michael Brennan
• Re: shared memory malloc library
  • From: llothar
• Re: low-level pointer vs. array question
  • From: CBFalconer
• Re: Allocating memory aligned on a given boundary
  • From: CBFalconer
• Re: gets() is dead
  • From: CBFalconer
• Re: gets() is dead
  • From: CBFalconer
• Re: string size greater than page size?
  • From: christian.bau
• string size greater than page size?
  • From: lazy
• Re: struct declaration query
  • From: Old Wolf
• Re: gets() is dead
  • From: Christopher Benson-Manica
• Re: gets() is dead
  • From: Keith Thompson
• Re: gets() is dead
  • From: Flash Gordon
• Re: output problem
  • From: Mark McIntyre
• Re: shared memory malloc library
  • From: Mark McIntyre
• Re: low-level pointer vs. array question
  • From: Keith Thompson
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Re: calculator program with memory function
  • From: Ian Collins
• Re: gets() is dead
  • From: Ian Collins
• Re: gets() is dead
  • From: Malcolm McLean
• Re: calculator program with memory function
  • From: Eric Sosman
• Re: Practical uses of XOR
  • From: Keith Thompson
• Re: Practical uses of XOR
  • From: Ian Collins
• Re: Info about the GNU C Compiler...?
  • From: Keith Thompson
• Re: calculator program with memory function
  • From: Martin Ambuhl
• Re: output problem
  • From: Keith Thompson
• Re: low-level pointer vs. array question
  • From: Flash Gordon
• Re: printf length modifier
  • From: Keith Thompson
• Re: low-level pointer vs. array question
  • From: Bond
• Re: printf length modifier
  • From: Harald van Dijk
• Re: calculator program with memory function
  • From: Flash Gordon
• Re: calculator program with memory function
  • From: Clever Monkey
• calculator program with memory function
  • From: Vijaykumar Dave
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Keith Thompson
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Harald van Dijk
• Re: gets() is dead
  • From: Charlton Wilbur
• Re: gets() is dead
  • From: Malcolm McLean
• Re: struct declaration query
  • From: CptDondo
• Re: Practical uses of XOR
  • From: BiGYaN
• Re: struct declaration query
  • From: Ian Collins
• Re: struct declaration query
  • From: Drew Lawson
• Re: gets() is dead
  • From: Dave Vandervies
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Re: Measuring running time in a general + portable way
  • From: Ian Collins
• Re: gets() is dead
  • From: Default User
• struct declaration query
  • From: CptDondo
• Re: Search input string
  • From: Clever Monkey
• Re: gets() is dead
  • From: Dave Vandervies
• Re: gets() is dead
  • From: Dave Vandervies
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Search input string
  • From: lucky_therock
• Re: printf length modifier
  • From: Flash Gordon
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: qed
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Flash Gordon
• Re: printf length modifier
  • From: Harald van Dijk
• Re: gets() is dead
  • From: Flash Gordon
• Re: gets() is dead
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Gregor H .
• Re: gets() is dead
  • From: Eric Sosman
• Re: gets() is dead
  • From: Francine . Neary
• Re: Info about the GNU C Compiler...?
  • From: Richard Tobin
• Re: Info about the GNU C Compiler...?
  • From: Gregor H .
• Re: Info about the GNU C Compiler...?
  • From: Gregor H .
• Re: Info about the GNU C Compiler...?
  • From: Clever Monkey
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Re: Info about the GNU C Compiler...?
  • From: Walter Roberson
• Re: Undefined Behavior
  • From: Christopher Benson-Manica
• Re: Info about the GNU C Compiler...?
  • From: Richard Heathfield
• Info about the GNU C Compiler...?
  • From: arun
• Re: Info about the GNU C Compiler...?
  • From: Marc Boyer
• Re: Reversing order of words in a given string
  • From: Kelly B
• Re: gets() is dead
  • From: Richard Heathfield
• Re: printf length modifier
  • From: Flash Gordon
• Re: shared memory malloc library
  • From: Walter Roberson
• Re: PDB File
  • From: Walter Roberson
• Re: shared memory malloc library
  • From: Richard Tobin
• Re: output problem
  • From: Dietmar Schindler
• Re: printf length modifier
  • From: Spoon
• Re: Measuring running time in a general + portable way
  • From: Richard Harter
• Re: Operand of postfix operator ->
  • From: Rajesh S R
• Re: gets() is dead
  • From: Chris Dollin
• Re: gets() is dead
  • From: Eric Sosman
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: 64-bit datatype
  • From: websnarf
• Re: gets() is dead
  • From: websnarf
• Re: shared memory malloc library
  • From: Flash Gordon
• Re: printf length modifier
  • From: Flash Gordon
• Re: gets() is dead
  • From: Kenny McCormack
• Re: Measuring running time in a general + portable way
  • From: Flash Gordon
• Re: printf length modifier
  • From: Flash Gordon
• Re: Retrieving NIC bitrate
  • From: Joachim Schmitz
• Retrieving NIC bitrate
  • From: thomasau
• [OT] Re: 64-bit datatype
  • From: Bjørn Augestad
• Re: printf length modifier
  • From: Spoon
• Re: 64-bit datatype
  • From: Jake Langham
• Re: printf length modifier
  • From: CBFalconer
• Re: shared memory malloc library
  • From: Richard Tobin
• Re: Measuring running time in a general + portable way
  • From: Richard Heathfield
• Re: Measuring running time in a general + portable way
  • From: CBFalconer
• Re: Undefined Behavior
  • From: Gregor H .
• Re: Measuring running time in a general + portable way
  • From: CBFalconer
• Re: Retrieving NIC bit rate
  • From: Ian Collins
• Re: Measuring running time in a general + portable way
  • From: Ian Collins
• Re: Undefined Behavior
  • From: CBFalconer
• Re: Undefined Behavior
  • From: Joachim Schmitz
• Re: gets() is dead
  • From: Richard Bos
• Re: Measuring running time in a general + portable way
  • From: Joachim Schmitz
• Re: Measuring running time in a general + portable way
  • From: Richard Heathfield
• Re: Undefined Behavior
  • From: Gregor H .
• Re: Arrays
  • From: mdeh
• Re: Arrays
  • From: mdeh
• CMMI Resource
  • From: greame . hook77
• Retrieving NIC bit rate
  • From: thomasau
• Re: shared memory malloc library
  • From: Chris Dollin
• printf length modifier
  • From: Spoon
• Re: PDB File
  • From: Ian Collins
• PDB File
  • From: Rajeshwaran
• Re: Arrays
  • From: Jens Thoms Toerring
• Re: Measuring running time in a general + portable way
  • From: Ian Collins
• Re: Measuring running time in a general + portable way
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Keith Thompson
• Re: 64-bit datatype
  • From: Michael
• Re: Arrays
  • From: Richard Heathfield
• Re: gets() is dead
  • From: jaysome
• Re: Operand of postfix operator ->
  • From: whyglinux
• Re: gets() is dead
  • From: Richard Heathfield
• Re: Measuring running time in a general + portable way
  • From: Ian Collins
• Re: 64-bit datatype
  • From: jaysome
• Re: gets() is dead
  • From: Keith Thompson
• Re: gets() is dead
  • From: Malcolm McLean
• Re: 64-bit datatype
  • From: Malcolm McLean
• Re: malloc()
  • From: Malcolm McLean
• Re: Reversing order of words in a given string
  • From: CBFalconer
• Re: Arrays
  • From: mdeh
• Re: measuring running time
  • From: Ben Pfaff
• Reversing order of words in a given string
  • From: Kelly B
• Re: Allocating memory aligned on a given boundary
  • From: Dave Vandervies
• Re: gets() is dead
  • From: Keith Thompson
• Re: measuring running time
  • From: Dave Vandervies
• Re: Undefined Behavior
  • From: Martin Ambuhl
• Re: Measuring running time in a general + portable way
  • From: CBFalconer
• measuring running time
  • From: upperclass
• Re: K&R2 exercise 1.13
  • From: CBFalconer
• Re: gets() is dead
  • From: CBFalconer
• Re: Allocating memory aligned on a given boundary
  • From: CBFalconer
• Re: shared memory malloc library
  • From: CBFalconer
• Re: No. of 'ab' or specific word in a text file
  • From: CBFalconer
• Re: 64-bit datatype
  • From: jacob navia
• Re: enum types and extern
  • From: kar1107@xxxxxxxxx
• Re: shared memory malloc library
  • From: Ian Collins
• Measuring running time in a general + portable way
  • From: upperclass
• Re: shared memory malloc library
  • From: llothar
• Re: Allocating memory aligned on a given boundary
  • From: Doug
• Re: gets() is dead
  • From: Default User
• Re: RFC: the state of charset support in C
  • From: Keith Thompson
• Re: union member
  • From: Ben Pfaff
• Re: Howto pass va_list to another va func
  • From: Tor Rustad
• Re: RFC: the state of charset support in C
  • From: Richard Heathfield
• Re: K&R2 exercise 1.13
  • From: Army1987
• Re: RFC: the state of charset support in C
  • From: Old Wolf
• Re: 64-bit datatype
  • From: Ian Collins
• Re: K&R2 exercise 1.13
  • From: Army1987
• Re: gets() is dead
  • From: Ian Collins
• Re: 64-bit datatype
  • From: Keith Thompson
• Re: union member
  • From: Keith Thompson
• Re: Undefined Behavior
  • From: Christopher Benson-Manica
• Re: low-level pointer vs. array question
  • From: Keith Thompson
• Re: low-level pointer vs. array question
  • From: Keith Thompson
• Re: Howto pass va_list to another va func
  • From: Eric Sosman
• Re: memcpy question
  • From: Keith Thompson
• Re: Howto pass va_list to another va func
  • From: Flash Gordon
• Re: gets() is dead
  • From: Keith Thompson
• Re: Practical uses of XOR
  • From: Joe Wright
• Re: Allocating memory aligned on a given boundary
  • From: Keith Thompson
• Re: Howto pass va_list to another va func
  • From: Tor Rustad
• Re: gets() is dead
  • From: Flash Gordon
• Howto pass va_list to another va func
  • From: Tor Rustad
• Re: gets() is dead
  • From: Christopher Benson-Manica
• Re: gets() is dead
  • From: Default User
• Re: gets() is dead
  • From: Dave Vandervies
• Re: Arrays
  • From: Jens Thoms Toerring
• Re: Practical uses of XOR
  • From: Default User
• Re: New freeware Win hex calculator here
  • From: Coos Haak
• Re: 64-bit datatype
  • From: Eric Sosman
• Re: union member
  • From: Eric Sosman
• Re: Practical uses of XOR
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Tor Rustad
• Re: 64-bit datatype
  • From: Martin Ambuhl
• Re: gets() is dead
  • From: Al Balmer
• 64-bit datatype
  • From: Jake Langham
• Re: union member
  • From: Ben Pfaff
• Re: Practical uses of XOR
  • From: Default User
• Re: union member
  • From: Kenneth Brody
• Re: gets() is dead
  • From: Charlton Wilbur
• Re: Undefined Behavior
  • From: Gregor H .
• Re: union member
  • From: Ben Pfaff
• Re: low-level pointer vs. array question
  • From: Eric Sosman
• Re: union member
  • From: Drew Lawson
• Re: gets() is dead
  • From: Christopher Benson-Manica
• Re: K&R2 exercise 1.13
  • From: Bjørn Augestad
• Re: gets() is dead
  • From: Richard Tobin
• Re: gets() is dead
  • From: Ben Pfaff
• Re: gets() is dead
  • From: Kenny McCormack
• Re: gets() is dead
  • From: Richard Heathfield
• Re: No. of 'ab' or specific word in a text file
  • From: James Kanze
• Re: Undefined Behavior
  • From: Martin Ambuhl
• K&R2 exercise 1.13
  • From: Army1987
• Re: Practical uses of XOR
  • From: Charles Richmond
• Re: gets() is dead
  • From: Tor Rustad
• Re: low-level pointer vs. array question
  • From: copx
• Re: gets() is dead
  • From: Al Balmer
• Re: Allocating memory aligned on a given boundary
  • From: Kenneth Brody
• Re: Allocating memory aligned on a given boundary
  • From: Kenneth Brody
• Re: Practical uses of XOR
  • From: Giorgos Keramidas
• Re: Arrays
  • From: pete
• Re: Practical uses of XOR
  • From: pete
• Re: Undefined Behavior
  • From: CBFalconer
• Re: function _findfirst with a pathname containing a blank
  • From: Tor Rustad
• Re: low-level pointer vs. array question
  • From: copx
• Re: low-level pointer vs. array question
  • From: Mike Wahler
• Re: low-level pointer vs. array question
  • From: Richard Heathfield
• Re: "a book on c" Kelly & Pohl (4e)
  • From: Jan Werner
• Re: Undefined Behavior
  • From: Richard Tobin
• low-level pointer vs. array question
  • From: copx
• Re: Undefined Behavior
  • From: Richard Heathfield
• Re: Practical uses of XOR
  • From: David Starr
• Re: doubt related to static library
  • From: Pierre Asselin
• Re: doubt related to static library
  • From: Joachim Schmitz
• Undefined Behavior
  • From: bbaale
• Re: enum types and extern
  • From: Chris Dollin
• Re: Practical uses of XOR
  • From: CBFalconer
• Re: enum types and extern
  • From: Chris Dollin
• Re: gets() is dead
  • From: CBFalconer
• Re: memcpy question
  • From: David Starr
• Re: enum types and extern
  • From: CBFalconer
• Re: Volatility of padding bytes?
  • From: Eric Sosman
• Re: Practical uses of XOR
  • From: Army1987
• Re: gets() is dead
  • From: Eric Sosman
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: Volatility of padding bytes?
  • From: smanohar
• Re: Allocating memory aligned on a given boundary
  • From: Richard Bos
• doubt related to static library
  • From: sam_cit
• Re: enum types and extern
  • From: Richard Heathfield
• Re: enum types and extern
  • From: Chris Dollin
• Re: enum types and extern
  • From: Richard Tobin
• Re: shared memory malloc library
  • From: Roland Pibinger
• Re: Practical uses of XOR
  • From: Richard Heathfield
• Re: Practical uses of XOR
  • From: Marcin Wolcendorf
• Re: gets() is dead
  • From: Keith Thompson
• Re: function _findfirst with a pathname containing a blank
  • From: Richard Heathfield
• Re: function _findfirst with a pathname containing a blank
  • From: Chris Dollin
• function _findfirst with a pathname containing a blank
  • From: hpber
• Re: enum types and extern
  • From: Chris Dollin
• Re: Allocating memory aligned on a given boundary
  • From: Ian Collins
• Re: Practical uses of XOR
  • From: Richard Heathfield
• Re: Practical uses of XOR
  • From: Marcin Wolcendorf
• Re: Operand of postfix operator ->
  • From: Flash Gordon
• Re: Allocating memory aligned on a given boundary
  • From: K. Jennings
• Re: union member
  • From: Joachim Schmitz
• union member
  • From: irwishlaw
• Re: help pls...
  • From: Richard Heathfield
• help pls...
  • From: phillip
• Re: memcpy question
  • From: Richard Heathfield
• Re: gets() is dead
  • From: Richard Heathfield
• Re: Operand of postfix operator ->
  • From: whyglinux
• Re: Arrays
  • From: CBFalconer
• Re: memcpy question
  • From: Gordon Burditt
• memcpy question
  • From: 2b|!2b==?
• Re: Arrays
  • From: Beej Jorgensen
• Re: Count total no. of characters,words & sentences in a text file
  • From: lovecreatesbea...@xxxxxxxxx
• Arrays
  • From: mdh
• Re: newbie
  • From: Dave Vandervies
• Re: enum types and extern
  • From: CBFalconer
• Re: gets() is dead
  • From: Keith Thompson
• Re: dynamic mem
  • From: CBFalconer
• newbie
  • From: poison tooth
• Re: gets() is dead
  • From: Gregor H .
• Re: enum types and extern
  • From: Mark McIntyre
• gets() is dead
  • From: jacob navia
• Re: Operand of postfix operator ->
  • From: Richard Tobin
• Re: dynamic mem
  • From: pete
• Re: shared memory malloc library
  • From: CBFalconer
• Re: Search for an expression in a text file
  • From: CBFalconer
• Re: Search for an expression in a text file
  • From: Jonas
• Re: asking a question about pointer array.
  • From: Flash Gordon
• Re: extern and enum typed variables
  • From: pete
• Re: asking a question about pointer array.
  • From: Richard Heathfield
• Re: shared memory malloc library
  • From: Richard Tobin
• Re: Trap representations for unsigned integers
  • From: Keith Thompson
• Re: shared memory malloc library
  • From: Keith Thompson
• Re: Operand of postfix operator ->
  • From: Keith Thompson
• Re: Allocating memory aligned on a given boundary
  • From: Eric Sosman
• Re: Allocating memory aligned on a given boundary
  • From: K. Jennings
• Re: asking a question about pointer array.
  • From: Flash Gordon
• Re: Allocating memory aligned on a given boundary
  • From: Army1987
• Re: shared memory malloc library
  • From: CBFalconer
• Re: Operand of postfix operator ->
  • From: Army1987
• Re: Deleting a File
  • From: Walter Roberson
• Re: asking a question about pointer array.
  • From: Roland Pibinger
• Re: Operand of postfix operator ->
  • From: Martin Ambuhl
• Re: Deleting a File
  • From: Flash Gordon
• Re: Deleting a File
  • From: zero
• Re: asking a question about pointer array.
  • From: Martin Ambuhl
• Re: Trap representations for unsigned integers
  • From: Army1987
• Re: malloc()
  • From: Walter Roberson
• Re: just want detail information
  • From: Army1987
• Re: Allocating memory aligned on a given boundary
  • From: Walter Roberson
• Re: malloc()
  • From: websnarf
• Re: Allocating memory aligned on a given boundary
  • From: Flash Gordon
• Re: Allocating memory aligned on a given boundary
  • From: Richard Heathfield
• Allocating memory aligned on a given boundary
  • From: K. Jennings
• Re: Operand of postfix operator ->
  • From: Rajesh S R
• Re: Count total no. of characters,words & sentences in a text file
  • From: lovecreatesbea...@xxxxxxxxx
• Re: Operand of postfix operator ->
  • From: Richard Tobin
• Re: shared memory malloc library
  • From: Walter Roberson
• Re: Operand of postfix operator ->
  • From: Rajesh S R
• enum types and extern
  • From: Charlie
• Re: Search for an expression in a text file
  • From: Al Balmer
• Re: Deleting a File
  • From: kvnsmnsn
• shared memory malloc library
  • From: llothar
• Re: Operand of postfix operator ->
  • From: Stephen Sprunk
• Re: Operand of postfix operator ->
  • From: Richard Tobin
• Re: extern and enum typed variables
  • From: Chris Dollin
• extern and enum typed variables
  • From: Charlie
• Re: Array of Array Initialisation
  • From: Duncan Muirhead
• Re: operand of postfix operator->
  • From: Chris Dollin
• Re: Search for an expression in a text file
  • From: Richard Heathfield
• operand of postfix operator->
  • From: Rajesh S R
• Re: Just a test, please ignore
  • From: Christopher Benson-Manica
• Re: Array of Array Initialisation
  • From: Christopher Benson-Manica
• Array of Array Initialisation
  • From: Olaf P.
• Re: Operand of postfix operator ->
  • From: Chris Dollin
• Re: Operand of postfix operator ->
  • From: Richard Tobin
• Operand of postfix operator ->
  • From: Rajesh S R
• Re: Search for an expression in a text file
  • From: ritesh
• Re: Search for an expression in a text file
  • From: B. Augestad
• Re: Just a test, please ignore
  • From: Dave Vandervies
• Re: Search for an expression in a text file
  • From: ritesh
• Re: Search for an expression in a text file
  • From: ritesh
• Re: asking a question about pointer array.
  • From: Jonas
• asking a question about pointer array.
  • From: rakhshanda . malik
• Re: Search for an expression in a text file
  • From: Keith Thompson
• Re: Search for an expression in a text file
  • From: Richard Heathfield
• Re: malloc()
  • From: Keith Thompson
• Re: Search for an expression in a text file
  • From: Keith Thompson
• Re: dynamic mem
  • From: Chris Dollin
• work at home from internet.and earn 4000USD every month
  • From: sibel
• Re: How to traverse the items in an array ?
  • From: Richard Heathfield
• Re: Turbo c
  • From: Richard Heathfield
• Re: dynamic mem
  • From: Ian Collins
• Re: dynamic mem
  • From: mark_bluemel
• Re: Search for an expression in a text file
  • From: Richard Heathfield
• dynamic mem
  • From: gNash
• Just a test, please ignore
  • From: kwikius
• Re: How to traverse the items in an array ?
  • From: etherzhhb@xxxxxxxxx
• Re: Turbo c
  • From: Nick Keighley
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Harter
• Link Direct to Order Page
  • From: pandiyan.gpandi@xxxxxxxxx
• Re: Search for an expression in a text file
  • From: Jonas
• Re: malloc()
  • From: CBFalconer
• Re: malloc()
  • From: Martin Ambuhl
• Re: Deleting a File
  • From: Richard Bos
• Re: C Object System
  • From: Richard Bos
• malloc()
  • From: sam_cit
• Re: Search for an expression in a text file
  • From: ritesh
• Re: Search for an expression in a text file
  • From: Peter Nilsson
• Turbo c
  • From: phillip
• Search for an expression in a text file
  • From: ritesh
• Re: Deleting a File
  • From: CBFalconer
• Re: C Object System
  • From: CBFalconer
• Re: RFC: the state of charset support in C
  • From: Peter Nilsson
• Re: Deleting a File
  • From: Martin Ambuhl
• Re: Count total no. of characters,words & sentences in a text file
  • From: John Bode
• Re: C Object System
  • From: Richard Heathfield
• Re: Count total no. of characters,words & sentences in a text file
  • From: Ian Collins
• Re: Deleting a File
  • From: Flash Gordon
• Re: Deleting a File
  • From: Ben Pfaff
• Re: Deleting a File
  • From: Richard Tobin
• Deleting a File
  • From: kvnsmnsn
• Re: RFC: the state of charset support in C
  • From: Keith Thompson
• Re: RFC: the state of charset support in C
  • From: Richard Heathfield
• Re: C Object System
  • From: Richard Tobin
• Re: Test Your C Skills - Errors
  • From: Christopher Benson-Manica
• Re: C Object System
  • From: Richard Heathfield
• Re: just want detail information
  • From: Keith Thompson
• Re: Count total no. of characters,words & sentences in a text file
  • From: Umesh
• Re: C Object System
  • From: Mark McIntyre
• Re: Count total no. of characters,words & sentences in a text file
  • From: Default User
• Re: Count total no. of characters,words & sentences in a text file
  • From: Default User
• Re: Count total no. of characters,words & sentences in a text file
  • From: Bill Pursell
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Chris Torek
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: atoi query - TPA
  • From: Default User
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Harter
• Re: enum bound check in compiler time in C
  • From: Duncan Muirhead
• Re: RFC: the state of charset support in C
  • From: Kenneth Brody
• Re: writing into file in c
  • From: Martin Ambuhl
• Re: enum bound check in compiler time in C
  • From: Laurent Deniau
• Re: enum bound check in compiler time in C
  • From: mark_bluemel
• Re: enum bound check in compiler time in C
  • From: Marc Boyer
• Re: enum bound check in compiler time in C
  • From: Eric Sosman
• enum bound check in compiler time in C
  • From: paragborkar
• Re: How to traverse the items in an array ?
  • From: llothar
• Re: RFC: the state of charset support in C
  • From: Richard Heathfield
• Re: RFC: the state of charset support in C
  • From: Kenneth Brody
• Re: How to traverse the items in an array ?
  • From: Richard Tobin
• Re: How to traverse the items in an array ?
  • From: Richard Heathfield
• Re: How to traverse the items in an array ?
  • From: llothar
• Re: use of strtok( )
  • From: mark_bluemel
• Re: use of strtok( )
  • From: Eric Sosman
• Re: How to traverse the items in an array ?
  • From: Richard Heathfield
• Re: use of strtok( )
  • From: Richard Heathfield
• How to traverse the items in an array ?
  • From: llothar
• Re: use of strtok( )
  • From: Kelly B
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Volatility of padding bytes?
  • From: swengineer001@xxxxxxxxx
• Re: writing into file in c
  • From: Richard Heathfield
• Re: Anonymous functions in C.
  • From: Richard Bos
• Re: error ..simple array
  • From: Flash Gordon
• error ..simple array
  • From: gNash
• Re: writing into file in c
  • From: mark_bluemel
• Re: malloc
  • From: Flash Gordon
• Re: malloc
  • From: Chris Dollin
• writing into file in c
  • From: sam_cit
• malloc
  • From: gNash
• Re: just want detail information
  • From: Flash Gordon
• Re: Volatility of padding bytes?
  • From: jaysome
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Volatility of padding bytes?
  • From: pete
• Re: C Object System
  • From: Laurent Deniau
• Re: just want detail information
  • From: Mark L Pappin
• Re: Volatility of padding bytes?
  • From: jaysome
• Re: Anonymous functions in C.
  • From: Richard Bos
• Re: just want detail information
  • From: pete
• Re: doubt regarding mmap() function call
  • From: Ian Collins
• doubt regarding mmap() function call
  • From: sam_cit
• Re: Volatility of padding bytes?
  • From: Richard Bos
• Re: Volatility of padding bytes?
  • From: Ian Collins
• Re: Volatility of padding bytes?
  • From: Francine . Neary
• Re: Volatility of padding bytes?
  • From: Francine . Neary
• Re: Volatility of padding bytes?
  • From: Francine . Neary
• Re: Test Your C Skills - Errors
  • From: Richard Bos
• Re: C Object System
  • From: Richard Bos
• Re: atoi query
  • From: Richard Bos
• Re: atoi query
  • From: Basu
• Re: Trap representations for unsigned integers
  • From: Peter Nilsson
• Re: Constant Expressions in C
  • From: Ian Collins
• Re: Constant Expressions in C
  • From: Peter Nilsson
• Re: Constant Expressions in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: Constant Expressions in C
  • From: Peter Nilsson
• Re: Constant Expressions in C
  • From: christian.bau
• Re: Volatility of padding bytes?
  • From: Ian Collins
• Re: Mapping a struct to a memory block....
  • From: Ian Collins
• Re: Volatility of padding bytes?
  • From: Roberto Waltman
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: Richard Tobin
• Re: Mapping a struct to a memory block....
  • From: Ben Pfaff
• Re: Volatility of padding bytes?
  • From: jacob navia
• Volatility of padding bytes?
  • From: Francine . Neary
• Re: Mapping a struct to a memory block....
  • From: Ian Collins
• Re: atoi query
  • From: Francine . Neary
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: Francine . Neary
• Re: Mapping a struct to a memory block....
  • From: Francine . Neary
• Re: C Object System
  • From: Old Wolf
• Re: Processing command line arguments
  • From: Francine . Neary
• Re: Passing strings between functions question
  • From: Old Wolf
• Re: 32 or 64 bit processor info in C
  • From: Francine . Neary
• Re: Test Your C Skills - Errors
  • From: Old Wolf
• Re: DHCP and RAW socket and C
  • From: Walter Roberson
• DHCP and RAW socket and C
  • From: yannifan
• Re: just want detail information
  • From: Keith Thompson
• Re: just want detail information
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: use of strtok( )
  • From: Richard Heathfield
• use of strtok( )
  • From: Kelly B
• Re: Test Your C Skills - Errors
  • From: Sharath
• Re: Anonymous functions in C.
  • From: Servé Laurijssen
• Re: 32 or 64 bit processor info in C
  • From: Ben Pfaff
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: just want detail information
  • From: Army1987
• Re: Calculating salary
  • From: Chris Hills
• Re: Anonymous functions in C.
  • From: Army1987
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: Anonymous functions in C.
  • From: Army1987
• Re: just want detail information
  • From: zero
• Re: just want detail information
  • From: zero
• Re: just want detail information
  • From: pete
• Re: Anonymous functions in C.
  • From: Steve Thompson
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Anonymous functions in C.
  • From: Steve Thompson
• Re: just want detail information
  • From: CBFalconer
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: just want detail information
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: just want detail information
  • From: ashu
• Re: just want detail information
  • From: Mark L Pappin
• Re: just want detail information
  • From: pete
• just want detail information
  • From: ashu
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: how to write in a file
  • From: Chris Dollin
• Re: Anonymous functions in C.
  • From: Chris Dollin
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Constant Expressions in C
  • From: Keith Thompson
• Re: RFC: the state of charset support in C
  • From: William Ahern
• Re: RFC: the state of charset support in C
  • From: Jack Klein
• Re: gtk+-2.0, GtkEntry - set cursor problems.
  • From: fabricio.b.cabral@xxxxxxxxx
• Re: gtk+-2.0, GtkEntry - set cursor problems.
  • From: llothar
• Re: Anonymous functions in C.
  • From: Ian Collins
• Re: how to write in a file
  • From: Chris Torek
• Re: Sample implementation of Dijkstras algorithm
  • From: Mark McIntyre
• Re: sscanf return value
  • From: Chris Torek
• Re: Sample implementation of Dijkstras algorithm
  • From: pete
• Re: Anonymous functions in C.
  • From: Chris Torek
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: Anonymous functions in C.
  • From: Steve Thompson
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Sample implementation of Dijkstras algorithm
  • From: Richard Heathfield
• Re: Sample implementation of Dijkstras algorithm
  • From: pete
• Re: Anonymous functions in C.
  • From: Ian Collins
• gtk+-2.0, GtkEntry - set cursor problems.
  • From: jnakam
• gtk+-2.0, GtkEntry - set cursor problems.
  • From: jnakam
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Constant Expressions in C
  • From: kar1107@xxxxxxxxx
• Sample implementation of Dijkstras algorithm
  • From: thomasau
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Anonymous functions in C.
  • From: Dave Vandervies
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Calculating salary
  • From: hmmtn
• Re: Processing command line arguments
  • From: Gregor H .
• Re: sscanf return value
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: sscanf return value
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: Calculating salary
  • From: hmmtn
• RFC: the state of charset support in C
  • From: Joshua Haberman
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Anonymous functions in C.
  • From: Ian Collins
• Re: Anonymous functions in C.
  • From: Michal Nazarewicz
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Calculating salary
  • From: hmmtn
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Anonymous functions in C.
  • From: CBFalconer
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Test Your C Skills - Errors
  • From: pete
• Re: Anonymous functions in C.
  • From: jacob.navia
• Re: Calculating salary
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Calculating salary
  • From: hmmtn
• Re: C Object System
  • From: Marco
• Re: 32 or 64 bit processor info in C
  • From: Francine . Neary
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: Processing command line arguments
  • From: Francine . Neary
• Re: Anonymous functions in C.
  • From: Harald van Dijk
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Anonymous functions in C.
  • From: Eric Sosman
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: Anonymous functions in C.
  • From: Michal Nazarewicz
• Re: C Object System
  • From: Mark McIntyre
• Re: Test Your C Skills - Errors
  • From: ¬a\\/b
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Mapping a struct to a memory block....
  • From: Mark McIntyre
• Re: Mapping a struct to a memory block....
  • From: Mark McIntyre
• Re: sscanf return value
  • From: gio
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: Anonymous functions in C.
  • From: Michal Nazarewicz
• Re: Anonymous functions in C.
  • From: jacob.navia
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: Anonymous functions in C.
  • From: jacob.navia
• Re: Anonymous functions in C.
  • From: Michal Nazarewicz
• Re: Test Your C Skills - Errors
  • From: Joe Estock
• Re: sscanf return value
  • From: Malcolm McLean
• Re: wht's
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: wht's
  • From: Martin Ambuhl
• Re: Constant Expressions in C
  • From: christian.bau
• Re: wht's
  • From: August Karlstrom
• Re: Anonymous functions in C.
  • From: jacob.navia
• Re: wht's
  • From: CBFalconer
• Re: sscanf return value
  • From: CBFalconer
• Re: Test Your C Skills - Errors
  • From: CBFalconer
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Trap representations for unsigned integers
  • From: Army1987
• Re: Trap representations for unsigned integers
  • From: Harald van Dijk
• Re: Trap representations for unsigned integers
  • From: Harald van Dijk
• Re: Trap representations for unsigned integers
  • From: Harald van Dijk
• Re: wht's
  • From: Army1987
• Re: Trap representations for unsigned integers
  • From: Army1987
• Re: Trap representations for unsigned integers
  • From: Army1987
• Re: Trap representations for unsigned integers
  • From: Harald van Dijk
• Re: Trap representations for unsigned integers
  • From: Army1987
• Re: Processing command line arguments
  • From: Harald van Dijk
• Re: Trap representations for unsigned integers
  • From: Eric Sosman
• Re: Trap representations for unsigned integers
  • From: Harald van Dijk
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Test Your C Skills - Errors
  • From: Joe Estock
• Re: sscanf return value
  • From: Army1987
• Trap representations for unsigned integers
  • From: Army1987
• Re: Passing strings between functions question
  • From: pete
• Re: Passing strings between functions question
  • From: pete
• sscanf return value
  • From: gio
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Passing strings between functions question
  • From: Walter Roberson
• Re: Passing strings between functions question
  • From: ptq2238
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Anonymous functions in C.
  • From: Harald van Dijk
• Re: Passing strings between functions question
  • From: pete
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Passing strings between functions question
  • From: tinysisi
• Re: Passing strings between functions question
  • From: Richard Heathfield
• Re: Constant Expressions in C
  • From: pete
• Re: Passing strings between functions question
  • From: Richard Tobin
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Passing strings between functions question
  • From: ptq2238
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: Processing command line arguments
  • From: Malcolm McLean
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Re: Anonymous functions in C.
  • From: Richard Tobin
• Processing command line arguments
  • From: Gregor H .
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Neil Booth
• Re: output problem
  • From: ¬a\\/b
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Constant Expressions in C
  • From: Ian Collins
• Re: Anonymous functions in C.
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: Constant Expressions in C
  • From: Jack Klein
• Re: Anonymous functions in C.
  • From: Keith Thompson
• Re: Mapping a struct to a memory block....
  • From: Keith Thompson
• Re: Mapping a struct to a memory block....
  • From: Ian Collins
• Anonymous functions in C.
  • From: jacob navia
• Re: Mapping a struct to a memory block....
  • From: barcaroller
• Re: Constant Expressions in C
  • From: Ian Collins
• Re: Reading in data into array (special case, please see)
  • From: Rob111b
• Re: C Object System
  • From: Richard Tobin
• Re: Mapping a struct to a memory block....
  • From: Ian Collins
• Re: C Object System
  • From: Keith Thompson
• Re: Mapping a struct to a memory block....
  • From: barcaroller
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Constant Expressions in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Test Your C Skills - Errors
  • From: Army1987
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: C Object System
  • From: CBFalconer
• Re: Constant Expressions in C
  • From: christian.bau
• Re: C Object System
  • From: Mark McIntyre
• Re: C Object System
  • From: Mark McIntyre
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Mapping a struct to a memory block....
  • From: Keith Thompson
• Constant Expressions in C
  • From: skibud2
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Mapping a struct to a memory block....
  • From: Ben Pfaff
• Re: Mapping a struct to a memory block....
  • From: Ian Collins
• Mapping a struct to a memory block....
  • From: barcaroller
• Re: C Object System
  • From: Ian Collins
• Re: Test Your C Skills - Errors
  • From: Ben Pfaff
• Re: Test Your C Skills - Errors
  • From: Army1987
• Re: extern and function prototypes
  • From: pete
• Re: atoi query
  • From: Keith Thompson
• Re: pinters to functions with variable arguments
  • From: Eric Sosman
• Re: pinters to functions with variable arguments
  • From: Kenneth Brody
• Re: pinters to functions with variable arguments
  • From: Harald van Dijk
• Re: pinters to functions with variable arguments
  • From: Walter Roberson
• Re: pinters to functions with variable arguments
  • From: CptDondo
• Re: Test Your C Skills - Errors
  • From: R Pradeep Chandran
• an example code of TPOP(the practice of programming),why cannot lookup
  • From: anson
• Re: pinters to functions with variable arguments
  • From: Eric Sosman
• pinters to functions with variable arguments
  • From: CptDondo
• Re: calling iwspy from a c program and using the results
  • From: Eric Sosman
• Re: postorder traversal of binary search tree without recursion
  • From: nishit . gupta
• calling iwspy from a c program and using the results
  • From: thomas . aure1
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: efficient way to process 100kb of data in C
  • From: mark_bluemel
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: efficient way to process 100kb of data in C
  • From: Chris Dollin
• Re: C Object System
  • From: John Smith
• Re: C Object System
  • From: Laurent Deniau
• Re: efficient way to process 100kb of data in C
  • From: sam_cit
• Re: efficient way to process 100kb of data in C
  • From: mark_bluemel
• Re: 32 or 64 bit processor info in C
  • From: Army1987
• Re: efficient way to process 100kb of data in C
  • From: sam_cit
• Re: C Object System
  • From: Friedrich Dominicus
• Re: efficient way to process 100kb of data in C
  • From: sam_cit
• Re: C Object System
  • From: Friedrich Dominicus
• this is a test mail
  • From: Anonyma
• Re: efficient way to process 100kb of data in C
  • From: Chris Dollin
• Re: atoi query
  • From: Flash Gordon
• Re: atoi query
  • From: CBFalconer
• Re: Test Your C Skills - Errors
  • From: Sharath
• Re: efficient way to process 100kb of data in C
  • From: sam_cit
• Re: atoi query
  • From: Richard Heathfield
• Re: efficient way to process 100kb of data in C
  • From: CBFalconer
• Re: atoi query
  • From: ptq2238
• off topic
  • From: aljaber
• Re: efficient way to process 100kb of data in C
  • From: Richard Tobin
• Re: C Object System
  • From: Richard Tobin
• Re: postorder traversal of binary search tree without recursion
  • From: saki
• Re: efficient way to process 100kb of data in C
  • From: Laurent Deniau
• Re: Text-Based Windows Library
  • From: Chris Hills
• efficient way to process 100kb of data in C
  • From: sam_cit
• Re: [OT] Re: C Object System
  • From: Laurent Deniau
• Re: 32 or 64 bit processor info in C
  • From: Richard Bos
• Re: 32 or 64 bit processor info in C
  • From: Richard Bos
• Re: extern and function prototypes
  • From: Nick Keighley
• Re: hash table
  • From: CBFalconer
• Re: sscanf behavoir
  • From: Gunvant Patil
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Richard Bos
• Re: FACTORIAL PROGRAM C99F
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: ¬a\\/b
• Re: Reading in data into array (special case, please see)
  • From: Richard Heathfield
• Re: function name as string
  • From: websnarf
• Re: hash table
  • From: user923005
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: FACTORIAL PROGRAM C99F
  • From: Ben Pfaff
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• hash table
  • From: uday
• Re: function name as string
  • From: limkatkat
• Reading in data into array (special case, please see)
  • From: Rob111b
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: output problem
  • From: Eric Sosman
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: output problem
  • From: Chris Torek
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: function name as string
  • From: Jack Klein
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: C Object System
  • From: CBFalconer
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Joe Wright
• Re: C Object System
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: C Object System
  • From: Mark McIntyre
• Re: C Object System
  • From: Mark McIntyre
• Re: C Object System
  • From: Mark McIntyre
• Re: C Object System
  • From: Mark McIntyre
• Re: C Object System
  • From: Mark McIntyre
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: brain teasers
  • From: Randy Howard
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Mark McIntyre
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Mark McIntyre
• Re: Test Your C Skills - Errors
  • From: Kenneth Brody
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: pete
• Re: C Object System
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: pete
• Re: output problem
  • From: aljaber
• Re: C Object System
  • From: Charlton Wilbur
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Test Your C Skills - Errors
  • From: Walter Roberson
• Re: extern and function prototypes
  • From: Ben Pfaff
• Re: C Object System
  • From: Ben Pfaff
• Re: extern and function prototypes
  • From: quarkLore
• Re: C Object System
  • From: Charlton Wilbur
• Re: Test Your C Skills - Errors
  • From: Richard Heathfield
• Re: Test Your C Skills - Errors
  • From: Eric Sosman
• Re: extern and function prototypes
  • From: jacob navia
• Re: Segmentation Fault....
  • From: jacob navia
• Re: C Object System
  • From: llothar
• Re: Test Your C Skills - Errors
  • From: Sharath
• Re: Test Your C Skills - Errors
  • From: Eric Sosman
• extern and function prototypes
  • From: quarkLore
• Re: Test Your C Skills - Errors
  • From: Sharath
• Re: Test Your C Skills - Errors
  • From: quarkLore
• Re: Test Your C Skills - Errors
  • From: Richard Heathfield
• Re: Test Your C Skills - Errors
  • From: Ben Pfaff
• Test Your C Skills - Errors
  • From: Sharath
• Re: H[y]stery behind the structure name FILE?
  • From: CBFalconer
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kenneth Brody
• Re: postorder traversal of binary search tree without recursion
  • From: Martin Ambuhl
• Re: Initialising a pointer
  • From: Keith Thompson
• Re: function name as string
  • From: CptDondo
• Re: function name as string
  • From: Harald van Dijk
• Re: output problem
  • From: Eric Sosman
• Re: function name as string
  • From: Karl Malbrain
• Re: C Object System
  • From: Kelsey Bjarnason
• function name as string
  • From: CptDondo
• Re: function length
  • From: Giorgos Keramidas
• Re: C Object System C99F
  • From: Richard Heathfield
• Re: C Object System
  • From: jacob navia
• Re: C Object System
  • From: Ben Pfaff
• Re: C Object System
  • From: Richard Tobin
• output problem
  • From: aljaber
• Re: C Object System
  • From: jacob navia
• Re: C Object System
  • From: Ben Pfaff
• Re: [OT] Re: C Object System
  • From: jacob navia
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: C Object System
  • From: llothar
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Charlton Wilbur
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Ed Jensen
• Re: C Object System
  • From: Al Balmer
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: stdazi@xxxxxxxxx
• Re: H[y]stery behind the structure name FILE?
  • From: Suman
• Re: C Object System
  • From: llothar
• Re: Regarding Mark Weiss's Data structures book
  • From: richie
• Re: H[y]stery behind the structure name FILE?
  • From: Richard Tobin
• Re: Initialising a pointer
  • From: lovecreatesbea...@xxxxxxxxx
• Re: Problematic code in K&R
  • From: Gregor H .
• H[y]stery behind the structure name FILE?
  • From: Suman
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• Re: Initialising a pointer
  • From: Chris Dollin
• Re: Initialising a pointer
  • From: Richard Heathfield
• Re: C Object System
  • From: CBFalconer
• Re: Initialising a pointer
  • From: google . bo
• Re: sscanf behavoir
  • From: Eric Sosman
• Re: sscanf behavoir
  • From: mark_bluemel
• Re: Regarding Mark Weiss's Data structures book
  • From: shambhu
• Problematic code in K&R
  • From: Gregor H .
• Re: sscanf behavoir
  • From: Joachim Schmitz
• Re: C Object System
  • From: Ian Collins
• Regarding Mark Weiss's Data structures book
  • From: richie
• Re: FACTORIAL PROGRAM C99F
  • From: Richard Heathfield
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: David Thompson
• Re: C Object System
  • From: jacob navia
• Re: Segmentation Fault....
  • From: David Thompson
• Re: postorder traversal of binary search tree without recursion
  • From: nishit . gupta
• Re: sscanf behavoir
  • From: Gunvant Patil
• Re: FACTORIAL PROGRAM C99F
  • From: Bjørn Augestad
• [OT] Re: C Object System
  • From: Laurent Deniau
• Re: postorder traversal of binary search tree without recursion
  • From: saki
• Re: C Object System
  • From: Ian Collins
• Re: C Object System
  • From: llothar
• Re: C Object System
  • From: Ian Collins
• Re: C Object System
  • From: Laurent Deniau
• Re: C Object System
  • From: Laurent Deniau
• Re: postorder traversal of binary search tree without recursion
  • From: Nick Keighley
• Re: Initialising a pointer
  • From: mail1779205
• Re: Initialising a pointer
  • From: Chris Dollin
• Re: sscanf behavoir
  • From: Joachim Schmitz
• Re: FACTORIAL PROGRAM C99F
  • From: Richard Heathfield
• Re: Initialising a pointer
  • From: Ian Collins
• Re: postorder traversal of binary search tree without recursion
  • From: nishit . gupta
• Re: postorder traversal of binary search tree without recursion
  • From: nishit . gupta
• Re: Initialising a pointer
  • From: Chris Dollin
• Re: sscanf behavoir
  • From: mark_bluemel
• Re: postorder traversal of binary search tree without recursion
  • From: Ian Collins
• Re: FACTORIAL PROGRAM C99F
  • From: Bjørn Augestad
• sscanf behavoir
  • From: Joachim Schmitz
• postorder traversal of binary search tree without recursion
  • From: nishit . gupta
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: CBFalconer
• Re: Initialising a pointer
  • From: Keith Thompson
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: C Object System
  • From: CBFalconer
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Initialising a pointer
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: CBFalconer
• Re: Initialising a pointer
  • From: lovecreatesbea...@xxxxxxxxx
• send pictures to mobile phones
  • From: sms767intro@xxxxxxxxx
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: C Object System
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: pete
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Initialising a pointer
  • From: Old Wolf
• Re: Initialising a pointer
  • From: Jens Thoms Toerring
• Re: Initialising a pointer
  • From: Keith Thompson
• Re: Initialising a pointer
  • From: Ian Collins
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Keith Thompson
• Re: Initialising a pointer
  • From: google . bo
• Re: Initialising a pointer
  • From: Richard Heathfield
• Re: Initialising a pointer
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Initialising a pointer
  • From: mail1779205
• Re: strlen runtime error after call strcpy
  • From: CBFalconer
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: C Object System
  • From: CBFalconer
• Re: [OT] C Object System
  • From: CBFalconer
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: CBFalconer
• Re: how to write in a file
  • From: CBFalconer
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Ian Collins
• Re: strlen runtime error after call strcpy
  • From: Mark McIntyre
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Mark McIntyre
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Mark McIntyre
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: William Ahern
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Ed Jensen
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: 32 or 64 bit processor info in C
  • From: William Ahern
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: strlen runtime error after call strcpy
  • From: Default User
• Re: C Object System
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: to free() or not to free() in lex/yacc
  • From: Richard
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: jacob navia
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: user923005
• Re: C Object System
  • From: jacob navia
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: Stephen Sprunk
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: strlen runtime error after call strcpy
  • From: Clever Monkey
• Re: how to write in a file
  • From: Roland Pibinger
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: atoi query
  • From: Default User
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Default User
• Re: C Object System
  • From: klaushuotari
• Re: strlen runtime error after call strcpy
  • From: Richard Heathfield
• Re: how to write in a file
  • From: Bill Pursell
• Re: strlen runtime error after call strcpy
  • From: Richard Heathfield
• Re: strlen runtime error after call strcpy
  • From: Duke
• strlen runtime error after call strcpy
  • From: Duke
• Re: atoi query
  • From: Richard Heathfield
• Re: gcc 64bit compiler does not offer any speed advantage
  • From: jacob navia
• C Object System
  • From: Laurent Deniau
• Re: segmentation fault: what is it
  • From: Charlton Wilbur
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Clem Clarke
• gcc 64bit compiler does not offer any speed advantage
  • From: llothar
• Re: atoi query
  • From: Flash Gordon
• Re: segmentation fault: what is it
  • From: Joachim Schmitz
• segmentation fault: what is it
  • From: Nagaraj
• Re: strdup + fread = fail?
  • From: Gunvant Patil
• Re: atoi query
  • From: Richard Bos
• atoi query
  • From: ptq2238
• Re: Detab/Entab( a little OT?)
  • From: Thomas Dickey
• Re: Detab/Entab( a little OT?)
  • From: Richard Bos
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: natkw1
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• How? Movable yet? Click here to join!
  • From: blackjay
• Re: how to write in a file
  • From: blackjay
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: how to write in a file
  • From: Roland Pibinger
• Re: array of char pointers
  • From: mdh
• Re: array of char pointers
  • From: Ian Collins
• Re: array of char pointers
  • From: mdh
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: array of char pointers
  • From: mdh
• Re: how to write in a file
  • From: CBFalconer
• Re: how to write in a file
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: array of char pointers
  • From: Martin Ambuhl
• Re: array of char pointers
  • From: Default User
• Re: how to write in a file
  • From: Bill Pursell
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Bill Pursell
• how to write in a file
  • From: sheilly_2k7
• Re: Fast bitwise algorithm
  • From: Thad Smith
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: array of char pointers
  • From: mdh
• Re: array of char pointers
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: array of char pointers
  • From: mdh
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: array of char pointers
  • From: mdh
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: array of char pointers
  • From: Ian Collins
• Re: array of char pointers
  • From: Peter Nilsson
• Re: array of char pointers
  • From: mdh
• Re: # in macro
  • From: Peter Nilsson
• Re: array of char pointers
  • From: Ian Collins
• Re: # in macro
  • From: Peter Nilsson
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• array of char pointers
  • From: mdh
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Facing Problem in Loop
  • From: pete
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kenneth Brody
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: Detab/Entab( a little OT?)
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Kelsey Bjarnason
• Re: Detab/Entab( a little OT?)
  • From: Clever Monkey
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: gw7rib
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: Facing Problem in Loop
  • From: Vijaykumar Dave
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Detab/Entab( a little OT?)
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Detab/Entab( a little OT?)
  • From: Eric Sosman
• Re: Detab/Entab( a little OT?)
  • From: Keith Thompson
• Re: Detab/Entab( a little OT?)
  • From: Bjørn Augestad
• Re: Detab/Entab( a little OT?)
  • From: mdh
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: Detab/Entab( a little OT?)
  • From: Bill Pursell
• Re: Detab/Entab( a little OT?)
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Detab/Entab( a little OT?)
  • From: Richard Heathfield
• Re: Metaphone is driving me crazy !!
  • From: user923005
• Re: Return Value of atoi and strtoul
  • From: Flash Gordon
• Re: Fast bitwise algorithm
  • From: user923005
• Re: strdup + fread = fail?
  • From: CBFalconer
• Re: Detab/Entab( a little OT?)
  • From: Clever Monkey
• Re: # in macro
  • From: Dave Hansen
• Fast bitwise algorithm
  • From: in_tyrannos
• Detab/Entab( a little OT?)
  • From: mdh
• Re: to free() or not to free() in lex/yacc
  • From: Christopher Benson-Manica
• Re: # in macro
  • From: John Bode
• Re: Converting Linux source code to Windows containing signal()
  • From: llothar
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Bos
• Re: 32 or 64 bit processor info in C
  • From: Richard Bos
• Re: # in macro
  • From: Eric Sosman
• Re: strdup + fread = fail?
  • From: Gunvant Patil
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: Eric Sosman
• Confused - suggest parentheses around assignment used as truth value
  • From: natkw1
• Re: Confused - suggest parentheses around assignment used as truth value
  • From: Richard Tobin
• Re: # in macro
  • From: quarkLore
• Re: Running ping
  • From: Richard Bos
• Re: Abusing C/C++ comments
  • From: pete
• Re: Newbie pointers and reversing question
  • From: Nick Keighley
• Re: strdup + fread = fail?
  • From: Richard Tobin
• Re: 32 or 64 bit processor info in C
  • From: Doug
• Re: Running ping
  • From: CBFalconer
• Re: Running ping
  • From: jacob navia
• Re: strdup + fread = fail?
  • From: Richard Heathfield
• strdup + fread = fail?
  • From: loudking
• Re: Abusing C/C++ comments
  • From: Richard Heathfield
• Re: Abusing C/C++ comments
  • From: jaysome
• Re: # in macro
  • From: junjiec
• Re: # in macro
  • From: Peter Nilsson
• # in macro
  • From: junjiec
• Re: problem in Loop
  • From: Eric
• Re: Return Value of atoi and strtoul
  • From: Thad Smith
• Re: Metaphone is driving me crazy !!
  • From: Jack Klein
• preview spiderman 3 for new
  • From: amit
• Re: K&R 5-10
  • From: CBFalconer
• Re: to free() or not to free() in lex/yacc
  • From: CBFalconer
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Mark McIntyre
• Re: How to determine the size of an output buffer
  • From: David Mathog
• Re: K&R 5-10
  • From: mdh
• Re: How to send frame address by MAC
  • From: Clever Monkey
• Re: K&R 5-10
  • From: pete
• Re: How to determine the size of an output buffer
  • From: Chris Torek
• Re: K&R 5-10
  • From: mdh
• Re: K&R 5-10
  • From: pete
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: what is the problem about my makefile
  • From: Kenny McCormack
• Re: to free() or not to free() in lex/yacc
  • From: Berk Birand
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Charlton Wilbur
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings - Off Topic - Philosophy.
  • From: Al Balmer
• Re: to free() or not to free() in lex/yacc
  • From: Berk Birand
• Re: to free() or not to free() in lex/yacc
  • From: Berk Birand
• Re: Newbie pointers and reversing question
  • From: pete
• Re: How to send frame address by MAC
  • From: Walter Roberson
• Re: Metaphone is driving me crazy !!
  • From: Kenny McCormack
• Re: Converting Linux source code to Windows containing signal()
  • From: Clever Monkey
• Re: How to send frame address by MAC
  • From: Clever Monkey
• How to send frame address by MAC
  • From: Jan Koprowski
• Metaphone is driving me crazy !!
  • From: rashpal . sidhu
• Converting Linux source code to Windows containing signal()
  • From: responsible
• Re: Newbie pointers and reversing question
  • From: Scott Fluhrer
• Re: K&R 5-10
  • From: pete
• Re: K&R 5-10
  • From: Bjørn Augestad
• Re: violating procedure calling convention
  • From: Chris Dollin
• Re: K&R 5-10
  • From: pete
• Re: violating procedure calling convention
  • From: KIRAN
• Re: Return Value of atoi and strtoul
  • From: CBFalconer
• Re: to free() or not to free() in lex/yacc
  • From: jacob navia
• Re: To C or not to C, that is the question...
  • From: per9000
• Re: To C or not to C, that is the question...
  • From: Lars Rune Nøstdal
• Re: To C or not to C, that is the question...
  • From: per9000
• Re: DO YOU HAVE ERROR IN PC SCAN AND DOWNLOAD FOR FREE
  • From: Richard Heathfield
• DO YOU HAVE ERROR IN PC SCAN AND DOWNLOAD FOR FREE
  • From: pandiyan.gpandi@xxxxxxxxx
• Re: K&R 5-10
  • From: Bjørn Augestad
• Re: Running ping
  • From: Richard Bos
• Re: what is the problem about my makefile
  • From: Chris Torek
• Re: to free() or not to free() in lex/yacc
  • From: Chris Torek
• Re: Return Value of atoi and strtoul
  • From: Richard Heathfield
• Re: K&R 5-10
  • From: mdh
• Re: K&R 5-10
  • From: Bjørn Augestad
• Return Value of atoi and strtoul
  • From: sachinahuja82
• Re: what is the problem about my makefile
  • From: Bill Pursell
• Re: to free() or not to free() in lex/yacc
  • From: Stephen Sprunk
• K&R 5-10
  • From: mdh
• Re: Abusing C/C++ comments
  • From: Richard Heathfield
• Re: what is the problem about my makefile
  • From: CBFalconer
• Re: to free() or not to free() in lex/yacc
  • From: CBFalconer
• Re: Abusing C/C++ comments
  • From: CBFalconer
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: Mark T
• Re: Newbie pointers and reversing question
  • From: Jack Klein
• Re: Abusing C/C++ comments
  • From: Hapary
• Re: what is the problem about my makefile
  • From: R Smith
• Re: to free() or not to free() in lex/yacc
  • From: Ian Collins
• Re: const non-pointer function parameters
  • From: Peter Nilsson
• Re: what is the problem about my makefile
  • From: Peter Nilsson
• Re: Running ping
  • From: TKowalcz
• what is the problem about my makefile
  • From: dolphin
• Re: to free() or not to free() in lex/yacc
  • From: Ian Collins
• Re: to free() or not to free() in lex/yacc
  • From: Berk Birand
• Re: Newbie pointers and reversing question
  • From: CBFalconer
• to free() or not to free() in lex/yacc
  • From: Berk Birand
• Re: help:question about sizeof?
  • From: Peter Nilsson
• Re: Newbie pointers and reversing question
  • From: Ian Collins
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Ian Collins
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Michael Jarrod
• Re: Facing Problem in Loop
  • From: pete
• Re: problem in Loop
  • From: Jens Thoms Toerring
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: Flash Gordon
• Re: Facing Problem in Loop
  • From: Richard Heathfield
• Re: Facing Problem in Loop
  • From: Flash Gordon
• Re: problem in Loop
  • From: CBFalconer
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: CBFalconer
• Re: Facing Problem in Loop
  • From: CBFalconer
• Re: problem in Loop
  • From: Richard Heathfield
• Re: Facing Problem in Loop
  • From: Vijaykumar Dave
• problem in Loop
  • From: Vijaykumar Dave
• Re: const non-pointer function parameters
  • From: Bill Pursell
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: Richard Heathfield
• Re: Newbie pointers and reversing question
  • From: CBFalconer
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Kelly B
• Re: Newbie pointers and reversing question
  • From: Kelly B
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Kelly B
• Re: Newbie pointers and reversing question
  • From: pete
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: Newbie pointers and reversing question
  • From: Kelly B
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: Newbie pointers and reversing question
  • From: Lew Pitcher
• Re: Newbie pointers and reversing question
  • From: conrad
• Re: Newbie pointers and reversing question
  • From: Harald van Dijk
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: Newbie pointers and reversing question
  • From: Kelly B
• Re: Newbie pointers and reversing question
  • From: CBFalconer
• Re: Newbie pointers and reversing question
  • From: Flash Gordon
• Re: Newbie pointers and reversing question
  • From: Army1987
• Re: Newbie pointers and reversing question
  • From: Jens Thoms Toerring
• Newbie pointers and reversing question
  • From: Michael Jarrod
• Re: Recursive functions
  • From: Army1987
• Re: Recursive functions
  • From: Army1987
• Re: c doubt
  • From: pete
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: Flash Gordon
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• Re: c doubt
  • From: David Thompson
• Re: Is necessary to switch to C++ or some object-oriented language?
  • From: David Thompson
• Re: Recursive functions
  • From: David Thompson
• Re: const non-pointer function parameters
  • From: David Thompson
• Re: problems with dynamic allocation in an ellipses function
  • From: David Thompson
• Re: OT - Re: c compilation
  • From: David Thompson
• Re: system() function and current working directory
  • From: David Thompson
• Re: Is cast between structs safe?
  • From: David Thompson
• Re: "a book on c" Kelly & Pohl (4e)
  • From: David Thompson
• Re: Is C faster than fortran?
  • From: David Thompson
• Re: multiple global variable definitions
  • From: David Thompson
• Re: representations
  • From: David Thompson
• Re: skipping a structure member while initializing
  • From: David Thompson
• Re: modifying the strings pointed to by argv
  • From: David Thompson
• Re: Requesting advice how to clean up C code for validating string represents integer
  • From: David Thompson
• Re: Help me with a class assignment
  • From: David Thompson
• Re: Will this leak memory?
  • From: David Thompson
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings - Off Topic - Philosophy.
  • From: Martin Ambuhl
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings - Off Topic - Philosophy.
  • From: Default User
• Re: Copy a file over TCP socket
  • From: pradqdo
• Re: Fast and Safe C Strings: User friendly C macros to Declare anduse C Strings.
  • From: CBFalconer
• Re: {OT} Fast and Safe C Strings: User friendly C macros to Declare and use C Strings - Off Topic - Philosophy.
  • From: Ian Collins
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings - Off Topic - Philosophy.
  • From: Clem Clarke
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: New site for all C programmers
  • From: August Karlstrom
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Clem Clarke
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Clem Clarke
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Clem Clarke
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Blank verse and style (was: Casting to unsigned char for isupper() and friends)
  • From: pete
• Re: Facing Problem in Loop
  • From: Ian Collins
• Re: Facing Problem in Loop
  • From: Vijaykumar Dave
• [OT] Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Running ping
  • From: jacob navia
• Re: newbie question on scanf( )
  • From: Kellyb
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: To C or not to C, that is the question...
  • From: Malcolm McLean
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Ed Jensen
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: websnarf
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Ed Jensen
• Re: Equivalent malloc with calloc
  • From: Army1987
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: No occurrence founded
  • From: Army1987
• Re: No occurrence founded
  • From: Army1987
• Re: 32 or 64 bit processor info in C
  • From: Army1987
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: To C or not to C, that is the question...
  • From: Rehceb Rotkiv
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: FACTORIAL PROGRAM
  • From: Chris Dollin
• Re: violating procedure calling convention
  • From: Chris Dollin
• Re: 32 or 64 bit processor info in C
  • From: Mark L Pappin
• Re: Copy a file over TCP socket
  • From: SM Ryan
• Re: To C or not to C, that is the question...
  • From: napi
• How to get a forum for my free site?
  • From: apple
• Re: Copy a file over TCP socket
  • From: Stephen Sprunk
• Re: Facing Problem in Loop
  • From: Ian Collins
• Re: Facing Problem in Loop
  • From: Vijaykumar Dave
• Re: To C or not to C, that is the question...
  • From: Keith Thompson
• Re: (OT)Re: To C or not to C, that is the question...
  • From: Ian Collins
• Re: FACTORIAL PROGRAM
  • From: banansol
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: To C or not to C, that is the question...
  • From: banansol
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Barry
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: To C or not to C, that is the question...
  • From: user923005
• Re: Segmentation Fault.... C99F
  • From: Francine . Neary
• Re: To C or not to C, that is the question...
  • From: Barry
• Re: FACTORIAL PROGRAM
  • From: Keith Thompson
• Re: violating procedure calling convention
  • From: Barry
• Re: To C or not to C, that is the question...
  • From: Dave Vandervies
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: To C or not to C, that is the question...
  • From: Barry
• Re: violating procedure calling convention
  • From: Dave Vandervies
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: FACTORIAL PROGRAM
  • From: Gregor H .
• Re: To C or not to C, that is the question...
  • From: Clever Monkey
• (OT)Re: To C or not to C, that is the question...
  • From: Barry
• Re: To C or not to C, that is the question...
  • From: Keith Thompson
• Re: To C or not to C, that is the question...
  • From: Keith Thompson
• Re: Checking if a file exists
  • From: Harald van Dijk
• Re: To C or not to C, that is the question...
  • From: user923005
• Re: Copy a file over TCP socket
  • From: Default User
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: violating procedure calling convention
  • From: Barry
• Re: To C or not to C, that is the question...
  • From: user923005
• Copy a file over TCP socket
  • From: pradqdo
• Re: To C or not to C, that is the question...
  • From: Barry
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: To C or not to C, that is the question...
  • From: Dave Vandervies
• Re: violating procedure calling convention
  • From: Dave Vandervies
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: To C or not to C, that is the question...
  • From: Barry
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Keith Thompson
• Re: FACTORIAL PROGRAM
  • From: Martin Ambuhl
• Re: To C or not to C, that is the question...
  • From: user923005
• Re: FACTORIAL PROGRAM
  • From: Keith Thompson
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: FACTORIAL PROGRAM
  • From: Barry
• Re: To C or not to C, that is the question...
  • From: Barry
• Re: violating procedure calling convention
  • From: Martin Ambuhl
• Re: "data hiding" prototype code
  • From: E. Robert Tisdale
• Re: No occurrence founded
  • From: Barry
• Re: char pointers?
  • From: Default User
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: No occurrence founded
  • From: Army1987
• Re: FACTORIAL PROGRAM
  • From: GeekBoy
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: user923005
• Re: char pointers?
  • From: Flash Gordon
• Re: To C or not to C, that is the question...
  • From: user923005
• Re: char pointers?
  • From: rasztasd@xxxxxxxxx
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Barry
• Re: No occurrence founded
  • From: Army1987
• Re: Checking if a file exists
  • From: Walter Roberson
• Re: Running ping
  • From: Barry
• Re: Segmentation Fault....
  • From: Default User
• Re: Please help with this command
  • From: Default User
• To C or not to C, that is the question...
  • From: Rehceb Rotkiv
• Re: violating procedure calling convention
  • From: Barry
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Default User
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: violating procedure calling convention
  • From: Dave Vandervies
• Re: Segmentation Fault....
  • From: Default User
• Re: Segmentation Fault.... C99F
  • From: Daniel Rudy
• Re: Equivalent malloc with calloc
  • From: Flash Gordon
• Re: [OT] Text-Based Windows Library
  • From: Army1987
• Re: Checking if a file exists
  • From: Kenneth Brody
• Re: Running ping
  • From: Mark
• Re: violating procedure calling convention
  • From: Tak-Shing Chan
• Running ping
  • From: TKowalcz
• Re: trying to use mmap on PC with cygwin.
  • From: Flash Gordon
• Re: Please help with this command
  • From: Flash Gordon
• Re: Abusing C/C++ comments
  • From: Chris Hills
• Re: violating procedure calling convention
  • From: Dave Vandervies
• Re: Abusing C/C++ comments
  • From: Chris Hills
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: Please help with this command
  • From: CBFalconer
• Re: Please help with this command
  • From: Barry Schwarz
• violating procedure calling convention
  • From: KIRAN
• Re: Please help with this command
  • From: Ulrich Eckhardt
• Re: Segmentation Fault....
  • From: Tak-Shing Chan
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Barry Schwarz
• Re: trying to use mmap on PC with cygwin.
  • From: Richard Tobin
• Re: Problem with function pointer in structure
  • From: Chris Torek
• Please help with this command
  • From: choudhary . poorva
• trying to use mmap on PC with cygwin.
  • From: comp.unix.shell
• Re: No reference to stdio.h
  • From: Manuel T
• Re: Reg: #define
  • From: Eric Sosman
• Re: Segmentation Fault....
  • From: army1987
• Re: FACTORIAL PROGRAM
  • From: army1987
• Re: Equivalent malloc with calloc
  • From: army1987
• Re: Hi
  • From: army1987
• Re: Reg: #define
  • From: army1987
• Re: No reference to stdio.h
  • From: army1987
• Re: Accessing files in a zip?
  • From: MikeC
• Re: Accessing files in a zip?
  • From: mark_bluemel
• Accessing files in a zip?
  • From: MikeC
• Re: Merging two AVL treees
  • From: Richard Bos
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Bos
• Re: file reading
  • From: Richard Bos
• Re: parsing text
  • From: Richard Bos
• Re: c doubt
  • From: Richard Bos
• Re: Problem with function pointer in structure
  • From: Duncan Muirhead
• Re: FACTORIAL PROGRAM
  • From: Chris Dollin
• Re: FACTORIAL PROGRAM
  • From: Richard Heathfield
• Merging two AVL treees
  • From: gagan . singh . arora
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Richard Heathfield
• Re: No reference to stdio.h
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: jacob navia
• Fast and Safe C Strings: User friendly C macros to Declare and use C Strings.
  • From: Clem Clarke
• Re: No reference to stdio.h
  • From: Ian Collins
• No reference to stdio.h
  • From: SamG
• Re: [OT] Text-Based Windows Library
  • From: Richard Bos
• Re: Text-Based Windows Library
  • From: Richard Bos
• Re: Segmentation Fault....
  • From: Richard Bos
• Re: help:question about sizeof?
  • From: JimS
• Re: help:question about sizeof?
  • From: shaanxxx
• Re: help:question about sizeof?
  • From: shaanxxx
• Re: Copyright Protection ? Is it really possible ?
  • From: Keith Thompson
• Copyright Protection ? Is it really possible ?
  • From: alertjean
• Re: help:question about sizeof?
  • From: Martin Ambuhl
• Re: help:question about sizeof?
  • From: seni.yin
• Re: Problem with function pointer in structure
  • From: dada
• Re: char pointers?
  • From: Peter Nilsson
• Re: Segmentation Fault....
  • From: Peter Nilsson
• Re: char pointers?
  • From: Chris Torek
• Re: help:question about sizeof?
  • From: Peter Nilsson
• help:question about sizeof?
  • From: guoliang
• Re: fread not reading all information
  • From: red floyd
• Re: Segmentation Fault.... C99F
  • From: Keith Thompson
• Re: parsing text
  • From: CBFalconer
• Re: parsing text
  • From: Doug
• Re: parsing text
  • From: Mark McIntyre
• Re: Segmentation Fault.... C99F
  • From: Mark McIntyre
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: Segmentation Fault.... C99F
  • From: Ian Collins
• Re: Segmentation Fault.... C99F
  • From: user923005
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Problem with function pointer in structure
  • From: Ian Collins
• Re: Facing Problem in Loop
  • From: Kelsey Bjarnason
• Re: Segmentation Fault.... C99F
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Problem with function pointer in structure
  • From: jb . simon
• Re: Segmentation Fault.... C99F
  • From: Francine . Neary
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Facing Problem in Loop
  • From: Old Wolf
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: fread not reading all information
  • From: juleigha27
• Re: Segmentation Fault....
  • From: Francine . Neary
• Re: parsing text
  • From: Default User
• Re: OT: Re: 32 or 64 bit processor info in C
  • From: Kelsey Bjarnason
• Re: Segmentation Fault.... C99F
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Re: Testing setuid()
  • From: Clever Monkey
• Re: Testing setuid()
  • From: Walter Roberson
• Re: Segmentation Fault.... C99F
  • From: Kelsey Bjarnason
• Re: Segmentation Fault....
  • From: Kelsey Bjarnason
• Testing setuid()
  • From: Stu
• Re: "data hiding" prototype code
  • From: sofeng
• Re: newbie question on scanf( )
  • From: CBFalconer
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Flash Gordon
• Re: "data hiding" prototype code
  • From: Jonas
• Re: Redundant return
  • From: William Hughes
• Re: Checking if a file exists
  • From: Harald van Dijk
• Re: Checking if a file exists
  • From: Harald van Dijk
• Re: New site for all C programmers
  • From: Andrew Tyler
• Re: newbie question on scanf( )
  • From: Kelly B
• newbie question on scanf( )
  • From: Kelly B
• Re: Redundant return
  • From: Tak-Shing Chan
• Re: [OT] Text-Based Windows Library
  • From: Tak-Shing Chan
• Re: [OT] Text-Based Windows Library
  • From: Tak-Shing Chan
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: [OT] Text-Based Windows Library
  • From: Charlton Wilbur
• Re: [OT] Text-Based Windows Library
  • From: Clever Monkey
• Re: New site for all C programmers
  • From: Tak-Shing Chan
• Re: Segmentation Fault.... C99F
  • From: Daniel Rudy
• Re: parsing text
  • From: user923005
• Re: [OT] Text-Based Windows Library
  • From: Tak-Shing Chan
• Re: Text-Based Windows Library
  • From: user923005
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Segmentation Fault.... C99F
  • From: Tak-Shing Chan
• Re: "data hiding" prototype code
  • From: sofeng
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: Segmentation Fault.... C99F
  • From: Tak-Shing Chan
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: Text-Based Windows Library
  • From: Chris Johnson
• Re: Segmentation Fault.... C99F
  • From: Tak-Shing Chan
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: parsing text
  • From: Default User
• Re: Segmentation Fault....
  • From: Default User
• Re: Text-Based Windows Library
  • From: Martin Ambuhl
• Re: Segmentation Fault.... C99F
  • From: Tak-Shing Chan
• Re: Segmentation Fault.... C99F
  • From: Charlton Wilbur
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: Segmentation Fault.... C99F
  • From: Gregor H .
• Re: Segmentation Fault.... C99F
  • From: Charlton Wilbur
• Re: Redundant return
  • From: Chris Dollin
• Re: Redundant return
  • From: Chris Dollin
• Re: Redundant return
  • From: Richard Heathfield
• Re: New site for all C programmers
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Text-Based Windows Library
  • From: bytebro
• Re: Redundant return
  • From: William Hughes
• Re: Redundant return
  • From: Chris Dollin
• Re: Redundant return
  • From: bytebro
• Re: New site for all C programmers
  • From: at
• Re: Segmentation Fault.... C99F
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Redundant return
  • From: Richard Heathfield
• Re: Text-Based Windows Library
  • From: SM Ryan
• Re: Redundant return
  • From: William Hughes
• Text-Based Windows Library
  • From: hstagni
• Re: Redundant return
  • From: robertwessel2@xxxxxxxxx
• Redundant return
  • From: quarkLore
• Re: parsing text
  • From: Richard Heathfield
• Re: parsing text
  • From: Richard Tobin
• Re: file reading
  • From: ramyakrishnakumar
• Re: file reading
  • From: Richard Bos
• Re: file reading
  • From: Ian Collins
• Re: parsing text
  • From: Richard Bos
• Re: 32 or 64 bit processor info in C
  • From: Richard Bos
• Re: Segmentation Fault....
  • From: Richard Bos
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Richard Bos
• Re: Checking if a file exists
  • From: Richard Bos
• file reading
  • From: ramyakrishnakumar
• Re: No occurrence founded
  • From: Chris Dollin
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: char pointers?
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: New site for all C programmers
  • From: Richard Heathfield
• Re: No occurrence founded
  • From: B. Augestad
• Re: parsing text
  • From: Richard Heathfield
• Re: parsing text
  • From: Richard Heathfield
• Re: Error in function declaration
  • From: CBFalconer
• Re: char pointers?
  • From: mdh
• Re: char pointers?
  • From: Ian Collins
• Re: char pointers?
  • From: Barry Schwarz
• Re: 32 or 64 bit processor info in C
  • From: christian.bau
• Re: char pointers?
  • From: mdh
• Re: Error in function declaration
  • From: Barry Schwarz
• Re: char pointers?
  • From: Peter Nilsson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: "data hiding" prototype code
  • From: E. Robert Tisdale
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: "data hiding" prototype code
  • From: sofeng
• Re: "data hiding" prototype code
  • From: sofeng
• Re: parsing text
  • From: Richard Tobin
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Default User
• Re: char pointers?
  • From: Default User
• Re: Segmentation Fault....
  • From: Keith Thompson
• Re: "data hiding" prototype code
  • From: Jonas
• Re: char pointers?
  • From: Default User
• Re: Segmentation Fault....
  • From: Old Wolf
• Re: No occurrence founded
  • From: Old Wolf
• Re: char pointers?
  • From: Jonas
• Re: parsing text
  • From: Default User
• Re: char pointers?
  • From: Eric Sosman
• Re: Facing Problem in Loop
  • From: Martin Ambuhl
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: "data hiding" prototype code
  • From: sofeng
• Re: Facing Problem in Loop
  • From: Kelsey Bjarnason
• Re: Very strange bug in C, please help
  • From: Mark L Pappin
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: char pointers?
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: char pointers?
  • From: Walter Roberson
• Re: parsing text
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: parsing text
  • From: Martin Ambuhl
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: Facing Problem in Loop
  • From: Walter Roberson
• char pointers?
  • From: mdh
• Re: Facing Problem in Loop
  • From: Walter Roberson
• Re: parsing text
  • From: Richard Tobin
• Facing Problem in Loop
  • From: Vijaykumar Dave
• Re: "data hiding" prototype code
  • From: jacob navia
• Re: Reg: #define
  • From: Walter Roberson
• Re: No occurrence founded
  • From: Keith Thompson
• Re: Dynamic lists of strings in C
  • From: Default User
• Re: "data hiding" prototype code
  • From: bluejack
• Re: No occurrence founded
  • From: Flash Gordon
• Re: Dynamic lists of strings in C
  • From: Ian Collins
• Re: No occurrence founded
  • From: B. Augestad
• "data hiding" prototype code
  • From: sofeng
• Re: Reg: #define
  • From: saki
• Re: Reg: #define
  • From: Keith Thompson
• Re: parsing text
  • From: user923005
• Re: GSoap
  • From: Default User
• Re: 32 or 64 bit processor info in C
  • From: Martin Ambuhl
• Re: Reg: #define
  • From: Walter Roberson
• Re: brain teasers
  • From: Default User
• Reg: #define
  • From: raghu
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Dynamic lists of strings in C
  • From: Default User
• Re: Segmentation Fault....
  • From: Default User
• Re: No occurrence founded
  • From: Fred Kleinschmidt
• Re: No occurrence founded
  • From: Chris Dollin
• Re: 32 or 64 bit processor info in C
  • From: broeisi
• Re: No occurrence founded
  • From: Eric Sosman
• Re: Segmentation Fault....
  • From: Christopher Benson-Manica
• No occurrence founded
  • From: nick048
• Re: parsing text
  • From: Martin Ambuhl
• Re: parsing text
  • From: Richard Tobin
• Re: Excercise 5-9 (K&R II)
  • From: mdh
• Re: Very strange bug in C, please help
  • From: CBFalconer
• Re: parsing text
  • From: Martin Ambuhl
• GSoap
  • From: simo
• Re: printf get -1 for an unsigned integer
  • From: Martin Ambuhl
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Charlton Wilbur
• Re: Segmentation Fault....
  • From: Charlton Wilbur
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Christopher Benson-Manica
• Re: Very strange bug in C, please help
  • From: Stephen Sprunk
• Re: 32 or 64 bit processor info in C
  • From: Stephen Sprunk
• Re: switch statement in C
  • From: Dave Hansen
• Re: Error in function declaration
  • From: Fred Kleinschmidt
• OT: Re: 32 or 64 bit processor info in C
  • From: Preben Traerup
• Re: Error in function declaration
  • From: Jonas
• Re: strange behaviour from a typedef in loop
  • From: Chris Dollin
• Re: strange behaviour from a typedef in loop
  • From: Richard Tobin
• Error in function declaration
  • From: nick048
• Re: strange behaviour from a typedef in loop
  • From: Richard Heathfield
• strange behaviour from a typedef in loop
  • From: gorbulastic
• Re: 32 or 64 bit processor info in C
  • From: jacob navia
• Re: Very strange bug in C, please help
  • From: Mark L Pappin
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: printf get -1 for an unsigned integer
  • From: lovecreatesbea...@xxxxxxxxx
• Re: Segmentation Fault....
  • From: Charlton Wilbur
• 25% Off Norton Internet Security
  • From: Innycool
• Re: Very strange bug in C, please help
  • From: CBFalconer
• Re: parsing text
  • From: mark_bluemel
• Re: switch statement in C
  • From: Richard Bos
• parsing text
  • From: yang__lee
• Re: printf get -1 for an unsigned integer
  • From: Keith Thompson
• Re: printf get -1 for an unsigned integer
  • From: Richard Heathfield
• Re: printf get -1 for an unsigned integer
  • From: mark_bluemel
• printf get -1 for an unsigned integer
  • From: lovecreatesbeauty@xxxxxxxxx
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Chris Dollin
• Re: Static and Dynamic Linking
  • From: Chris Dollin
• Static and Dynamic Linking
  • From: Rajeshwaran
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: 32 or 64 bit processor info in C
  • From: Jean-Marc Bourguet
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Very strange bug in C, please help
  • From: Richard Heathfield
• Re: Very strange bug in C, please help
  • From: jaysome
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Stephen Sprunk
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Flash Gordon
• Re: Excercise 5-9 (K&R II)
  • From: Chris Torek
• Re: switch statement in C
  • From: CBFalconer
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Vallabha
• Re: is there any equivalent of getche in C on Linux platform??
  • From: Bill Pursell
• Re: Segmentation Fault....
  • From: Bill Pursell
• Re: 32 or 64 bit processor info in C
  • From: robertwessel2@xxxxxxxxx
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: switch statement in C
  • From: koolj96825
• Re: 32 or 64 bit processor info in C
  • From: Keith Thompson
• Re: 32 or 64 bit processor info in C
  • From: Tim Prince
• Re: 32 or 64 bit processor info in C
  • From: robertwessel2@xxxxxxxxx
• Re: c doubt
  • From: user923005
• Re: 32 or 64 bit processor info in C
  • From: CBFalconer
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: switch statement in C
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Abusing C/C++ comments
  • From: Keith Thompson
• Re: Abusing C/C++ comments
  • From: Al Balmer
• Re: Dynamic lists of strings in C
  • From: Al Balmer
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: brain teasers
  • From: Dik T. Winter
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: Abusing C/C++ comments
  • From: Dave Vandervies
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Segmentation Fault....
  • From: jacob navia
• Re: 32 or 64 bit processor info in C
  • From: Old Wolf
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Dynamic lists of strings in C
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Gordon Burditt
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Dynamic lists of strings in C
  • From: Peter Nilsson
• Re: Segmentation Fault....
  • From: Old Wolf
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: jacob navia
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Dynamic lists of strings in C
  • From: Peter Nilsson
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Gregor H .
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: c doubt
  • From: Craig Franck
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Abusing C/C++ comments
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: switch statement in C
  • From: koolj96825
• Re: 32 or 64 bit processor info in C
  • From: jacob navia
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Abusing C/C++ comments
  • From: Al Balmer
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: jacob navia
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Flash Gordon
• Re: Very strange bug in C, please help - TPA
  • From: Default User
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: Segmentation Fault....
  • From: jacob navia
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Abusing C/C++ comments
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Richard Tobin
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: 32 or 64 bit processor info in C
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: 32 or 64 bit processor info in C
  • From: Martin Ambuhl
• Re: Segmentation Fault....
  • From: Mark McIntyre
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Segmentation Fault....
  • From: Army1987
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Very strange bug in C, please help
  • From: VijaKhara
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Very strange bug in C, please help
  • From: Martin Ambuhl
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: 32 or 64 bit processor info in C
  • From: Martin Ambuhl
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: Ian Collins
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Very strange bug in C, please help
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Eric Sosman
• Re: Dynamic lists of strings in C
  • From: Ian Collins
• Very strange bug in C, please help
  • From: VijaKhara
• Re: Incorrect while condition
  • From: SM Ryan
• Re: Segmentation Fault....
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: Martin Ambuhl
• Re: 32 or 64 bit processor info in C
  • From: broeisi
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Excercise 5-9 (K&R II)
  • From: mdh
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: 32 or 64 bit processor info in C
  • From: broeisi
• Re: 32 or 64 bit processor info in C
  • From: Army1987
• Re: Excercise 5-9 (K&R II)
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Malcolm McLean
• Re: Segmentation Fault....
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: Doug
• Re: Checking if a file exists
  • From: Army1987
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Checking if a file exists
  • From: Army1987
• Re: 32 or 64 bit processor info in C
  • From: Flash Gordon
• Re: 32 or 64 bit processor info in C
  • From: broeisi
• Re: Segmentation Fault....
  • From: Clever Monkey
• Re: Segmentation Fault....
  • From: user923005
• Re: 32 or 64 bit processor info in C
  • From: Walter Roberson
• Re: Segmentation Fault....
  • From: Clever Monkey
• 32 or 64 bit processor info in C
  • From: broeisi
• Re: switch statement in C
  • From: Keith Thompson
• Re: Excercise 5-9 (K&R II)
  • From: mdh
• Re: Abusing C/C++ comments
  • From: Keith Thompson
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Excercise 5-9 (K&R II)
  • From: Richard Heathfield
• Re: Excercise 5-9 (K&R II)
  • From: mdh
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Re: Excercise 5-9 (K&R II)
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Segmentation Fault....
  • From: Charlton Wilbur
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Excercise 5-9 (K&R II)
  • From: mdh
• Re: Incorrect while condition
  • From: mike
• Re: Excercise 5-9 (K&R II)
  • From: Richard Heathfield
• Re: Segmentation Fault....
  • From: Richard Heathfield
• Excercise 5-9 (K&R II)
  • From: mdh
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Incorrect while condition
  • From: Ben Bacarisse
• Re: Segmentation Fault....
  • From: Charlton Wilbur
• Re: Incorrect while condition
  • From: Walter Roberson
• Incorrect while condition
  • From: nick048
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Kenneth Brody
• Re: switch statement in C
  • From: Martin Ambuhl
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Segmentation Fault....
  • From: jacob navia
• Re: Dynamic lists of strings in C
  • From: Al Balmer
• Re: Segmentation Fault....
  • From: Nomad.C@xxxxxxxxx
• Re: Segmentation Fault....
  • From: Daniel Rudy
• Re: Segmentation Fault....
  • From: bytebro
• Re: Segmentation Fault....
  • From: Malcolm McLean
• Segmentation Fault....
  • From: Nomad.C@xxxxxxxxx
• Re: quicksort
  • From: Chris Dollin
• quicksort
  • From: aparnakakkar2003
• Re: Abusing C/C++ comments
  • From: adam.wieckowski@xxxxxxxxx
• Re: Dynamic lists of strings in C
  • From: Mark McIntyre
• Re: Reading a key inside a loop
  • From: Mark McIntyre
• Re: B
  • From: Eric Sosman
• Re: is there any equivalent of getche in C on Linux platform??
  • From: John Bode
• Re: Dynamic lists of strings in C
  • From: Richard Bos
• Re: Abusing C/C++ comments
  • From: Ian Collins
• Re: Abusing C/C++ comments
  • From: Richard Bos
• Re: is there any equivalent of getche in C on Linux platform??
  • From: Richard Bos
• Re: Abusing C/C++ comments
  • From: Ian Collins
• Re: Evils of M$ and C++ability
  • From: Richard Bos
• Re: c doubt
  • From: Richard Bos
• Re: Abusing C/C++ comments
  • From: Richard Heathfield
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: B
  • From: vectorizor
• Re: Abusing C/C++ comments
  • From: Keith Thompson
• Re: switch statement in C
  • From: Keith Thompson
• Re: Abusing C/C++ comments
  • From: Malcolm McLean
• Re: Abusing C/C++ comments
  • From: Ian Collins
• Re: switch statement in C
  • From: Ian Collins
• Re: Dynamic lists of strings in C
  • From: Ian Collins
• switch statement in C
  • From: koolj96825
• Re: printf("%hhd",89);
  • From: P.J. Plauger
• Re: Dynamic lists of strings in C
  • From: Ian Collins
• Re: Assuming size_t is unsigned long
  • From: Keith Thompson
• Re: is there any equivalent of getche in C on Linux platform??
  • From: Martin Ambuhl
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: Dynamic lists of strings in C
  • From: Peter Nilsson
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: is there any equivalent of getche in C on Linux platform??
  • From: Richard Heathfield
• Abusing C/C++ comments
  • From: Hapary
• is there any equivalent of getche in C on Linux platform??
  • From: aman
• Re: printf("%hhd",89);
  • From: Keith Thompson
• Re: Address constant expression
  • From: Harald van Dijk
• Re: Assuming size_t is unsigned long
  • From: Harald van Dijk
• Re: Dynamic lists of strings in C
  • From: Peter Nilsson
• Re: Address constant expression
  • From: Old Wolf
• Re: Assuming size_t is unsigned long
  • From: Thad Smith
• Re: Address constant expression
  • From: Richard Heathfield
• Address constant expression
  • From: Old Wolf
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Find Programming Job?
  • From: Cindy
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Gordon Burditt
• Re: Assuming size_t is unsigned long
  • From: Keith Thompson
• Re: printf("%hhd",89);
  • From: P.J. Plauger
• Re: Reading a key inside a loop
  • From: Mark McIntyre
• Re: Reading a key inside a loop
  • From: Mark McIntyre
• Re: Evils of M$ and C++ability
  • From: Mark McIntyre
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Keith Thompson
• Re: problem in unsigned long long
  • From: Keith Thompson
• Re: problem in unsigned long long
  • From: Keith Thompson
• Re: printf("%hhd",89);
  • From: Keith Thompson
• Re: printf("%hhd",89);
  • From: Keith Thompson
• Re: printf("%hhd",89);
  • From: Siddhartha Gandhi
• Re: Assuming size_t is unsigned long
  • From: Old Wolf
• Re: Assuming size_t is unsigned long
  • From: Keith Thompson
• Re: Reading a key inside a loop
  • From: Richard Tobin
• Re: lookup message trying to write to a file
  • From: Richard Tobin
• Re: Header Files in Linux..
  • From: John Bode
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Harald van Dijk
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: B. Augestad
• Re: About ocurrences problem
  • From: Ian Collins
• Re: NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Harald van Dijk
• Re: Roman numeral to Decimal Conversion
  • From: user923005
• Re: Roman numeral to Decimal Conversion
  • From: billbaitsg
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Re: Assuming size_t is unsigned long
  • From: Harald van Dijk
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Re: About ocurrences problem
  • From: Richard Heathfield
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: problem in unsigned long long
  • From: J. J. Farrell
• Re: About ocurrences problem
  • From: Frodo Baggins
• Re: newbie question: whats wrong with my code?
  • From: Giorgos Keramidas
• Re: Assuming size_t is unsigned long
  • From: Harald van Dijk
• Re: problem in unsigned long long
  • From: R Pradeep Chandran
• Re: How to get the size of the array which is an argument of a function? - TPA
  • From: Default User
• Re: Reading a key inside a loop
  • From: Default User
• Re: [OT] Re: I want spam
  • From: Al Balmer
• Re: How to get the size of the array which is an argument of a function?
  • From: CBFalconer
• Re: lookup message trying to write to a file
  • From: Malcolm McLean
• Re: problem in unsigned long long
  • From: Martin Ambuhl
• Re: How to get the size of the array which is an argument of a function?
  • From: Bill Pursell
• Re: lookup message trying to write to a file
  • From: Flash Gordon
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Re: Assuming size_t is unsigned long
  • From: Martin Ambuhl
• lookup message trying to write to a file
  • From: juliatiupsam
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Martin Ambuhl
• Re: problem in unsigned long long
  • From: David Mathog
• Re: Header Files in Linux..
  • From: Kenneth Brody
• Re: problem in unsigned long long
  • From: Stephen Sprunk
• Re: Evils of M$ and C++ability
  • From: Kenneth Brody
• Re: Assuming size_t is unsigned long
  • From: Paulo Matos
• Re: Assuming size_t is unsigned long
  • From: Eric Sosman
• Re: Evils of M$ and C++ability
  • From: Kenneth Brody
• NULL and all-bits-zero (was Re: Equivalent malloc with calloc)
  • From: Kenneth Brody
• Re: Assuming size_t is unsigned long
  • From: Harald van Dijk
• Re: writing to database
  • From: Kenneth Brody
• Re: Roman numeral to Decimal Conversion
  • From: Joachim Schmitz
• Re: About ocurrences problem
  • From: Servé Laurijssen
• Re: Assuming size_t is unsigned long
  • From: Paulo Matos
• Re: problem in unsigned long long
  • From: vadivel . ks
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: lovecreatesbea...@xxxxxxxxx
• Re: problem in unsigned long long
  • From: Lew Pitcher
• problem in unsigned long long
  • From: vadivel . ks
• Re: Assuming size_t is unsigned long
  • From: B. Augestad
• Re: Assuming size_t is unsigned long
  • From: B. Augestad
• printf("%hhd",89);
  • From: Rajesh S R
• Re: Assuming size_t is unsigned long
  • From: B. Augestad
• Re: Assuming size_t is unsigned long
  • From: Eric Sosman
• Re: Roman numeral to Decimal Conversion
  • From: billbaitsg
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Re: Assuming size_t is unsigned long
  • From: B. Augestad
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: Reading a key inside a loop
  • From: Richard Tobin
• Re: Roman numeral to Decimal Conversion
  • From: Joachim Schmitz
• Re: Assuming size_t is unsigned long
  • From: Richard Heathfield
• Assuming size_t is unsigned long
  • From: Paulo Matos
• Re: Roman numeral to Decimal Conversion
  • From: Joachim Schmitz
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Malcolm McLean
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: Jens Thoms Toerring
• Re: Header Files in Linux..
  • From: Richard Heathfield
• Re: Header Files in Linux..
  • From: Jens Thoms Toerring
• Re: (char *) to (const char *) is also dangerous but allowed?
  • From: christian.bau
• Re: About ocurrences problem
  • From: Jens Thoms Toerring
• Re: Header Files in Linux..
  • From: Flash Gordon
• Re: Header Files in Linux..
  • From: Vallabha
• (char *) to (const char *) is also dangerous but allowed?
  • From: lovecreatesbea...@xxxxxxxxx
• Header Files in Linux..
  • From: aman
• Re: Hi
  • From: ramasubramanian.rahul@xxxxxxxxx
• Re: Hi
  • From: Malcolm McLean
• Re: Hi
  • From: Ivar Rosquist
• Re: how to make these warnings disappear?
  • From: pete142
• About ocurrences problem
  • From: nick048
• Re: brain teasers
  • From: Ian Collins
• Re: How to get the size of the array which is an argument of a function?
  • From: bowlderster
• Re: Roman numeral to Decimal Conversion
  • From: Barry Schwarz
• Hi
  • From: fayed
• Twelve Proofs that Muhammad is a True Prophet
  • From: fayed
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: Checking if a file exists
  • From: Richard Heathfield
• Re: how to make these warnings disappear?
  • From: Mike Wahler
• Windows Hacking -> Chat Tools!
  • From: candra
• Windows Hacking -> Destructive Tools!
  • From: candra
• Windows Hacking -> Desktop Tools!
  • From: candra
• Windows Hacking And Security
  • From: candra
• Unix And Linux Hacking And Security
  • From: candra
• PC Hacking - Crypto - Virology - Cracking - Backdoors!
  • From: candra
• Phreaking - The Black Art Of Telephony!
  • From: candra
• Learn What Hackers Know And How Hackers Attack!
  • From: candra
• Become A Master Hacker - Part 7
  • From: candra
• Become A Master Hacker - Part 6
  • From: candra
• Become A Master Hacker - Part 5
  • From: candra
• Become A Master Hacker - Part 4
  • From: candra
• Become A Master Hacker - Part 3
  • From: candra
• Become A Master Hacker - Part 2
  • From: candra
• Become A Master Hacker - Part 1
  • From: candra
• Re: How to get the size of the array which is an argument of a function?
  • From: Jens Thoms Toerring
• Re: How to get the size of the array which is an argument of a function?
  • From: Martin Ambuhl
• Re: How to get the size of the array which is an argument of a function?
  • From: Siddhartha Gandhi
• Roman numeral to Decimal Conversion
  • From: billbaitsg
• Re: Reading a key inside a loop
  • From: Mark McIntyre
• Re: Evils of M$ and C++ability
  • From: jacob navia
• How to get the size of the array which is an argument of a function?
  • From: bowlderster
• Re: Evils of M$ and C++ability
  • From: jacob navia
• Re: Reading a key inside a loop
  • From: Thomas Dickey
• Re: Evils of M$ and C++ability
  • From: Malcolm McLean
• Re: Checking if a file exists
  • From: Barry Schwarz
• Re: Checking if a file exists
  • From: SM Ryan
• Re: array of array of pointers
  • From: Default User
• Re: related to k&R 5.7
  • From: Army1987
• Re: Checking if a file exists
  • From: Richard Heathfield
• Re: C Tutorials
  • From: Keith Thompson
• Re: C Tutorials
  • From: Robert Gamble
• Re: C Tutorials
  • From: B. Augestad
• Re: related to k&R 5.7
  • From: mdh
• Re: related to k&R 5.7
  • From: mdh
• Re: related to k&R 5.7
  • From: Army1987
• Re: related to k&R 5.7
  • From: Army1987
• Re: K&R 5.7
  • From: Chris Torek
• [OT] Re: array of array of pointers
  • From: Eric Sosman
• Re: [OT] Re: I want spam
  • From: Kelsey Bjarnason
• Re: related to k&R 5.7
  • From: Kelsey Bjarnason
• Re: Checking if a file exists
  • From: SM Ryan
• Re: array of array of pointers
  • From: Piotrek
• related to k&R 5.7
  • From: mdh
• K&R 5.7
  • From: mdh
• Re: array of array of pointers
  • From: Piotrek
• Re: array of array of pointers
  • From: Eric Sosman
• Re: array of array of pointers
  • From: Bill Pursell
• array of array of pointers
  • From: Piotrek
• Re: how to make these warnings disappear?
  • From: Eric Sosman
• Re: how to make these warnings disappear?
  • From: Jack Klein
• Re: how to make these warnings disappear?
  • From: pete142
• Re: how to make these warnings disappear?
  • From: Mike Wahler
• how to make these warnings disappear?
  • From: pete142
• Re: Checking if a file exists
  • From: Chris Torek
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: Checking if a file exists
  • From: Keith Thompson
• Re: How to count occurencies in a Structure
  • From: Barry Schwarz
• Re: Evils of M$ and C++ability
  • From: Keith Thompson
• Re: Checking if a file exists
  • From: Army1987
• Re: Recursive functions
  • From: Army1987
• Re: Recursive functions
  • From: Alex
• Re: How to count occurencies in a Structure
  • From: Army1987
• Re: Checking if a file exists
  • From: Army1987
• Re: Recursive functions
  • From: Army1987
• Re: fflush(stdout);
  • From: Army1987
• Re: Checking if a file exists
  • From: Jens Thoms Toerring
• Re: Checking if a file exists
  • From: Richard Heathfield
• Re: Checking if a file exists
  • From: Army1987
• Re: How to count occurencies in a Structure
  • From: Thomas.Chang
• Re: How to count occurencies in a Structure
  • From: Jens Thoms Toerring
• Re: Evils of M$ and C++ability
  • From: Malcolm McLean
• Re: Checking if a file exists
  • From: Army1987
• Re: String Matching
  • From: jaysome
• Computers & Other Accessories Expert Reviews
  • From: felics60
• Re: String Matching
  • From: Richard Heathfield
• Re: How to count occurencies in a Structure
  • From: nick048
• Re: C Tutorials
  • From: B. Augestad
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: Richard Heathfield
• Re: C Tutorials
  • From: Richard Heathfield
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: K&R2, exercise 1-19
  • From: Peter "Shaggy" Haywood
• Re: String Matching
  • From: Mike Wahler
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: Keith Thompson
• Re: String Matching
  • From: CBFalconer
• String Matching
  • From: Kelly B
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: Gordon Burditt
• C Tutorials
  • From: Software Engineer
• Re: fflush(stdout);
  • From: Keith Thompson
• Re: Reading a key inside a loop
  • From: Keith Thompson
• Re: Evils of M$ and C++ability
  • From: Keith Thompson
• Re: Reading a key inside a loop
  • From: Thomas Dickey
• Re: Checking if a file exists
  • From: Eric Sosman
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: Reading a key inside a loop
  • From: Keith Thompson
• Re: Checking if a file exists
  • From: Keith Thompson
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: Evils of M$ and C++ability
  • From: klaushuotari
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: Richard Heathfield
• Re: brain teasers
  • From: Joe Wright
• Re: brain teasers
  • From: Default User
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: Keith Thompson
• Re: brain teasers
  • From: Richard Heathfield
• Re: Is this a qualifier or something else?
  • From: Mike Wahler
• Re: fflush(stdout);
  • From: Mike Wahler
• Re: brain teasers
  • From: Joe Wright
• Re: brain teasers
  • From: Flash Gordon
• Re: brain teasers
  • From: Keith Thompson
• Re: K&R2, exercise 1-19
  • From: Craig Franck
• Re: Recursive functions
  • From: Chris Torek
• Re: c doubt
  • From: Craig Franck
• Re: How to count occurencies in a Structure
  • From: Jens Thoms Toerring
• Re: How to count occurencies in a Structure
  • From: nick048
• Re: fflush(stdout);
  • From: Rajesh S R
• Re: brain teasers
  • From: Richard Heathfield
• Re: fflush(stdout);
  • From: Default User
• Re: fflush(stdout);
  • From: Walter Roberson
• Re: Checking if a file exists
  • From: Daniel Rudy
• Re: brain teasers
  • From: Daniel Rudy
• Re: brain teasers
  • From: Daniel Rudy
• fflush(stdout);
  • From: Rajesh S R
• Re: How to count occurencies in a Structure
  • From: Jens Thoms Toerring
• Re: How to count occurencies in a Structure
  • From: Default User
• Re: [OT] Re: I want spam
  • From: Default User
• How to count occurencies in a Structure
  • From: nick048
• Re: Reading a key inside a loop
  • From: Thomas Dickey
• Re: Recursive functions
  • From: Charlton Wilbur
• Re: Checking if a file exists
  • From: Jens Thoms Toerring
• Re: Checking if a file exists
  • From: Richard Heathfield
• Checking if a file exists
  • From: Army1987
• Re: Recursive functions
  • From: Harald van Dijk
• Re: I want spam
  • From: Richard Heathfield
• [OT] Re: I want spam
  • From: Army1987
• Re: Recursive functions
  • From: Army1987
• Re: K&R2, exercise 1-23
  • From: Jonas
• Re: Recursive functions
  • From: Harald van Dijk
• Re: Evils of M$ and C++ability
  • From: Richard Heathfield
• Re: Recursive functions
  • From: Army1987
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: Richard Heathfield
• Re: Is this a qualifier or something else?
  • From: D.Hering
• Re: K&R2, exercise 1-23
  • From: Barry Schwarz
• Re: K&R2, exercise 1-23
  • From: Barry Schwarz
• Re: K&R2, exercise 1-23
  • From: Barry Schwarz
• Re: K&R2, exercise 1-23
  • From: Barry Schwarz
• Re: Is this a qualifier or something else?
  • From: Zero
• Re: About Assignment
  • From: nick048
• Re: Evils of M$ and C++ability
  • From: Flash Gordon
• Re: K&R2, exercise 1-19
  • From: Barry Schwarz
• Re: brain teasers
  • From: Martin Ambuhl
• Re: Evils of M$ and C++ability
  • From: user923005
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: Bill Pursell
• Re: Is this a qualifier or something else?
  • From: user923005
• Is this a qualifier or something else?
  • From: D.Hering
• Re: About Assignment
  • From: Cong Wang
• Re: brain teasers
  • From: Keith Thompson
• Re: K&R2, exercise 1-23
  • From: arnuld
• About Assignment
  • From: nick048
• Re: K&R2, exercise 1-23
  • From: arnuld
• Re: K&R2, exercise 1-23
  • From: arnuld
• Re: brain teasers
  • From: saki
• Re: c doubt
  • From: mensanator@xxxxxxx
• Re: brain teasers
  • From: Keith Thompson
• Re: K&R2, exercise 1-23
  • From: Thad Smith
• Re: brain teasers
  • From: Richard Heathfield
• Re: synchronizing 3 threads
  • From: CBFalconer
• Re: Converting to ASCII code
  • From: CBFalconer
• Re: magic square~ what should i do
  • From: CBFalconer
• Re: B
  • From: CBFalconer
• Re: EOF from printf
  • From: CBFalconer
• Re: How many algo possible???
  • From: CBFalconer
• Re: expression evaluation doubt!
  • From: CBFalconer
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: CBFalconer
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: CBFalconer
• Re: K&R2, exercise 1-19
  • From: user923005
• Re: brain teasers
  • From: CBFalconer
• Re: What's going on with C Compilers and C99??
  • From: Richard Heathfield
• Re: brain teasers
  • From: CBFalconer
• Re: Equivalent malloc with calloc
  • From: CBFalconer
• Re: What's going on with C Compilers and C99??
  • From: CBFalconer
• Re: writing to database
  • From: Keith Thompson
• Evils of M$ and C++ability
  • From: Malcolm McLean
• Re: Learning C?
  • From: Martin
• Re: writing to database
  • From: Martin Ambuhl
• Re: c doubt
  • From: Craig Franck
• Re: writing to database
  • From: Keith Thompson
• Re: synchronizing 3 threads
  • From: Default User
• Re: c doubt
  • From: Martin Ambuhl
• Re: brain teasers
  • From: Default User
• Re: brain teasers
  • From: Flash Gordon
• Re: c doubt
  • From: Craig Franck
• Re: Reading a key inside a loop
  • From: Keith Thompson
• Re: brain teasers
  • From: Richard Heathfield
• Re: brain teasers
  • From: Stephen Sprunk
• Re: brain teasers
  • From: Richard Heathfield
• Re: K&R2, exercise 1-19
  • From: Richard Heathfield
• Re: brain teasers
  • From: Default User
• Re: synchronizing 3 threads
  • From: Keith Thompson
• Re: brain teasers
  • From: Keith Thompson
• Re: c doubt
  • From: Richard Heathfield
• Re: brain teasers
  • From: Kelsey Bjarnason
• Re: brain teasers
  • From: Keith Thompson
• Re: K&R2, exercise 1-23
  • From: Fred Kleinschmidt
• Re: Converting to ASCII code
  • From: spacecriter \(Bill C\)
• Re: brain teasers
  • From: Chris Torek
• Re: K&R2, exercise 1-23
  • From: arnuld
• Re: Recursive functions
  • From: Charlton Wilbur
• Re: How to access processor registers
  • From: Al Balmer
• Re: K&R2, exercise 1-19
  • From: Jonas
• Re: c doubt
  • From: Stephen Sprunk
• Re: synchronizing 3 threads
  • From: Army1987
• Re: How many algo possible???
  • From: nishit . gupta
• Re: Recursive functions
  • From: Richard Harter
• Re: While not ended
  • From: nick048
• Re: Recursive functions
  • From: ymuntyan
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: synchronizing 3 threads
  • From: Kenny McCormack
• Re: brain teasers
  • From: Richard Heathfield
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: brain teasers
  • From: zebedee
• Re: brain teasers
  • From: zebedee
• Re: K&R2, exercise 1-19
  • From: Jonas
• Re: Recursive functions
  • From: Jean-Marc Bourguet
• Re: K&R2, exercise 1-23
  • From: Jonas
• Re: brain teasers
  • From: Daniel Rudy
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: Recursive functions
  • From: Army1987
• K&R2, exercise 1-23
  • From: arnuld
• Re: Recursive functions
  • From: Charlton Wilbur
• Re: Reading a key inside a loop
  • From: hstagni
• Re: K&R2, exercise 1-19
  • From: Jonas
• Re: brain teasers
  • From: Flash Gordon
• Re: brain teasers
  • From: Richard Heathfield
• Re: synchronizing 3 threads
  • From: jacob navia
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: brain teasers
  • From: Gunvant Patil
• Re: magic square~ what should i do
  • From: Richard Bos
• Re: brain teasers
  • From: Richard Bos
• Re: brain teasers
  • From: Keith Thompson
• Re: K&R2, exercise 1-19
  • From: Jonas
• Re: While not ended
  • From: Jonas
• Re: While not ended
  • From: Richard Heathfield
• Re: brain teasers
  • From: Richard Heathfield
• Re: c doubt
  • From: Richard Heathfield
• Re: While not ended
  • From: Gunvant Patil
• Re: c doubt
  • From: Richard Heathfield
• Re: pointers and array of pointers
  • From: Chris Torek
• While not ended
  • From: nick048
• Re: brain teasers
  • From: Gunvant Patil
• Re: c doubt
  • From: Stephen Sprunk
• Re: brain teasers
  • From: Richard Heathfield
• Re: Creating a DLL
  • From: Richard Heathfield
• Re: c doubt
  • From: Richard Heathfield
• Re: brain teasers
  • From: Richard Heathfield
• Re: c doubt
  • From: Bill Pursell
• Re: B
  • From: Malcolm McLean
• Re: Converting to ASCII code
  • From: Malcolm McLean
• Re: don't understand the "&&" in K&R2 example
  • From: Bill Pursell
• Re: don't understand the "&&" in K&R2 example
  • From: Stephen Sprunk
• Re: c doubt
  • From: Malcolm McLean
• Re: Creating a DLL
  • From: jaysome
• Re: Undefined reference
  • From: Stephen Sprunk
• Re: Difference between for n while
  • From: Gunvant Patil
• Re: Undefined reference
  • From: Daniel Rudy
• Re: How to access processor registers
  • From: Daniel Rudy
• Re: How to access processor registers
  • From: Daniel Rudy
• Re: brain teasers
  • From: Daniel Rudy
• don't understand the "&&" in K&R2 example
  • From: arnuld
• Re: brain teasers
  • From: Daniel Rudy
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: K&R2, exercise 1-19
  • From: arnuld
• Re: c doubt
  • From: Martin Ambuhl
• Re: c doubt
  • From: Martin Ambuhl
• Re: brain teasers
  • From: user923005
• Re: Difference between for n while
  • From: rohitjogya@xxxxxxxxx
• Re: K&R2, exercise 1-19
  • From: user923005
• K&R2, exercise 1-19
  • From: arnuld
• Re: c doubt
  • From: Ian Collins
• Re: The weird while and If
  • From: pete
• Re: Undefined reference
  • From: Barry Schwarz
• Re: c doubt
  • From: Craig Franck
• Re: brain teasers
  • From: Ian Collins
• Re: c doubt
  • From: Craig Franck
• Re: brain teasers
  • From: user923005
• Re: brain teasers
  • From: user923005
• Re: brain teasers
  • From: Ian Collins
• Re: c doubt
  • From: Robert Gamble
• Re: brain teasers
  • From: user923005
• Re: synchronizing 3 threads
  • From: Jack Klein
• Re: c doubt
  • From: Ian Collins
• Re: brain teasers
  • From: Ian Collins
• Re: c doubt
  • From: Craig Franck
• Re: brain teasers
  • From: user923005
• synchronizing 3 threads
  • From: iwasinnihon
• Re: brain teasers
  • From: user923005
• Re: How to access processor registers
  • From: Martin Golding
• Re: brain teasers
  • From: Keith Thompson
• Re: Undefined reference
  • From: wdh3rd
• get your prize
  • From: ourmicro . com
• Re: brain teasers
  • From: user923005
• Re: printf on doubles
  • From: Allin Cottrell
• Re: printf on doubles
  • From: user923005
• Re: brain teasers
  • From: Keith Thompson
• Re: Undefined reference
  • From: Ian Collins
• Re: brain teasers
  • From: Keith Thompson
• Re: Undefined reference
  • From: wdh3rd
• Re: brain teasers
  • From: Keith Thompson
• Re: brain teasers
  • From: Coos Haak
• Re: brain teasers
  • From: Coos Haak
• Re: Noob File IO question
  • From: Barry Schwarz
• Re: expression evaluation doubt!
  • From: Barry Schwarz
• Re: Undefined reference
  • From: Ian Collins
• Re: Recursive functions
  • From: Keith Thompson
• Re: anyone have MetaWare High-C compiler 3.01 ?
  • From: jacob navia
• Re: Undefined reference
  • From: wdh3rd
• Re: brain teasers
  • From: user923005
• Undefined reference
  • From: wdh3rd
• Re: brain teasers
  • From: user923005
• Re: brain teasers
  • From: user923005
• Re: brain teasers
  • From: Ian Collins
• Re: How to access processor registers
  • From: Ian Collins
• Re: brain teasers
  • From: Dave Vandervies
• Re: How to access processor registers
  • From: Daniel Rudy
• Re: brain teasers
  • From: Richard Heathfield
• Re: brain teasers
  • From: Richard Heathfield
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Richard Heathfield
• Re: brain teasers
  • From: Daniel Rudy
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: Reading a key inside a loop
  • From: Flash Gordon
• Re: brain teasers
  • From: Ian Collins
• Re: magic square~ what should i do
  • From: Daniel Rudy
• Re: brain teasers
  • From: Daniel Rudy
• Re: What's going on with C Compilers and C99??
  • From: Default User
• Re: brain teasers
  • From: Ian Collins
• Re: Reading a key inside a loop
  • From: hstagni
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: user923005
• Re: brain teasers
  • From: Daniel Rudy
• Re: Please explain this code to me
  • From: Eric Sosman
• Re: Please explain this code to me
  • From: Ian Collins
• Re: Please explain this code to me
  • From: fred . zakity
• Re: How to find string contains a numeric value
  • From: user923005
• Re: B
  • From: Ian Collins
• Re: Please explain this code to me
  • From: Ian Collins
• Re: Please explain this code to me
  • From: Walter Roberson
• Re: B
  • From: Eric Sosman
• Re: Converting to ASCII code
  • From: Walter Roberson
• Please explain this code to me
  • From: fred . zakity
• Re: cant reove the shift reduce conflict..
  • From: Ian Collins
• LINK
  • From: Sims
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Flash Gordon
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Flash Gordon
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Flash Gordon
• Re: cant reove the shift reduce conflict..
  • From: Coos Haak
• Re: writing to database
  • From: Martin Ambuhl
• Re: brain teasers
  • From: Martin Ambuhl
• Re: brain teasers
  • From: Flash Gordon
• Re: magic square~ what should i do
  • From: Richard Heathfield
• Re: Equivalent malloc with calloc
  • From: Richard Heathfield
• magic square~ what should i do
  • From: jyck91
• B
  • From: vectorizor
• Re: Equivalent malloc with calloc
  • From: B. Augestad
• Re: Recursive functions
  • From: Army1987
• Re: Memory leak when internal pointer passed out as parameter
  • From: Cameron Laird
• Re: Allowed to undef EOF?
  • From: Eric Sosman
• Re: Equivalent malloc with calloc
  • From: Richard Tobin
• Re: How to pass a struct to a function
  • From: Richard Bos
• Re: EOF from printf
  • From: Richard Bos
• Re: Passing by Value
  • From: Richard Heathfield
• Re: expression evaluation doubt!
  • From: Army1987
• Re: How many algo possible???
  • From: Eric Sosman
• Re: c doubt
  • From: U
• Re: cant reove the shift reduce conflict..
  • From: aman
• Re: cant reove the shift reduce conflict..
  • From: Jens Thoms Toerring
• Re: How many algo possible???
  • From: bytebro
• Re: brain teasers
  • From: Army1987
• Re: expression evaluation doubt!
  • From: Ian Collins
• Re: writing to database
  • From: Richard Bos
• Re: Want to ask OCCI
  • From: Ian Collins
• How many algo possible???
  • From: nishit . gupta
• Re: brain teasers
  • From: Richard Bos
• expression evaluation doubt!
  • From: Bhavik
• Want to ask OCCI
  • From: rangga
• Re: brain teasers
  • From: Richard Bos
• Re: writing to database
  • From: childtobe
• Re: cant reove the shift reduce conflict..
  • From: Ian Collins
• Re: writing to database
  • From: Ian Collins
• Re: brain teasers
  • From: Ian Collins
• Re: brain teasers
  • From: Army1987
• Re: brain teasers
  • From: Army1987
• Make a FREE Call Any Where Any Time
  • From: Neelam007
• Re: Equivalent malloc with calloc
  • From: Richard Tobin
• cant reove the shift reduce conflict..
  • From: None
• writing to database
  • From: childtobe
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: arnuld
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: arnuld
• Re: Help with writing codes for routing algorithm
  • From: Nick Keighley
• Re: brain teasers
  • From: Vishesh
• Re: c doubt
  • From: Ian Collins
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: arnuld
• c doubt
  • From: swapna . annamaneni
• Re: Question about read data from a text file.
  • From: Nick Keighley
• Re: Passing by Value
  • From: irwishlaw
• Re: read a file's line into an array, error: makes pointer from integer without a cast
  • From: Ian Collins
• read a file's line into an array, error: makes pointer from integer without a cast
  • From: Kinbote
• Re: brain teasers
  • From: Ian Collins
• Re: wctomb function for AVR
  • From: Keith Thompson
• Re: Memory leak when internal pointer passed out as parameter
  • From: websnarf
• Re: brain teasers
  • From: Richard Heathfield
• Re: Memory leak when internal pointer passed out as parameter
  • From: Daniel Rudy
• Re: brain teasers
  • From: Daniel Rudy
• Re: An interesting C problem
  • From: Old Wolf
• Re: Passing by Value
  • From: Richard Heathfield
• Re: How to find string contains a numeric value
  • From: Old Wolf
• Re: Passing by Value
  • From: Martin Ambuhl
• anyone have MetaWare High-C compiler 3.01 ?
  • From: anuj . goyal
• Re: Passing by Value
  • From: CBFalconer
• printf on doubles
  • From: Allin Cottrell
• Re: Passing by Value
  • From: Richard Heathfield
• Re: Passing by Value
  • From: Richard Heathfield
• Re: Passing by Value
  • From: irwishlaw
• Re: What's going on with C Compilers and C99??
  • From: Richard Heathfield
• Re: Passing by Value
  • From: irwishlaw
• Re: Passing by Value
  • From: Ben Pfaff
• Re: Passing by Value
  • From: Peter Nilsson
• Passing by Value
  • From: irwishlaw
• Re: What's going on with C Compilers and C99??
  • From: Keith Thompson
• Re: wctomb function for AVR
  • From: CBFalconer
• Re: read one line of input from file and then destroying it!
  • From: CBFalconer
• Re: How to find string contains a numeric value
  • From: CBFalconer
• Re: An interesting C problem
  • From: CBFalconer
• Re: Equivalent malloc with calloc
  • From: J. J. Farrell
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Richard Heathfield
• Re: brain teasers
  • From: Richard Heathfield
• Re: What's going on with C Compilers and C99??
  • From: Richard Heathfield
• Re: Allowed to undef EOF?
  • From: Keith Thompson
• Re: Recursive functions
  • From: Richard Heathfield
• Re: K&R2, 1.5.3, exercise 1-9
  • From: Richard Heathfield
• Re: Can you do this? (bit ops)
  • From: Old Wolf
• Re: Recursive functions
  • From: Keith Thompson
• Re: How to find string contains a numeric value
  • From: user923005
• Re: Question about read data from a text file.
  • From: bowlderster
• Re: Question about read data from a text file.
  • From: bowlderster
• Re: Question about read data from a text file.
  • From: Michael
• Allowed to undef EOF?
  • From: Old Wolf
• Re: How to find string contains a numeric value
  • From: Old Wolf
• Re: Recursive functions
  • From: army1987
• Re: Question about read data from a text file.
  • From: Walter Roberson
• Re: Question about read data from a text file.
  • From: Army1987
• Re: Question about read data from a text file.
  • From: Army1987
• Re: brain teasers
  • From: Keith Thompson
• Re: How to find string contains a numeric value
  • From: John Bode
• Re: What's going on with C Compilers and C99??
  • From: Keith Thompson
• Question about read data from a text file.
  • From: bowlderster
• Re: The weird while and If
  • From: Racaille
• Re: Header questions
  • From: Army1987
• Re: brain teasers
  • From: Al Balmer
• Re: brain teasers
  • From: Malcolm McLean
• Re: Help with writing codes for routing algorithm
  • From: Malcolm McLean
• Re: C or Algorithm's
  • From: Malcolm McLean
• Re: simple question
  • From: Malcolm McLean
• Re: The weird while and If
  • From: stremler
• Re: Creating a DLL
  • From: fyderniX
• Re: How to find string contains a numeric value
  • From: user923005
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: user923005
• Re: K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: Flash Gordon
• Re: read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: Reading a key inside a loop
  • From: Army1987
• Re: read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: Reading a key inside a loop
  • From: Army1987
• Re: An interesting C problem
  • From: Army1987
• Re: brain teasers
  • From: Martin Ambuhl
• Re: wctomb function for AVR
  • From: R Pradeep Chandran
• Re: read one line of input from file and then destroying it!
  • From: Default User
• Re: Noob File IO question
  • From: sore eyes
• Re: hey man~
  • From: Default User
• Re: How to find string contains a numeric value - TPA
  • From: Default User
• Re: An interesting C problem
  • From: Army1987
• K&R2 1.6 Arrays, exercise 1-13 (vertical histogram)
  • From: arnuld
• Re: An interesting C problem
  • From: Army1987
• Re: An interesting C problem
  • From: Army1987
• Re: Difference between for n while
  • From: Army1987
• Re: The weird while and If
  • From: Dave Hansen
• Re: K&R2 1.6 Arrays, exercise 1-13
  • From: arnuld
• Re: K&R2 1.6 Arrays, exercise 1-13
  • From: santosh
• Re: Header questions
  • From: Al Balmer
• Re: C or Algorithm's
  • From: santosh
• Re: simple question
  • From: Al Balmer
• Re: C or Algorithm's
  • From: Pierre Asselin
• Re: Is cast between structs safe?
  • From: Eric Sosman
• Re: C or Algorithm's
  • From: arnuld
• wctomb function for AVR
  • From: lorenzvvv
• K&R2 1.6 Arrays, exercise 1-13
  • From: arnuld
• Re: Noob File IO question
  • From: santosh
• Is cast between structs safe?
  • From: lovecreatesbea...@xxxxxxxxx
• Re: read one line of input from file and then destroying it!
  • From: Nick Keighley
• Re: mbtowc - combining character
  • From: Boudewijn Dijkstra
• Re: Header questions
  • From: John Smith
• Re: Noob File IO question
  • From: Ian Malone
• Re: brain teasers
  • From: santosh
• Help with writing codes for routing algorithm
  • From: ricky
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: Tor Rustad
• Re: read one line of input from file and then destroying it!
  • From: santosh
• Re: Can you do this? (bit ops)
  • From: Daniel Rudy
• Re: read one line of input from file and then destroying it!
  • From: santosh
• Re: How to refuse Connections ? [OT]
  • From: Tor Rustad
• Re: read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: Noob File IO question
  • From: sore eyes
• Re: read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: when can realloc fail?
  • From: Eric Sosman
• Re: read one line of input from file and then destroying it!
  • From: santosh
• Re: end in a loop
  • From: santosh
• Re: end in a loop
  • From: santosh
• Re: end in a loop
  • From: nick048
• read one line of input from file and then destroying it!
  • From: waffle . horn
• read one line of input from file and then destroying it!
  • From: waffle . horn
• read one line of input from file and then destroying it!
  • From: waffle . horn
• Re: end in a loop
  • From: santosh
• Re: end in a loop
  • From: Klarth
• Re: Memory leak when internal pointer passed out as parameter
  • From: santosh
• Re: brain teasers
  • From: rohitjogya@xxxxxxxxx
• Re: brain teasers
  • From: Martin Ambuhl
• Re: K&R2, 1.5.3, exercise 1-10
  • From: Ben Bacarisse
• Re: brain teasers
  • From: bytebro
• Re: Can you do this? (bit ops)
  • From: Barry
• Re: brain teasers
  • From: santosh
• Re: portable bit ops
  • From: copx
• brain teasers
  • From: viv342
• Re: Noob File IO question
  • From: santosh
• Re: Noob File IO question
  • From: santosh
• Re: Noob File IO question
  • From: santosh
• Re: K&R2, 1.5.3, exercise 1-10
  • From: Ian Collins
• Re: bit shift and data type of a constant value
  • From: santosh
• Re: bit shift and data type of a constant value
  • From: pete
• Re: What's going on with C Compilers and C99??
  • From: santosh
• Re: Memory leak when internal pointer passed out as parameter
  • From: Daniel Rudy
• Re: K&R2, 1.5.1 example
  • From: santosh
• Can you do this? (bit ops)
  • From: Daniel Rudy
• Re: simple question
  • From: Chris Dollin
• Re: K&R2, 1.5.3, exercise 1-10
  • From: arnuld
• end in a loop
  • From: nick048
• Re: bit shift and data type of a constant value
  • From: Flash Gordon
• Re: Memory leak when internal pointer passed out as parameter
  • From: mark_bluemel
• Re: Memory leak when internal pointer passed out as parameter
  • From: Flash Gordon
• Re: simple question
  • From: MJ_India
• Re: Please
  • From: Sjouke Burry
• Re: K&R2, 1.5.3, exercise 1-10
  • From: Ian Collins
• K&R2, 1.5.3, exercise 1-10
  • From: arnuld
• hey man~
  • From: À̱æ¿ì
• Re: Please
  • From: ÀÓÁ¤¼º
• Re: What's going on with C Compilers and C99??
  • From: Keith Thompson
• Re: bit shift and data type of a constant value
  • From: jacob navia
• bit shift and data type of a constant value
  • From: Felix Kater
• K&R2, 1.5.3, exercise 1-9
  • From: arnuld
• Re: K&R2, 1.5.1 example
  • From: Richard Heathfield
• Re: K&R2, 1.5.1 example
  • From: arnuld
• Re: K&R2, 1.5.1 example
  • From: Richard Heathfield
• K&R2, 1.5.1 example
  • From: arnuld
• Noob File IO question
  • From: sore eyes
• Re: How to find string contains a numeric value
  • From: Old Wolf
• Re: How to find string contains a numeric value
  • From: Martin Ambuhl
• Re: What's going on with C Compilers and C99??
  • From: Keith Thompson
• Re: Header questions
  • From: Bill Pursell
• Re: How to find string contains a numeric value
  • From: nishit . gupta
• Re: How to find string contains a numeric value
  • From: user923005
• Re: How to find string contains a numeric value
  • From: Old Wolf
• How to find string contains a numeric value
  • From: nishit . gupta
• Re: What's going on with C Compilers and C99??
  • From: Ben Pfaff
• Re: What's going on with C Compilers and C99??
  • From: Keith Thompson
• Re: Bush moan
  • From: Peter Nilsson
• Re: mbtowc - combining character
  • From: Harald van Dijk
• Re: Creating a DLL
  • From: jacob navia
• Re: Header questions
  • From: user923005
• Re: mbtowc - combining character
  • From: CBFalconer
• Re: when can realloc fail?
  • From: CBFalconer
• Re: using autocad using C
  • From: Jack Klein
• Re: portable bit ops
  • From: Jack Klein
• Re: A question about sort stable
  • From: user923005
• Re: *p++ = tolower(*p));
  • From: Keith Thompson
• Re: [OT] Bush moan
  • From: Keith Thompson
• Re: mbtowc - combining character
  • From: klaushuotari
• Re: using autocad using C
  • From: Malcolm McLean
• Re: Header questions
  • From: CBFalconer
• mbtowc - combining character
  • From: Old Wolf
• Re: Memory leak when internal pointer passed out as parameter
  • From: Mr John FO Evans
• Re: when can realloc fail?
  • From: Joe Wright
• Re: Memory leak when internal pointer passed out as parameter
  • From: CBFalconer
• Re: simple question
  • From: Al Balmer
• Re: Header questions
  • From: CBFalconer
• Re: simple question
  • From: Richard Heathfield
• Re: Request for naming help
  • From: CBFalconer
• Re: simple question
  • From: Malcolm McLean
• Re: Header questions
  • From: wdh3rd
• Re: Header questions
  • From: wdh3rd
• Re: portable bit ops
  • From: William Ahern
• Re: Header questions
  • From: Al Balmer
• Re: Memory leak when internal pointer passed out as parameter
  • From: Eric Sosman
• Re: Memory leak
  • From: Cameron Laird
• Re: Memory leak when internal pointer passed out as parameter
  • From: Keith Thompson
• Re: portable bit ops
  • From: William Ahern
• Re: Header questions
  • From: Keith Thompson
• Re: Memory leak when internal pointer passed out as parameter
  • From: Ben Pfaff
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: Header questions
  • From: Francine . Neary
• Re: Memory leak when internal pointer passed out as parameter
  • From: Flash Gordon
• Re: Memory leak when internal pointer passed out as parameter
  • From: Walter Roberson
• Re: Memory leak when internal pointer passed out as parameter
  • From: Mike
• Re: Header questions
  • From: Flash Gordon
• Re: Memory leak when internal pointer passed out as parameter
  • From: Walter Roberson
• Re: Memory leak when internal pointer passed out as parameter
  • From: Ben Pfaff
• Re: function length
  • From: August Karlstrom
• Memory leak when internal pointer passed out as parameter
  • From: Mike
• Re: Header questions
  • From: Stephen Sprunk
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: Martin Ambuhl
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: William Hughes
• Re: Header questions
  • From: Kenneth Brody
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: Eric Sosman
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: Kenneth Brody
• Re: Is it a good thing that program mix C and C++?
  • From: John Bode
• Re: dynamic content of a binary file
  • From: santosh
• Re: what does this double conversion mean (unsigned long)(unsigned int)
  • From: Richard Bos
• Re: Header questions
  • From: Lew Pitcher
• Re: dynamic content of a binary file
  • From: bwv539
• Header questions
  • From: wdh3rd
• Re: using autocad using C
  • From: Lew Pitcher
• using autocad using C
  • From: Aman
• Re: Equivalent malloc with calloc
  • From: J. Sommers
• Re: simple question
  • From: Mr John FO Evans
• Re: Equivalent malloc with calloc
  • From: Chris Dollin
• what does this double conversion mean (unsigned long)(unsigned int)
  • From: CFAN
• Re: Is it a good thing that program mix C and C++?
  • From: Chris Hills
• Re: Is it a good thing that program mix C and C++?
  • From: Chris Hills
• Re: portable bit ops
  • From: Nick Keighley
• Re: Equivalent malloc with calloc
  • From: J. Sommers
• Re: The weird while and If
  • From: santosh
• Re: Request for naming help
  • From: santosh
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• portable bit ops
  • From: copx
• Re: Equivalent malloc with calloc
  • From: J. Sommers
• Re: Parameter Passing via a Stack
  • From: Chris Dollin
• Re: An interesting C problem
  • From: Chris Dollin
• Re: Etymology of "struct"
  • From: Chris Torek
• Re: Parameter Passing via a Stack
  • From: Flash Gordon
• Re: int main(void) { return main(); }
  • From: Daniel Rudy
• Re: Increment
  • From: per9000
• Re: Ask an old kerword "entry"
  • From: Lauri Alanko
• Re: simple question
  • From: Richard Heathfield
• Re: Equivalent malloc with calloc
  • From: Richard Heathfield
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: Richard Heathfield
• Re: The weird while and If
  • From: Bill Pursell
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: The weird while and If
  • From: Richard Heathfield
• Re: The weird while and If
  • From: Richard Heathfield
• Request for naming help
  • From: Bill Pursell
• Re: simple question
  • From: Bill Pursell
• Re: simple question
  • From: Ian Collins
• Re: simple question
  • From: Ian Collins
• Re: simple question
  • From: Anthony Irwin
• Re: simple question
  • From: Klarth
• simple question
  • From: viv342
• Re: when can realloc fail?
  • From: pete
• Re: Equivalent malloc with calloc
  • From: CBFalconer
• Re: Equivalent malloc with calloc
  • From: J. J. Farrell
• Re: on italians
  • From: nbaker2328
• Re: pointers and array of pointers
  • From: CBFalconer
• Re: The weird while and If
  • From: pete
• Re: when can realloc fail?
  • From: CBFalconer
• Re: Equivalent malloc with calloc
  • From: pete
• Re: when can realloc fail?
  • From: CBFalconer
• Re: Increment
  • From: CBFalconer
• Re: Parameter Passing via a Stack
  • From: CBFalconer
• Re: Parameter Passing via a Stack
  • From: CBFalconer
• Re: The weird while and If
  • From: Keith Thompson
• Re: The weird while and If
  • From: CBFalconer
• Re: Equivalent malloc with calloc
  • From: CBFalconer
• Re: An interesting C problem
  • From: CBFalconer
• Re: pointers and array of pointers
  • From: Klarth
• Re: Parameter Passing via a Stack
  • From: Gordon Burditt
• Re: Dynamic lists of strings in C
  • From: Peter Nilsson
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: Gordon Burditt
• Re: when can realloc fail?
  • From: Joe Wright
• Re: The weird while and If
  • From: Dave Hansen
• Re: when can realloc fail?
  • From: Joe Wright
• Re: Ask an old kerword "entry"
  • From: Keith Thompson
• Re: Is it a good thing that program mix C and C++?
  • From: Dave Vandervies
• Re: pointers and array of pointers
  • From: Keith Thompson
• Re: pointers and array of pointers
  • From: Keith Thompson
• Re: Ask an old kerword "entry"
  • From: Francine . Neary
• Re: The weird while and If
  • From: Keith Thompson
• Re: Increment
  • From: per9000
• Re: Increment
  • From: Harald van Dijk
• Re: Increment
  • From: Ben Pfaff
• Re: pointers and array of pointers
  • From: Martin Ambuhl
• Increment
  • From: per9000
• Re: pointers and array of pointers
  • From: pete
• Re: pointers and array of pointers
  • From: santosh
• pointers and array of pointers
  • From: Piotrek
• Re: The weird while and If
  • From: Keith Thompson
• Re: The weird while and If
  • From: Richard Heathfield
• Re: The weird while and If
  • From: Dave Hansen
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: The weird while and If
  • From: stremler
• Re: The weird while and If
  • From: Dave Hansen
• Re: Ask an old kerword "entry"
  • From: Martin Ambuhl
• Re: Ask an old kerword "entry"
  • From: Keith Thompson
• Re: Parameter Passing via a Stack
  • From: Keith Thompson
• Re: malloc() and alignment
  • From: Eric Sosman
• Re: Equivalent malloc with calloc
  • From: Default User
• Re: malloc() and alignment
  • From: Francine . Neary
• Re: Parameter Passing via a Stack
  • From: Stephen Sprunk
• Re: ot: omnis class
  • From: Nelu
• ot: omnis class
  • From: dan . gr13
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Re: Equivalent malloc with calloc
  • From: Ben Pfaff
• Re: Equivalent malloc with calloc
  • From: Richard Heathfield
• Re: Equivalent malloc with calloc
  • From: J. Sommers
• Re: Parameter Passing via a Stack
  • From: Walter Roberson
• Re: dynamic content of a binary file
  • From: Clever Monkey
• Re: dynamic content of a binary file
  • From: Walter Roberson
• Re: Is it a good thing that program mix C and C++?
  • From: Kenneth Brody
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: spammenotplui31
• Re: dynamic content of a binary file
  • From: santosh
• Re: Parameter Passing via a Stack
  • From: santosh
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: santosh
• Re: An interesting C problem
  • From: Laurent Deniau
• Re: Equivalent malloc with calloc
  • From: Chris Dollin
• Re: Equivalent malloc with calloc
  • From: ilan pillemer
• Re: A 64-bit binary returning a value to a 32-bit binary?
  • From: spammenotplui31
• Re: Parameter Passing via a Stack
  • From: Thad Smith
• Re: The weird while and If
  • From: Scott
• Re: An interesting C problem
  • From: Barry
• dynamic content of a binary file
  • From: bwv539
• Re: Parameter Passing via a Stack
  • From: mark_bluemel
• Re: An interesting C problem
  • From: Chris Dollin
• Re: An interesting C problem
  • From: Laurent Deniau
• Re: An interesting C problem
  • From: Laurent Deniau
• Re: Reading a key inside a loop
  • From: santosh
• Re: An interesting C problem
  • From: gteddy923@xxxxxxxxx
• Re: The weird while and If
  • From: Chris Dollin
• Re: The weird while and If
  • From: santosh
• Re: Parameter Passing via a Stack
  • From: Keith Thompson
• Re: malloc() and alignment
  • From: Keith Thompson
• Re: How to access processor registers
  • From: santosh
• Re: Difference between for n while
  • From: J. J. Farrell
• Re: Ask an old kerword "entry"
  • From: mark_bluemel
• Re: Parameter Passing via a Stack
  • From: santosh
• Re: Parameter Passing via a Stack
  • From: J. J. Farrell
• Re: [OT] Re: Etymology of "struct"
  • From: Joachim Schmitz
• Ask an old kerword "entry"
  • From: Lung . S . wu
• Re: Parameter Passing via a Stack
  • From: Sharath
• Re: Parameter Passing via a Stack
  • From: Ian Collins
• Re: malloc() and alignment
  • From: Ian Collins
• Re: malloc() and alignment
  • From: Ian Collins
• Re: What's going on with C Compilers and C99??
  • From: Chris Hills
• Parameter Passing via a Stack
  • From: Theo R.
• Re: What's going on with C Compilers and C99??
  • From: Nick Keighley
• Re: malloc() and alignment
  • From: Francine . Neary
• Re: malloc() and alignment
  • From: Francine . Neary
• Re: Reading a key inside a loop
  • From: Keith Thompson
• Re: Difference between for n while
  • From: Richard Heathfield
• Re: The weird while and If
  • From: Richard Heathfield
• Re: Difference between for n while
  • From: rohitjogya@xxxxxxxxx
• Re: Difference between for n while
  • From: rohitjogya@xxxxxxxxx
• Re: Recursive functions
  • From: Keith Thompson
• Re: How to refuse Connections ?
  • From: victor
• Re: Difference between for n while
  • From: Anthony Irwin
• Re: Difference between for n while
  • From: CBFalconer
• Re: Difference between for n while
  • From: Anthony Irwin
• Re: An interesting C problem
  • From: Keith Thompson
• Re: How to refuse Connections ?
  • From: Default User
• Re: when can realloc fail?
  • From: CBFalconer
• Re: How to refuse Connections ?
  • From: Bill Pursell
• Re: How to refuse Connections ?
  • From: Ian Collins
• Re: [OT] Turing completeness of C (was: Perl troll's latest rubbish)
  • From: Keith Thompson
• Difference between for n while
  • From: rohitjogya@xxxxxxxxx
• Re: Recursive functions
  • From: Bill Pursell
• Re: malloc() and alignment
  • From: Keith Thompson
• Re: An interesting C problem
  • From: Keith Thompson
• How to refuse Connections ?
  • From: victor
• Re: Recursive functions
  • From: Keith Thompson
• Re: The weird while and If
  • From: Keith Thompson
• Re: when can realloc fail?
  • From: Nelu
• Re: when can realloc fail?
  • From: pete
• Re: when can realloc fail?
  • From: Nelu
• Re: when can realloc fail?
  • From: pete
• Re: when can realloc fail?
  • From: Nelu
• Re: when can realloc fail?
  • From: pete
• Re: when can realloc fail?
  • From: Eric Sosman
• Re: Reading a key inside a loop
  • From: Old Wolf
• Re: when can realloc fail?
  • From: CBFalconer
• Re: About Union's question
  • From: CBFalconer
• Re: malloc() and alignment
  • From: Eric Sosman
• Re: when can realloc fail?
  • From: Nelu
• Re: About Union's question
  • From: Old Wolf
• Re: Reading a key inside a loop
  • From: Joe Wright
• Re: About Union's question
  • From: Old Wolf
• Re: C++ is complicated and C is bloated.
  • From: Walter Roberson
• Re: when can realloc fail?
  • From: pete
• Re: *p++ = tolower(*p));
  • From: Old Wolf
• Re: malloc() and alignment
  • From: Ian Collins
• [OT] Turing completeness of C (was: Perl troll's latest rubbish)
  • From: Old Wolf
• Re: Dynamic lists of strings in C
  • From: hlubenow
• malloc() and alignment
  • From: Francine . Neary
• Re: Reading a key inside a loop
  • From: Old Wolf
• Re: when can realloc fail?
  • From: Old Wolf
• Re: An interesting C problem
  • From: CBFalconer
• Re: The weird while and If
  • From: CBFalconer
• Re: when can realloc fail?
  • From: Malcolm McLean
• Re: Reading a key inside a loop
  • From: army1987
• Re: when can realloc fail?
  • From: CBFalconer
• Re: int main(void) { return main(); }
  • From: army1987
• Re: Recursive functions
  • From: CBFalconer
• Re: Recursive functions
  • From: army1987
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: Reading a key inside a loop
  • From: Keith Thompson
• Re: The weird while and If
  • From: army1987
• Re: Recursive functions
  • From: Keith Thompson
• Re: An interesting C problem
  • From: army1987
• Re: How to access processor registers
  • From: Ian Collins
• Re: Equivalent malloc with calloc
  • From: Ben Pfaff
• Re: How to access processor registers
  • From: Francine . Neary
• Re: The weird while and If
  • From: Scott
• Re: Etymology of "struct"
  • From: Francine . Neary
• Re: The weird while and If
  • From: Scott
• Re: Equivalent malloc with calloc
  • From: Ian Collins
• Re: The weird while and If
  • From: Scott
• Re: The weird while and If
  • From: Scott
• Re: Equivalent malloc with calloc
  • From: Francine . Neary
• Re: when can realloc fail?
  • From: Barry Schwarz
• Re: Recursive functions
  • From: Bill Pursell
• Re: when can realloc fail?
  • From: banansol
• Re: The weird while and If
  • From: Ian Collins
• Re: The weird while and If
  • From: gw7rib
• Re: The weird while and If
  • From: Spiros Bousbouras
• Re: The weird while and If
  • From: Army1987
• Re: The weird while and If
  • From: Spiros Bousbouras
• Re: The weird while and If
  • From: Army1987
• Re: The weird while and If
  • From: Harald van Dijk
• The weird while and If
  • From: Scott
• Re: when can realloc fail?
  • From: Hallvard B Furuseth
• Re: Recursive functions
  • From: Harald van Dijk
• Re: Recursive functions
  • From: Bill Pursell
• Re: when can realloc fail?
  • From: santosh
• Re: Recursive functions
  • From: Lauri Alanko
• Re: Equivalent malloc with calloc
  • From: Keith Thompson
• Re: An interesting C problem
  • From: Bill Pursell
• Re: Etymology of "struct"
  • From: Gordon Burditt
• Re: when can realloc fail?
  • From: Army1987
• Re: Equivalent malloc with calloc
  • From: Richard Heathfield
• Re: Recursive functions
  • From: Bill Pursell
• Re: question about k&r2
  • From: pete
• Re: when can realloc fail?
  • From: banansol
• Re: when can realloc fail?
  • From: banansol
• Re: when can realloc fail?
  • From: santosh
• Re: when can realloc fail?
  • From: Eric Sosman
• Re: OT - Re: Looking for a *FAST* graphics library More options
  • From: santosh
• Re: Multi-word #define
  • From: Eric Sosman
• Re: Multi-word #define
  • From: Ben Pfaff
• when can realloc fail?
  • From: banansol
• Re: Reading a key inside a loop
  • From: Army1987
• Multi-word #define
  • From: Army1987
• Re: OT - Re: Looking for a *FAST* graphics library More options
  • From: Richard
• Re: [OT] Re: Etymology of "struct"
  • From: Richard
• Re: C++ is complicated and C is bloated.
  • From: Default User
• Re: Recursive functions
  • From: Default User
• Re: C++ is complicated and C is bloated.
  • From: santosh
• Re: Recursive functions
  • From: Richard
• Re: Equivalent malloc with calloc
  • From: santosh
• Re: Guessing program that compressed file (was: bzip2, unicode+0097, finances, sue spammers ...)
  • From: santosh
• Re: Guessing program that compressed file (was: bzip2, unicode+0097, finances, sue spammers ...)
  • From: Richard Heathfield
• Re: Equivalent malloc with calloc
  • From: Harald van Dijk
• Equivalent malloc with calloc
  • From: lovecreatesbea...@xxxxxxxxx
• Guessing program that compressed file (was: bzip2, unicode+0097, finances, sue spammers ...)
  • From: Robert Maas, see http://tinyurl.com/uh3t
• Re: Dynamic lists of strings in C
  • From: hlubenow
• Re: Reading a key inside a loop
  • From: ais523
• Re: C++ is complicated and C is bloated.
  • From: ais523
• Re: sizeof dataTypes at run time
  • From: ilan pillemer
• Re: An interesting C problem
  • From: Army1987
• Re: Reading a key inside a loop
  • From: Army1987
• Re: An interesting C problem
  • From: Barry
• Re: An interesting C problem
  • From: Army1987
• Re: An interesting C problem
  • From: Army1987
• Re: An interesting C problem
  • From: Lauri Alanko
• Re: An interesting C problem
  • From: Malcolm McLean
• Re: An interesting C problem
  • From: Richard Heathfield
• Re: Recursive functions
  • From: Harald van Dijk
• Re: Dynamic lists of strings in C
  • From: Richard Heathfield
• Re: [OT] Re: Etymology of "struct"
  • From: Joachim Schmitz
• Re: Learning C?
  • From: Flash Gordon
• Re: An interesting C problem
  • From: santosh
• Re: An interesting C problem
  • From: Army1987
• Re: Windows and Linux
  • From: verdverm
• An interesting C problem
  • From: gteddy923@xxxxxxxxx
• Re: Dynamic lists of strings in C
  • From: santosh
• Re: How to access processor registers
  • From: santosh
• Re: Recursive functions
  • From: Bill Pursell
• Re: Dynamic lists of strings in C
  • From: Malcolm McLean
• Re: How to access processor registers
  • From: dspfun
• Re: K&R2 Ex1-14
  • From: Malcolm McLean
• Re: Etymology of "struct"
  • From: J. J. Farrell
• Re: obfuscating C executable
  • From: J. J. Farrell
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Spiros Bousbouras
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: J. J. Farrell
• Re: Reading a key inside a loop
  • From: Harald van Dijk
• Re: obfuscating C executable
  • From: Ian Collins
• obfuscating C executable
  • From: Anthony Rossi
• Re: K&R2 Ex1-14
  • From: Richard Heathfield
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Spiros Bousbouras
• Re: Man pages and standards (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Richard Heathfield
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Richard Heathfield
• Re: bzip2, unicode+0097, finances, sue spammers (was: Various C standards/documents ...)
  • From: Richard Heathfield
• Re: sizeof dataTypes at run time
  • From: Richard Heathfield
• Re: Reading a key inside a loop
  • From: Richard Heathfield
• Re: K&R2 Ex1-14
  • From: Barry Schwarz
• Re: Man pages and standards (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: CBFalconer
• Re: Recursive functions
  • From: Barry Schwarz
• K&R2 Ex1-14
  • From: ilan pillemer
• Re: Recursive functions
  • From: Martin Ambuhl
• Re: VonNeumann/Harvard architecture (was: Places=lvalues and <ot>Pop11</ot>)
  • From: Keith Thompson
• Recursive functions
  • From: Harry
• Re: sizeof dataTypes at run time
  • From: ilan pillemer
• Re: VonNeumann/Harvard architecture (was: Places=lvalues and <ot>Pop11</ot>)
  • From: SM Ryan
• Re: Nitpicking over how a disabled low-income person copes (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Default User
• Re: Reading a key inside a loop
  • From: Default User
• Re: VonNeumann/Harvard architecture (was: Places=lvalues and <ot>Pop11</ot>)
  • From: Keith Thompson
• Re: bzip2, unicode+0097, finances, sue spammers (was: Various C standards/documents ...)
  • From: Keith Thompson
• Re: Nitpicking over how a disabled low-income person copes (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Keith Thompson
• Re: Etymology of "struct"
  • From: Keith Thompson
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Luís Oliveira
• Re: Man pages and standards (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Robert Maas, see http://tinyurl.com/uh3t
• Re: How to access processor registers
  • From: CBFalconer
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Robert Maas, see http://tinyurl.com/uh3t
• Re: bzip2 (was months ago: Requesting advice how to clean up C code for validating string represents integer
  • From: Robert Maas, see http://tinyurl.com/uh3t
• VonNeumann/Harvard architecture (was: Places=lvalues and <ot>Pop11</ot>)
  • From: Robert Maas, see http://tinyurl.com/uh3t
• Re: how to quit
  • From: Thomas Dickey
• Re: How to access processor registers
  • From: Thad Smith
• Re: Learning C?
  • From: Ian Collins
• Re: Nitpicking over how a disabled low-income person copes (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Flash Gordon
• Re: Nitpicking over how a disabled low-income person copes (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Spiros Bousbouras
• Nitpicking over how a disabled low-income person copes (was months ago: Requesting advice how to clean up C code for validating string represents integer)
  • From: Robert Maas, see http://tinyurl.com/uh3t
• Re: Learning C?
  • From: Flash Gordon
• Re: Etymology of "struct"
  • From: Dave Vandervies
• Re: *p++ = tolower(*p));
  • From: Dave Vandervies
• attn: aloisia - very fulfilling fast downloads - uchi - (1/1)
  • From: nil
• Re: sizeof dataTypes at run time
  • From: Keith Thompson
• Re: Etymology of "struct"
  • From: Keith Thompson
• Re: sizeof dataTypes at run time
  • From: Ben Pfaff
• Re: Learning C?
  • From: Ian Collins
• Re: About Union's question
  • From: Robert Gamble
• Re: sizeof dataTypes at run time
  • From: ilan pillemer
• Re: How to access processor registers
  • From: Flash Gordon
• Re: Reading a key inside a loop
  • From: ilan pillemer
• Re: How to access processor registers
  • From: Ben Pfaff
• Re: Etymology of "struct"
  • From: Francine . Neary
• Re: How to access processor registers
  • From: Ian Collins
• How to access processor registers
  • From: dspfun
• Re: Etymology of "struct"
  • From: Bill Leary
• Re: Learning C?
  • From: Flash Gordon
• Re: About Union's question
  • From: CBFalconer