comp.lang.c

• Thread Index

---

• Re: Choosing function parameter types - pointers or objects?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Ian Collins
• Re: BOMDAS Vs BODMAS
  • From: Keith Thompson
• Re: C sucks at math? (help)
  • From: Flash Gordon
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: C sucks at math? (help)
  • From: Keith Thompson
• Re: void vs void* (philosophical question)
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Mark McIntyre
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: Choosing function parameter types - pointers or objects?
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Mark McIntyre
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Keith Thompson
• Re: Order of execution
  • From: Mark McIntyre
• Re: So what Standard are we working off?
  • From: Ben Pfaff
• Re: So what Standard are we working off?
  • From: Joe Wright
• Re: void vs void* (philosophical question)
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Ben Pfaff
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: C sucks at math? (help)
  • From: Malcolm
• Re: OT: Good introduction to CPU/Memory terms
  • From: Joe Wright
• Re: Need to implement strdup, strnicmp and stricmp
  • From: pete
• Re: doubts
  • From: Malcolm
• Re: Application Reading Itself
  • From: Malcolm
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Al Balmer
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: void vs void* (philosophical question)
  • From: Chris Torek
• Re: Problems with typedef
  • From: Chris Torek
• Re: Linked list, no out put,help
  • From: D. Power
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Richard Heathfield
• Re: Choosing function parameter types - pointers or objects?
  • From: Frederick Gotham
• Re: Choosing function parameter types - pointers or objects?
  • From: Richard Heathfield
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Walter Roberson
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Joe Wright
• Re: void vs void* (philosophical question)
  • From: Kenneth Brody
• Re: String Character Conversion
  • From: Jayson Davis
• Re: Scope of specifier extern
  • From: Chris Torek
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Choosing function parameter types - pointers or objects?
  • From: ballpointpenthief
• Re: redefine a function with a same name
  • From: Tom Rauschenbach
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: void vs void* (philosophical question)
  • From: Chris Torek
• Re: Application Reading Itself
  • From: Ed Prochak
• Re: So what Standard are we working off?
  • From: Walter Banks
• Re: Binary storage of string constants
  • From: Keith Thompson
• Re: Where can I learn about Multithreading for C
  • From: G4M3 C0D3R
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Chris Torek
• Re: Joining 2 char to 1 short
  • From: Keith Thompson
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Default User
• Application Reading Itself
  • From: ReaperUnreal
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Walter Roberson
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Ben Pfaff
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: String Character Conversion
  • From: Eric Sosman
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Andrew Poelstra
• Re: Need help to save strings from a file to a structure
  • From: Andrew Poelstra
• Re: String Character Conversion
  • From: Jack Klein
• Re: Safe use of unions
  • From: Jack Klein
• Re: String Character Conversion
  • From: Jayson Davis
• Re: So what Standard are we working off?
  • From: Al Balmer
• Re: String Character Conversion
  • From: Eric Sosman
• Re: So what Standard are we working off?
  • From: Al Balmer
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Al Balmer
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: So what Standard are we working off?
  • From: Keith Thompson
• String Character Conversion
  • From: Jayson Davis
• Re: Order of execution
  • From: Kenneth Brody
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: same name global variable multi-files
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: santosh
• Re: new/delete
  • From: Richard Heathfield
• Re: new/delete
  • From: John Bode
• same name global variable multi-files
  • From: quickcur
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Richard Heathfield
• Re: new/delete
  • From: Giannis Papadopoulos
• Re: new/delete
  • From: Thomas J. Gritzan
• Re: void vs void* (philosophical question)
  • From: Thomas J. Gritzan
• Safe use of unions
  • From: dingoatemydonut
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Kenneth Brody
• new/delete
  • From: c language
• Printing string constants
  • From: Ross
• Re: So what Standard are we working off?
  • From: lovecreatesbeauty
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: Joining 2 char to 1 short
  • From: Frederick Gotham
• Re: Binary storage of string constants
  • From: Ross
• Re: Joining 2 char to 1 short
  • From: pete
• Re: So what Standard are we working off?
  • From: lovecreatesbeauty
• Re: Need to implement strdup, strnicmp and stricmp
  • From: SM Ryan
• Re: [OT]Good introduction to CPU/Memory terms
  • From: Morris Dovey
• Re: So what Standard are we working off?
  • From: Roberto Waltman
• Re: So what Standard are we working off?
  • From: Tom St Denis
• Re: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: So what Standard are we working off?
  • From: Roberto Waltman
• Re: Joining 2 char to 1 short
  • From: Tom St Denis
• Re: Joining 2 char to 1 short
  • From: Frederick Gotham
• Re: Joining 2 char to 1 short
  • From: Frederick Gotham
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Morris Dovey
• Re: So what Standard are we working off?
  • From: Harald van Dijk
• Re: C Pointer problem
  • From: goose
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: qsort() results: implementation dependent?
  • From: Max
• Re: Scope of specifier extern
  • From: Tom St Denis
• Re: Order of execution
  • From: Chris Hills
• Re: Time compatibility issue between Java and C
  • From: Nelu
• Re: Extending snprintf() - how to modify va_list?
  • From: A. Farber
• Re: void vs void* (philosophical question)
  • From: Harald van Dijk
• Re: Scope of specifier extern
  • From: pete
• Re: Joining 2 char to 1 short
  • From: pete
• Re: Linked list, no out put,help
  • From: pete
• Re: Scope of specifier extern
  • From: Christian Christmann
• Re: Scope of specifier extern
  • From: Tom St Denis
• Re: Scope of specifier extern
  • From: pete
• Re: Linked list, no out put,help
  • From: asm_fool
• Re: Joining 2 char to 1 short
  • From: "Nils O. Selåsdal"
• Re: Linked list, no out put,help
  • From: pete
• Re: Linked list, no out put,help
  • From: pete
• Re: Linked list, no out put,help
  • From: Alf P. Steinbach
• Scope of specifier extern
  • From: Christian Christmann
• Re: void vs void* (philosophical question)
  • From: pete
• Linked list, no out put,help
  • From: asm_fool
• Re: Joining 2 char to 1 short
  • From: Sven Fülster
• Re: Joining 2 char to 1 short
  • From: pete
• Re: So what Standard are we working off?
  • From: Harald van Dijk
• Re: Joining 2 char to 1 short
  • From: Chris Dollin
• Re: void vs void* (philosophical question)
  • From: Ben C
• Re: So what Standard are we working off?
  • From: pete
• Re: Joining 2 char to 1 short
  • From: Steffen Loringer
• Re: void vs void* (philosophical question)
  • From: Ian Malone
• Re: void vs void* (philosophical question)
  • From: Richard Heathfield
• Re: void vs void* (philosophical question)
  • From: Giannis Papadopoulos
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: Binary storage of string constants
  • From: Ross
• Re: void vs void* (philosophical question)
  • From: Mark F. Haigh
• Re: Binary storage of string constants
  • From: Ross
• Re: OT: Good introduction to CPU/Memory terms
  • From: Chris Dollin
• Re: automated coding standard validation?
  • From: Richard Bos
• void vs void* (philosophical question)
  • From: Giannis Papadopoulos
• Re: OT: Good introduction to CPU/Memory terms
  • From: Mark F. Haigh
• Re: So what Standard are we working off?
  • From: Richard Bos
• Re: So what Standard are we working off?
  • From: Mark F. Haigh
• Re: OT: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: Joining 2 char to 1 short
  • From: Richard Bos
• Re: So what Standard are we working off?
  • From: santosh
• Re: Using size_t clearly (appropriately?)
  • From: Mark F. Haigh
• Joining 2 char to 1 short
  • From: Steffen Loringer
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: doubts
  • From: Richard Heathfield
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Richard Bos
• Re: So what Standard are we working off?
  • From: Richard Heathfield
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Richard Bos
• Re: doubts
  • From: santosh
• Re: Using size_t clearly (appropriately?)
  • From: Mark F. Haigh
• Re: So what Standard are we working off?
  • From: Suman
• Re: So what Standard are we working off?
  • From: santosh
• Re: doubts
  • From: Suman
• Re: BOMDAS Vs BODMAS
  • From: Chris Dollin
• Re: So what Standard are we working off?
  • From: lovecreatesbeauty
• Re: Need help to save strings from a file to a structure
  • From: Dadio
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Chris Dollin
• Re: Problems with typedef
  • From: Ian Bush
• Re: Order of execution
  • From: Keith Thompson
• Re: Casting nonscalar to the same type.
  • From: crook
• Re: Problems with typedef
  • From: Harald van Dijk
• doubts
  • From: ran
• Re: Order of execution
  • From: divyank.rastogi@xxxxxxxxx
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Ian Collins
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Andrew Poelstra
• Re: Value Bits Vs Object Bits
  • From: Michael Mair
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: Time compatibility issue between Java and C
  • From: Walter Roberson
• Re: So what Standard are we working off?
  • From: Ben Pfaff
• Re: Thanks again! [Was: Warning on assigning...]
  • From: I . M . !Knuth
• Time compatibility issue between Java and C
  • From: Adi
• Re: So what Standard are we working off?
  • From: Rouben Rostamian
• Re: So what Standard are we working off?
  • From: Peter Nilsson
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: Problems with typedef
  • From: pete
• Re: So what Standard are we working off?
  • From: pete
• Re: Order of execution
  • From: Roberto Waltman
• Re: So what Standard are we working off?
  • From: pete
• Re: So what Standard are we working off?
  • From: Ben Pfaff
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: So what Standard are we working off?
  • From: Frederick Gotham
• Re: So what Standard are we working off?
  • From: pete
• Re: So what Standard are we working off?
  • From: Keith Thompson
• Re: Value Bits Vs Object Bits
  • From: Frederick Gotham
• Re: Need to implement strdup, strnicmp and stricmp
  • From: pete
• Re: So what Standard are we working off?
  • From: santosh
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Barry Schwarz
• Re: [OT] Good introduction to CPU/Memory terms
  • From: Morris Dovey
• Re: So what Standard are we working off?
  • From: Sjouke Burry
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Tom Plunket
• Re: Function Pointers
  • From: Tom Plunket
• So what Standard are we working off?
  • From: Frederick Gotham
• Re: Need help to save strings from a file to a structure
  • From: Morris Dovey
• Re: #warning preprocessor command
  • From: ddehterov
• Re: Order of execution
  • From: Richard Heathfield
• Re: 64 bit portability, size_t, and printf format strings
  • From: Simon Biber
• Re: C Pointer problem
  • From: Simon Biber
• Re: Problems with typedef
  • From: John Smith
• Re: A few English terms [was Okay to move an "object" will-nilly?]
  • From: Thomas J. Gritzan
• Re: Order of execution
  • From: Robert Gamble
• Re: OT: Good introduction to CPU/Memory terms
  • From: Flash Gordon
• Re: Casting nonscalar to the same type.
  • From: pete
• Re: OT: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: Order of execution
  • From: Chris Hills
• Re: OT: Good introduction to CPU/Memory terms
  • From: pete
• Re: #warning preprocessor command
  • From: Keith Thompson
• Re: BOMDAS Vs BODMAS
  • From: Keith Thompson
• Re: OT: Good introduction to CPU/Memory terms
  • From: Ian Collins
• Re: #warning preprocessor command
  • From: Skarmander
• Re: Need to implement strdup, strnicmp and stricmp
  • From: pete
• Re: OT: Good introduction to CPU/Memory terms
  • From: Robert Gamble
• Re: #warning preprocessor command
  • From: Keith Thompson
• Re: OT: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: OT: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: Function Pointers
  • From: Al Balmer
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Eric Sosman
• Re: OT: Good introduction to CPU/Memory terms
  • From: Skarmander
• Re: BOMDAS Vs BODMAS
  • From: Robert Gamble
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Chris Torek
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: 64 bit portability, size_t, and printf format strings
  • From: Skarmander
• Re: 64 bit portability, size_t, and printf format strings
  • From: Skarmander
• Re: #warning preprocessor command
  • From: Robert Gamble
• Re: Problems with typedef
  • From: Chris Torek
• Re: Working with negative numbers
  • From: Keith Thompson
• Re: #warning preprocessor command
  • From: Keith Thompson
• Re: Casting nonscalar to the same type.
  • From: Keith Thompson
• Re: Function Pointers
  • From: Ben C
• Re: #warning preprocessor command
  • From: Robert Gamble
• Re: OT: Good introduction to CPU/Memory terms
  • From: santosh
• Re: Working with negative numbers
  • From: Mark McIntyre
• Re: OT: Good introduction to CPU/Memory terms
  • From: Robert Gamble
• Re: OT: Good introduction to CPU/Memory terms
  • From: Richard Heathfield
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Robert Gamble
• Re: Need help to save strings from a file to a structure
  • From: Clever Monkey
• #warning preprocessor command
  • From: ddehterov
• Re: Need help to save strings from a file to a structure
  • From: Dadio
• Re: Casting nonscalar to the same type.
  • From: Eric Sosman
• Re: extern keyword
  • From: Frederick Gotham
• OT: Good introduction to CPU/Memory terms
  • From: Seeker
• Re: Casting nonscalar to the same type.
  • From: Ben Pfaff
• Re: Casting nonscalar to the same type.
  • From: Richard Heathfield
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Flash Gordon
• Casting nonscalar to the same type.
  • From: crook
• Re: Using size_t clearly (appropriately?)
  • From: Al Balmer
• Re: Array elements
  • From: Keith Thompson
• Re: hi friends
  • From: Joe Van Dyk
• Re: Order of execution
  • From: Richard Heathfield
• Re: 64 bit portability, size_t, and printf format strings
  • From: Jack Klein
• Re: Dialectal Idiosyncrasies
  • From: Frederick Gotham
• Re: Take and return pointer to function
  • From: Frederick Gotham
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Flash Gordon
• Re: Using size_t clearly (appropriately?)
  • From: Keith Thompson
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Robert Gamble
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Robert Gamble
• Re: Binary storage of string constants
  • From: Skarmander
• Re: Order of execution
  • From: Chris Hills
• Re: About header files
  • From: Eric Sosman
• Re: About header files
  • From: Robert Gamble
• Re: Order of execution
  • From: Chris Hills
• Re: About header files
  • From: Christoph Scholtes
• Re: Need to implement strdup, strnicmp and stricmp
  • From: pete
• Re: Dialectal Idiosyncrasies
  • From: Al Balmer
• Re: Using size_t clearly (appropriately?)
  • From: pete
• Re: Function Pointers
  • From: Roberto Waltman
• Re: fgetc
  • From: Morris Dovey
• Re: Using size_t clearly (appropriately?)
  • From: Al Balmer
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Kenneth Brody
• Re: Take and return pointer to function
  • From: Kenneth Brody
• Re: Using size_t clearly (appropriately?)
  • From: Ben Pfaff
• Re: Order of execution
  • From: Kenneth Brody
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Morris Dovey
• Re: fgetc
  • From: Herbert Rosenau
• Re: Need to implement strdup, strnicmp and stricmp
  • From: pete
• Re: Problems with typedef
  • From: pete
• Re: Take and return pointer to function
  • From: Frederick Gotham
• Re: About header files
  • From: Richard Heathfield
• Re: which is faster?
  • From: pete
• About header files
  • From: Christoph Scholtes
• Re: 64 bit portability, size_t, and printf format strings
  • From: Eric Sosman
• Re: Array elements
  • From: santosh
• Re: Array elements
  • From: pete
• Re: Function Pointers
  • From: Clever Monkey
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Robert Gamble
• Re: OT: Windows console programs (was Re: Function Pointers)
  • From: Richard Heathfield
• Take and return pointer to function
  • From: Frederick Gotham
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Richard Heathfield
• Re: Order of execution
  • From: Richard Heathfield
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Roberto Waltman
• Re: Function Pointers
  • From: Ben C
• 64 bit portability, size_t, and printf format strings
  • From: dank
• Re: Need help to save strings from a file to a structure
  • From: Dadio
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Frederick Gotham
• Re: economizing with functions that do the same thing
  • From: Default User
• Re: Using size_t clearly (appropriately?)
  • From: Andrey Tarasevich
• Re: Using size_t clearly (appropriately?)
  • From: Andrey Tarasevich
• Re: Preprocessing
  • From: Eric Sosman
• Preprocessing
  • From: tatto0_2000
• Re: Order of execution
  • From: Roberto Waltman
• Re: Problems with typedef
  • From: goose
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Walter Roberson
• Re: Order of execution
  • From: Richard Heathfield
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Ian Malone
• Re: Function Pointers
  • From: lovecreatesbeauty
• Dialectal Idiosyncrasies
  • From: Frederick Gotham
• Re: which is faster?
  • From: Frederick Gotham
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Al Balmer
• Re: Need to implement strdup, strnicmp and stricmp
  • From: Roberto Waltman
• Re: need help with a new site
  • From: Al Balmer
• Need to implement strdup, strnicmp and stricmp
  • From: jamihuq
• Re: Using size_t clearly (appropriately?)
  • From: Al Balmer
• Re: Order of execution
  • From: gangchen . oz
• Re: which is faster?
  • From: Richard Heathfield
• Re: Problems with typedef
  • From: John Smith
• Re: Array elements
  • From: Kenneth Brody
• Re: Using size_t clearly (appropriately?)
  • From: Stephen Sprunk
• Re: need help with a new site
  • From: Kenneth Brody
• Re: Problems with typedef
  • From: Ian Bush
• Re: which is faster?
  • From: Frederick Gotham
• Problems with typedef
  • From: Ian Bush
• OT: Windows console programs (was Re: Function Pointers)
  • From: Kenneth Brody
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Frederick Gotham
• Re: Problems with typedef
  • From: Eric Sosman
• Re: Problems with typedef
  • From: Roberto Waltman
• Re: Problems with typedef
  • From: Robert Gamble
• Re: Problems with typedef
  • From: Lew Pitcher
• Re: Binary storage of string constants
  • From: Frederick Gotham
• Re: Array elements
  • From: Chris Dollin
• Re: Array elements
  • From: Frederick Gotham
• Re: Problems with typedef
  • From: Roberto Waltman
• Re: Need help to save strings from a file to a structure
  • From: bert
• Re: Need help to save strings from a file to a structure
  • From: Morris Dovey
• Re: Need help to save strings from a file to a structure
  • From: Chris Dollin
• Re: OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Chris Dollin
• Need help to save strings from a file to a structure
  • From: Dadio
• Re: which is faster?
  • From: Chris Dollin
• Re: which is faster?
  • From: Richard Tobin
• OT: English dialect [Was: Okay to move an "object" will-nilly?]
  • From: Nick Keighley
• Re: which is faster?
  • From: Richard Heathfield
• Re: Constructor equivalent
  • From: Gernot Frisch
• which is faster?
  • From: Sunil Varma
• Re: C Pointer problem
  • From: Joe Wright
• Re: Binary storage of string constants
  • From: Richard Heathfield
• Re: Binary storage of string constants
  • From: Ross
• Re: Binary storage of string constants
  • From: Richard Heathfield
• Re: Binary storage of string constants
  • From: Chris Dollin
• Re: Array elements
  • From: Chris Dollin
• Array elements
  • From: Kumar
• Binary storage of string constants
  • From: Ross
• Re: C Pointer problem
  • From: Richard Bos
• Re: Using size_t clearly (appropriately?)
  • From: Keith Thompson
• Re: need help with a new site
  • From: Chris Dollin
• Re: BOMDAS Vs BODMAS
  • From: Chris Dollin
• Re: Using size_t clearly (appropriately?)
  • From: Marc Thrun
• Re: C sucks at math? (help)
  • From: Walter Roberson
• Re: Using size_t clearly (appropriately?)
  • From: Michael Mair
• Re: need help with a new site
  • From: Christopher Benson-Manica
• Re: need help with a new site
  • From: Richard Heathfield
• Re: Function Pointers
  • From: pete
• Re: fgetc
  • From: Chris Torek
• Re: need help with a new site
  • From: Joshua Shinavier
• Re: economizing with functions that do the same thing
  • From: Barry Schwarz
• need help with a new site
  • From: da404LewZer
• Re: Function Pointers
  • From: Richard Heathfield
• Re: About Transfering Complex datastructures using Sockets
  • From: Nelu
• Re: Function Pointers
  • From: Frederick Gotham
• Re: Function Pointers
  • From: Richard Heathfield
• Re: Function Pointers
  • From: Keith Thompson
• Re: Using size_t clearly (appropriately?)
  • From: Richard Heathfield
• Re: Function Pointers
  • From: ab
• Re: Function Pointers
  • From: William Ahern
• Re: C sucks at math? (help)
  • From: Joe Wright
• Re: Function Pointers
  • From: Andrew Poelstra
• Re: Function Pointers
  • From: Joshua Shinavier
• Re: Using size_t clearly (appropriately?)
  • From: Andrey Tarasevich
• Re: Function Pointers
  • From: Frederick Gotham
• Re: C sucks at math? (help)
  • From: Richard Tobin
• Re: Using size_t clearly (appropriately?)
  • From: Andrey Tarasevich
• Re: Nested Variable Argument Macros
  • From: William Ahern
• Re: Using size_t clearly (appropriately?)
  • From: Keith Thompson
• Re: Using size_t clearly (appropriately?)
  • From: Al Balmer
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• Re: Using size_t clearly (appropriately?)
  • From: Richard Heathfield
• Re: C sucks at math? (help)
  • From: Joe Wright
• Re: Nested Variable Argument Macros
  • From: Keith Thompson
• Re: Using size_t clearly (appropriately?)
  • From: pete
• Re: economizing with functions that do the same thing
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: Using size_t clearly (appropriately?)
  • From: pete
• Re: Using size_t clearly (appropriately?)
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Keith Thompson
• [ot]Re: economizing with functions that do the same thing
  • From: pete
• Re: Function Pointers
  • From: Morris Dovey
• Re: Using size_t clearly (appropriately?)
  • From: Andrey Tarasevich
• Re: Function Pointers
  • From: Tom Plunket
• Re: fgetc
  • From: pete
• Re: data mining
  • From: Your Uncle
• Re: economizing with functions that do the same thing
  • From: Ian Collins
• Re: Function Pointers
  • From: Charles Richmond
• Re: Using size_t clearly (appropriately?)
  • From: William Ahern
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Nested Variable Argument Macros
  • From: William Ahern
• Re: Using size_t clearly (appropriately?)
  • From: Al Balmer
• Re: fgetc
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: fgetc
  • From: Richard Heathfield
• Re: Function Pointers
  • From: Richard Heathfield
• Re: fgetc
  • From: pete
• Re: Function Pointers
  • From: Richard Heathfield
• Re: Function Pointers
  • From: Frederick Gotham
• Re: Function Pointers
  • From: Frederick Gotham
• Re: String data input and storage
  • From: Joe Wright
• Re: Constructor equivalent
  • From: Ian Collins
• Re: Using size_t clearly (appropriately?)
  • From: pete
• Re: Segfault City
  • From: Flash Gordon
• Re: Constructor equivalent
  • From: Keith Thompson
• Re: Using size_t clearly (appropriately?)
  • From: Keith Thompson
• Re: C Pointer problem
  • From: Flash Gordon
• Re: Function Pointers
  • From: Jack Klein
• Re: Function Pointers
  • From: Default User
• Re: Function Pointers
  • From: Andrew Poelstra
• Re: fgetc
  • From: Richard Heathfield
• Function Pointers
  • From: noridotjabi@xxxxxxxxx
• Re: Constructor equivalent
  • From: Tom Plunket
• Re: Using size_t clearly (appropriately?)
  • From: Default User
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: linux redirect problem
  • From: Richard Heathfield
• Re: Using size_t clearly (appropriately?)
  • From: Richard Heathfield
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: About Transfering Complex datastructures using Sockets
  • From: Keith Thompson
• Re: A few English terms [was Okay to move an "object" will-nilly?]
  • From: Richard Heathfield
• Re: How to prevent the quick disappearance of window
  • From: Keith Thompson
• Re: Using size_t clearly (appropriately?)
  • From: Andrew Poelstra
• Re: fgetc
  • From: pete
• Re: Sequence point at comma?
  • From: Keith Thompson
• Re: C Pointer problem
  • From: Ian Collins
• Re: C sucks at math? (help)
  • From: Keith Thompson
• Re: C Pointer problem
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: Order of execution
  • From: Chris Hills
• Re: fgetc
  • From: Herbert Rosenau
• Re: Programming challenges leading to a job?
  • From: spibou
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: Segfault City
  • From: pete
• Re: Works on Windows but not on HPUX, Help Please
  • From: pete
• Re: Constructor equivalent
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: Extending snprintf() - how to modify va_list?
  • From: Chris Torek
• Re: Using size_t clearly (appropriately?)
  • From: Michael Mair
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: tedu
• Re: Using size_t clearly (appropriately?)
  • From: Morris Dovey
• Re: C Pointer problem
  • From: Default User
• Using size_t clearly (appropriately?)
  • From: Mark Odell
• Re: Working with negative numbers
  • From: Keith Thompson
• Re: linux redirect problem
  • From: Bill Pursell
• Re: qsort() results: implementation dependent?
  • From: Keith Thompson
• Re: Working with negative numbers
  • From: Bill Pursell
• Re: Order of execution
  • From: Stephen Sprunk
• Re: How to prevent the quick disappearance of window
  • From: av
• Re: Multiplications by powers of 2
  • From: Dann Corbit
• Re: automated coding standard validation?
  • From: Dann Corbit
• Re: Integer Promotion?
  • From: Peter Boettcher
• Re: __STDIN__ and __STDOUT__
  • From: Jack Klein
• Re: Works on Windows but not on HPUX, Help Please
  • From: Walter Roberson
• Re: C Pointer problem
  • From: Walter Roberson
• Re: Integer Promotion?
  • From: Andrew Poelstra
• __STDIN__ and __STDOUT__
  • From: noridotjabi@xxxxxxxxx
• Re: Sequence point at comma?
  • From: Al Balmer
• Re: Okay to move an "object" will-nilly?
  • From: Jack Klein
• Re: Sequence point at comma?
  • From: Tom St Denis
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: Sequence point at comma?
  • From: Robert Gamble
• Re: Sequence point at comma?
  • From: Roberto Waltman
• Re: Sequence point at comma?
  • From: Michael Mair
• Sequence point at comma?
  • From: Frederick Gotham
• Re: Order of execution
  • From: Michael Mair
• Re: Segfault City
  • From: Michael Mair
• Re: Order of execution
  • From: Roberto Waltman
• Re: Order of execution
  • From: Michael Mair
• Re: About Transfering Complex datastructures using Sockets
  • From: Tom St Denis
• Re: About Transfering Complex datastructures using Sockets
  • From: deepak
• Re: Order of execution
  • From: Richard Bos
• Re: Working with negative numbers
  • From: Michael Mair
• Re: Order of execution
  • From: Roberto Waltman
• Order of execution
  • From: Sabiyur
• Re: Multiplications by powers of 2
  • From: Al Balmer
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: FILE *
  • From: Richard Bos
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: Working with negative numbers
  • From: Richard Bos
• Re: About Transfering Complex datastructures using Sockets
  • From: Flash Gordon
• Re: Programming challenges leading to a job?
  • From: Robert Latest
• Re: Integer Promotion?
  • From: Roberto Waltman
• Re: Value Bits Vs Object Bits
  • From: Hallvard B Furuseth
• Re: Help requested - Application to use an IP interface
  • From: Roberto Waltman
• Re: Multiplications by powers of 2
  • From: Dik T. Winter
• Re: FILE *
  • From: cerelaz
• Re: Working with negative numbers
  • From: Richard Tobin
• Re: FILE *
  • From: Igmar Palsenberg
• FILE *
  • From: cerelaz
• Re: About Transfering Complex datastructures using Sockets
  • From: Roberto Waltman
• Re: Working with negative numbers
  • From: Richard Tobin
• Re: About Transfering Complex datastructures using Sockets
  • From: Morris Dovey
• Re: Segfault City
  • From: Kenneth Brody
• Re: Working with negative numbers
  • From: Roberto Waltman
• Re: Okay to move an "object" will-nilly?
  • From: Morris Dovey
• Re: Multiplications by powers of 2
  • From: Stephen Sprunk
• Re: Working with negative numbers
  • From: Dik T. Winter
• About Transfering Complex datastructures using Sockets
  • From: sareel
• Re: Okay to move an "object" will-nilly?
  • From: Roberto Waltman
• Re: Multiplications by powers of 2
  • From: Tim Prince
• Re: C sucks at math? (help)
  • From: Flash Gordon
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: Integer Promotion?
  • From: Frederick Gotham
• Re: qsort() results: implementation dependent?
  • From: Max
• Re: Help requested - Application to use an IP interface
  • From: Morris Dovey
• Re: Working with negative numbers
  • From: Dik T. Winter
• Re: qsort() results: implementation dependent?
  • From: Eric Sosman
• Re: Working with negative numbers
  • From: Dik T. Winter
• Re: qsort() results: implementation dependent?
  • From: pete
• Re: Multiplications by powers of 2
  • From: Morris Dovey
• Re: Working with negative numbers
  • From: Eric Sosman
• Re: Working with negative numbers
  • From: Eric Sosman
• Re: C sucks at math? (help)
  • From: Richard Tobin
• Extending snprintf() - how to modify va_list?
  • From: A. Farber
• Re: kernel module: beginner
  • From: Joe Estock
• Re: Integer Promotion?
  • From: Eric Sosman
• Re: C sucks at math? (help)
  • From: Richard Tobin
• Re: Multiplications by powers of 2
  • From: pete
• Re: linux redirect problem
  • From: Lew Pitcher
• Re: qsort() results: implementation dependent?
  • From: Max
• Re: Constructor equivalent
  • From: Roberto Waltman
• Re: Segfault City
  • From: pete
• Re: Help requested - Application to use an IP interface
  • From: MikeC
• Re: C Pointer problem
  • From: pete
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: Constructor equivalent
  • From: pete
• Re: Okay to move an "object" will-nilly?
  • From: pete
• Re: Alignment of pointer to void
  • From: David Deharbe
• Re: Integer Promotion?
  • From: pete
• Re: Negative number system as compile-time constant?
  • From: pete
• Re: Working with negative numbers
  • From: Flash Gordon
• Re: linux redirect problem
  • From: Flash Gordon
• Re: Working with negative numbers
  • From: pete
• Re: Working with negative numbers
  • From: pete
• Re: Working with negative numbers
  • From: pete
• Re: kernel module: beginner
  • From: Ian Malone
• Re: fgetc
  • From: pete
• Re: Okay to move an "object" will-nilly?
  • From: Tom St Denis
• Re: Constructor equivalent
  • From: Ian Collins
• Re: Constructor equivalent
  • From: Gernot Frisch
• Okay to move an "object" will-nilly?
  • From: Frederick Gotham
• Re: C Pointer problem
  • From: goose
• Re: Multiplications by powers of 2
  • From: Lisa Simpson
• Re: Works on Windows but not on HPUX, Help Please
  • From: goose
• Re: qsort() results: implementation dependent?
  • From: Duncan Muirhead
• Re: Multiplications by powers of 2
  • From: pnreddy1976
• Re: Integer Promotion?
  • From: Frederick Gotham
• Re: Integer Promotion?
  • From: Frederick Gotham
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: kernel module: beginner
  • From: Ian Collins
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: hi friends
  • From: Chris Hills
• Re: Imagine: A GUI standard.
  • From: Chris Hills
• Re: Working with negative numbers
  • From: Keith Thompson
• kernel module: beginner
  • From: h . silent57
• Re: Imagine: A GUI standard.
  • From: Chris Hills
• Re: qsort() results: implementation dependent?
  • From: Keith Thompson
• Re: Working with negative numbers
  • From: Giorgio Pastore
• Re: linux redirect problem
  • From: Keith Thompson
• qsort() results: implementation dependent?
  • From: Max
• Re: Is the output of the preprocessor deterministic ?
  • From: Harald van Dijk
• Re: linux redirect problem
  • From: Bill Pursell
• linux redirect problem
  • From: cmk128
• Re: How to prevent the quick disappearance of window
  • From: Robert Gamble
• Re: Multiplications by powers of 2
  • From: Morris Dovey
• Re: Working with negative numbers
  • From: Bill Pursell
• Re: Segfault City
  • From: Michael Mair
• Re: automated coding standard validation?
  • From: Michael Mair
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: economizing with functions that do the same thing
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: Roberto Waltman
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: Programming challenges leading to a job?
  • From: Thad Smith
• Re: fopen() causes an "obvious" time delay in WC ???
  • From: Gordon Burditt
• Re: fgetc
  • From: Andrew Poelstra
• Re: fgetc
  • From: lovecreatesbeauty
• Re: C Pointer problem
  • From: Gordon Burditt
• Re: Working with negative numbers
  • From: Keith Thompson
• Re: Works on Windows but not on HPUX, Help Please
  • From: Keith Thompson
• Re: Working with negative numbers
  • From: Richard Heathfield
• Re: BOMDAS Vs BODMAS
  • From: Richard Heathfield
• Re: String data input and storage
  • From: Christoph Scholtes
• Re: Negative number system as compile-time constant?
  • From: Frederick Gotham
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: Alignment of pointer to void
  • From: Keith Thompson
• Re: String data input and storage
  • From: Barry Schwarz
• Re: Negative number system as compile-time constant?
  • From: Christoph Scholtes
• Re: Imagine: A GUI standard.
  • From: Dann Corbit
• fopen() causes an "obvious" time delay in WC ???
  • From: liaoo
• Re: basics
  • From: Richard Heathfield
• Re: BOMDAS Vs BODMAS
  • From: Frederick Gotham
• Re: Imagine: A GUI standard.
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: Mistake in solutions to K&R?
  • From: poodles
• Re: BOMDAS Vs BODMAS
  • From: Keith Thompson
• Re: Mistake in solutions to K&R?
  • From: poodles
• Re: Is the output of the preprocessor deterministic ?
  • From: Keith Thompson
• Re: basics
  • From: Al Balmer
• Re: Working with negative numbers
  • From: pete
• Re: Is the output of the preprocessor deterministic ?
  • From: Keith Thompson
• Re: basics
  • From: Keith Thompson
• Re: BOMDAS Vs BODMAS
  • From: Richard Tobin
• Re: C sucks at math? (help)
  • From: Dik T. Winter
• Re: Mistake in solutions to K&R?
  • From: Richard Heathfield
• Re: Alignment of pointer to void
  • From: Dik T. Winter
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: BOMDAS Vs BODMAS
  • From: Michael Mair
• Re: BOMDAS Vs BODMAS
  • From: Richard Heathfield
• Re: automated coding standard validation?
  • From: Walter Roberson
• Re: Imagine: A GUI standard.
  • From: Walter Roberson
• Re: Is the output of the preprocessor deterministic ?
  • From: Skarmander
• Re: automated coding standard validation?
  • From: Michael Mair
• Re: Is the output of the preprocessor deterministic ?
  • From: spibou
• Re: automated coding standard validation?
  • From: Michael Mair
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: automated coding standard validation?
  • From: Richard Heathfield
• Re: Function return type
  • From: Richard Heathfield
• Re: basics
  • From: Richard Heathfield
• Re: Working with negative numbers
  • From: pete
• Re: Working with negative numbers
  • From: pete
• Re: BOMDAS Vs BODMAS
  • From: Richard Tobin
• Re: Working with negative numbers
  • From: Eric Sosman
• Re: Working with negative numbers
  • From: Michael Mair
• Re: Works on Windows but not on HPUX, Help Please
  • From: Smurff
• Re: BOMDAS Vs BODMAS
  • From: Tom St Denis
• Re: Is the output of the preprocessor deterministic ?
  • From: pete
• Re: Works on Windows but not on HPUX, Help Please
  • From: Skarmander
• Re: Mistake in solutions to K&R?
  • From: Mark McIntyre
• Re: Is the output of the preprocessor deterministic ?
  • From: Keith Thompson
• Re: Working with negative numbers
  • From: Frederick Gotham
• Re: basics
  • From: pete
• Re: C sucks at math? (help)
  • From: Mark McIntyre
• Re: Imagine: A GUI standard.
  • From: Mark McIntyre
• Re: BOMDAS Vs BODMAS
  • From: Frederick Gotham
• Re: BOMDAS Vs BODMAS
  • From: Tom St Denis
• Weird output when using more samples (help)
  • From: Jordi
• Re: Works on Windows but not on HPUX, Help Please
  • From: Tom St Denis
• Re: BOMDAS Vs BODMAS
  • From: Mark McIntyre
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: Is the output of the preprocessor deterministic ?
  • From: Mark McIntyre
• Re: Working with negative numbers
  • From: pete
• Re: Function return type
  • From: Keith Thompson
• Re: Function return type
  • From: Keith Thompson
• Re: Negative number system as compile-time constant?
  • From: pete
• Re: hi friends
  • From: Keith Thompson
• Working with negative numbers
  • From: Frederick Gotham
• Re: basics
  • From: Keith Thompson
• Re: Is this str_rev() ok?
  • From: pete
• Re: fgetc
  • From: Keith Thompson
• Re: Works on Windows but not on HPUX, Help Please
  • From: pete
• Negative number system as compile-time constant?
  • From: Frederick Gotham
• Re: Works on Windows but not on HPUX, Help Please
  • From: Default User
• Re: C sucks at math? (help)
  • From: David Wade
• Re: Segfault City
  • From: Malcolm
• Re: C sucks at math? (help)
  • From: David Wade
• Re: Works on Windows but not on HPUX, Help Please
  • From: Walter Roberson
• Re: Is this str_rev() ok?
  • From: Skarmander
• Re: Is this str_rev() ok?
  • From: Eric Sosman
• Re: Imagine: A GUI standard.
  • From: websnarf
• Works on Windows but not on HPUX, Help Please
  • From: Smurff
• Re: fgetc
  • From: pete
• Re: Is this str_rev() ok?
  • From: pete
• Re: Mistake in solutions to K&R?
  • From: poodles
• Re: Is this str_rev() ok?
  • From: Skarmander
• Re: Is this str_rev() ok?
  • From: Skarmander
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Skarmander
• Re: C sucks at math? (help)
  • From: Flash Gordon
• Re: Inherent inefficiency in domestic "for" loop?
  • From: lawrence . jones
• Re: Is this str_rev() ok?
  • From: pete
• Re: fgetc
  • From: Herbert Rosenau
• Re: Is this str_rev() ok?
  • From: Skarmander
• Re: Imagine: A GUI standard.
  • From: Gordon Burditt
• Re: Is this str_rev() ok?
  • From: pete
• Clever Vs. Experienced
  • From: Frederick Gotham
• Re: Is this str_rev() ok?
  • From: Malcolm
• Re: Inherent inefficiency in domestic "for" loop?
  • From: av
• Re: Segfault City
  • From: av
• Re: Is this str_rev() ok?
  • From: Eric Sosman
• Re: Is this str_rev() ok?
  • From: Frederick Gotham
• Re: Segmentation Fault using the srand function
  • From: Default User
• BOMDAS Vs BODMAS
  • From: Frederick Gotham
• Re: Multiplications by powers of 2
  • From: inmatarian
• Re: Is this str_rev() ok?
  • From: Malcolm
• Re: Is this str_rev() ok?
  • From: Roberto Waltman
• Re: Programming challenges leading to a job?
  • From: Walter Roberson
• Re: Segmentation Fault using the srand function
  • From: jtagpgmr
• Re: Segmentation Fault using the srand function
  • From: Jack Klein
• Re: Segmentation Fault using the srand function
  • From: Simon Biber
• Re: Is this str_rev() ok?
  • From: Jack Klein
• Re: Is this str_rev() ok?
  • From: ballpointpenthief
• Re: Segmentation Fault using the srand function
  • From: jtagpgmr
• Re: Segmentation Fault using the srand function
  • From: Richard Heathfield
• Re: finding largest numbers
  • From: Dann Corbit
• Re: Is this str_rev() ok?
  • From: Richard Heathfield
• Re: Segmentation Fault using the srand function
  • From: jtagpgmr
• Re: Segmentation Fault using the srand function
  • From: Jack Klein
• Re: C Pointer problem
  • From: Simon Biber
• Is this str_rev() ok?
  • From: ballpointpenthief
• Re: Multiplications by powers of 2
  • From: Roberto Waltman
• Re: Segmentation Fault using the srand function
  • From: Richard Heathfield
• Re: Segmentation Fault using the srand function
  • From: jtagpgmr
• Re: Segmentation Fault using the srand function
  • From: Eric Sosman
• Segmentation Fault using the srand function
  • From: jtagpgmr
• Re: zero the last 13 bits of an unsigned long number
  • From: junky_fellow@xxxxxxxxxxx
• Re: Function return type
  • From: Jack Klein
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Richard Tobin
• Re: C sucks at math? (help)
  • From: Richard Tobin
• Re: C sucks at math? (help)
  • From: Default User
• Re: C free
  • From: Default User
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Skarmander
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Roberto Waltman
• Re: Inherent inefficiency in domestic "for" loop?
  • From: lawrence . jones
• Re: fgetc
  • From: pete
• Re: fgetc
  • From: pete
• Re: C Pointer problem
  • From: Frederick Gotham
• Re: Alignment of pointer to void
  • From: Roberto Waltman
• Re: Function return type
  • From: Richard Heathfield
• Re: fgetc
  • From: Nick Keighley
• Re: hi friends
  • From: Skarmander
• Re: Alignment of pointer to void
  • From: pete
• Re: zero the last 13 bits of an unsigned long number
  • From: Duncan Muirhead
• Re: hi friends
  • From: Richard Heathfield
• Re: Function return type
  • From: pete
• Re: Constructor equivalent
  • From: Roberto Waltman
• Re: fgetc
  • From: pete
• Re: fgetc
  • From: Richard Heathfield
• Re: fgetc
  • From: pete
• Re: Is the output of the preprocessor deterministic ?
  • From: Al Balmer
• Re: hi friends
  • From: Richard Heathfield
• Re: fgetc
  • From: lovecreatesbeauty
• Re: Function return type
  • From: inmatarian
• Re: fgetc
  • From: lovecreatesbeauty
• Re: Mistake in solutions to K&R?
  • From: Harald van Dijk
• Re: C Pointer problem
  • From: Simon Biber
• Re: zero the last 13 bits of an unsigned long number
  • From: Roberto Waltman
• Re: Alignment of pointer to void
  • From: Dik T. Winter
• Re: Alignment of pointer to void
  • From: Dik T. Winter
• Re: zero the last 13 bits of an unsigned long number
  • From: Tom St Denis
• Re: zero the last 13 bits of an unsigned long number
  • From: Skarmander
• Re: C sucks at math? (help)
  • From: Dik T. Winter
• zero the last 13 bits of an unsigned long number
  • From: junky_fellow@xxxxxxxxxxx
• Re: Mistake in solutions to K&R?
  • From: Dik T. Winter
• Re: Function return type
  • From: Vladimir Oka
• Re: Imagine: A GUI standard.
  • From: Chris Hills
• Re: Function return type
  • From: Tom St Denis
• Re: C sucks at math? (help)
  • From: Peter Boettcher
• Function return type
  • From: Christian Christmann
• Re: hi friends
  • From: santosh
• Re: Multiplications by powers of 2
  • From: Skarmander
• Re: hi friends
  • From: santosh
• Re: Alignment of pointer to void
  • From: Roberto Waltman
• Re: Constructor equivalent
  • From: Thad Smith
• Re: hi friends
  • From: Skarmander
• Re: finding largest numbers
  • From: Christopher Benson-Manica
• Re: Imagine: A GUI standard.
  • From: Christopher Benson-Manica
• Re: automated coding standard validation?
  • From: Roberto Waltman
• Re: C sucks at math? (help)
  • From: Richard Tobin
• Re: hi friends
  • From: pete
• Re: Alignment of pointer to void
  • From: Skarmander
• Re: fgetc
  • From: pete
• Re: economizing with functions that do the same thing
  • From: Kenny McCormack
• Re: economizing with functions that do the same thing
  • From: Chris Dollin
• Re: fgetc
  • From: 01
• Re: economizing with functions that do the same thing
  • From: Kenny McCormack
• Re: hi friends
  • From: Skarmander
• Re: fgetc
  • From: 01
• Re: hi friends
  • From: pete
• Re: String data input and storage
  • From: Christoph Scholtes
• Re: C free
  • From: Eric Sosman
• Re: Alignment of pointer to void
  • From: pete
• Re: Multiplications by powers of 2
  • From: pete
• Alignment of pointer to void
  • From: David Deharbe
• Re: fgetc
  • From: Richard Heathfield
• [ot]Re: Imagine: A GUI standard.
  • From: pete
• Re: hi friends
  • From: Skarmander
• Multiplications by powers of 2
  • From: Lisa Simpson
• Re: fgetc
  • From: pete
• Re: Imagine: A GUI standard.
  • From: pemo
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Anders Arnholm
• Re: finding largest numbers
  • From: $hiv.....
• Re: fgetc
  • From: 01
• Re: Mistake in solutions to K&R?
  • From: Richard Heathfield
• Re: C sucks at math? (help)
  • From: Dik T. Winter
• Re: hi friends
  • From: Richard Heathfield
• Re: C sucks at math? (help)
  • From: Dik T. Winter
• Mistake in solutions to K&R?
  • From: poodles
• Mistake in solutions to K&R?
  • From: poodles
• Re: hi friends
  • From: Vladimir Oka
• hi friends
  • From: appi
• Re: hi friends
  • From: Chris Dollin
• Re: C free
  • From: Flash Gordon
• Re: basics
  • From: Richard Heathfield
• Re: C free
  • From: Harald van Dijk
• Re: C free
  • From: pete
• Re: C free
  • From: Vladimir Oka
• Re: C free
  • From: pete
• Re: C free
  • From: Harald van Dijk
• Re: economizing with functions that do the same thing
  • From: Nick Keighley
• Re: C free
  • From: Harald van Dijk
• Re: C free
  • From: pete
• Re: C free
  • From: Vladimir Oka
• Re: C free
  • From: pete
• Re: fgetc
  • From: pete
• Re: fgetc
  • From: Richard Heathfield
• Re: C free
  • From: Vladimir Oka
• Re: C free
  • From: Flash Gordon
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Keith Thompson
• Re: C free
  • From: Keith Thompson
• Re: Constructor equivalent
  • From: Vladimir Oka
• Re: fgetc
  • From: lovecreatesbeauty
• Re: basics
  • From: Flash Gordon
• Re: Constructor equivalent
  • From: Gernot Frisch
• Re: C Pointer problem
  • From: Chris Dollin
• Re: fgetc
  • From: 01
• Re: Imagine: A GUI standard.
  • From: Flash Gordon
• Re: "Numerical Recipes in C" code
  • From: Your Uncle
• Re: fgetc
  • From: 01
• Re: fgetc
  • From: 01
• Re: MD5 message digest conversion to 16 byte array
  • From: Skarmander
• Re: C free
  • From: Vladimir Oka
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: fgetc
  • From: Vladimir Oka
• Re: basics
  • From: spibou
• Re: C free
  • From: spibou
• Re: Constructor equivalent
  • From: Vladimir Oka
• fgetc
  • From: 01
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Neil
• Re: Programming challenges leading to a job?
  • From: spibou
• Re: basics
  • From: 01
• Constructor equivalent
  • From: Gernot Frisch
• Re: Imagine: A GUI standard.
  • From: Gernot Frisch
• Re: C free
  • From: Harald van Dijk
• Re: C free
  • From: Reddy
• Re: String data input and storage
  • From: Barry Schwarz
• Re: Is the output of the preprocessor deterministic ?
  • From: Keith Thompson
• Re: C sucks at math? (help)
  • From: Keith Thompson
• Re: C sucks at math? (help)
  • From: Bill Pursell
• Re: Segfault City
  • From: Old Wolf
• Re: C Pointer problem
  • From: Bill Pursell
• Re: Segfault City
  • From: Old Wolf
• Re: Segfault City
  • From: Old Wolf
• Re: Is the output of the preprocessor deterministic ?
  • From: Peter Nilsson
• Re: C sucks at math? (help)
  • From: inmatarian
• Re: C free
  • From: Eric Sosman
• Re: Segfault City
  • From: Peter "Shaggy" Haywood
• Re: Segfault City
  • From: Peter "Shaggy" Haywood
• Re: C free
  • From: Keith Thompson
• Re: C free
  • From: Thad Smith
• Re: MD5 message digest conversion to 16 byte array
  • From: Tom St Denis
• Re: MD5 message digest conversion to 16 byte array
  • From: chaitali . pats
• Re: MD5 message digest conversion to 16 byte array
  • From: chaitali . pats
• Re: Programming challenges leading to a job?
  • From: Thad Smith
• Re: Forward Declarations
  • From: Keith Thompson
• Re: Forward Declarations
  • From: Frederick Gotham
• Re: Forward Declarations
  • From: Frederick Gotham
• Re: C sucks at math? (help)
  • From: Walter Roberson
• Re: C sucks at math? (help)
  • From: pete
• Re: C sucks at math? (help)
  • From: Gordon Burditt
• Re: C sucks at math? (help)
  • From: Keith Thompson
• Re: C sucks at math? (help)
  • From: Jordi
• Re: C sucks at math? (help)
  • From: Gordon Burditt
• Re: Forward Declarations
  • From: Keith Thompson
• Re: C sucks at math? (help)
  • From: Newsreader
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Juuso Hukkanen
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Keith Thompson
• Re: Arbitrary length multi-dimensional arrays
  • From: KeeganDunn
• Re: C sucks at math? (help)
  • From: Jordi
• Re: C sucks at math? (help)
  • From: Walter Roberson
• Re: Programming challenges leading to a job?
  • From: Walter Roberson
• Re: C sucks at math? (help)
  • From: Ian Collins
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• C sucks at math? (help)
  • From: Jordi
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: Imagine: A GUI standard.
  • From: Gordon Burditt
• Re: Programming challenges leading to a job?
  • From: Andrew Poelstra
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Al Balmer
• Re: Imagine: A GUI standard.
  • From: Andrew Poelstra
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Al Balmer
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Al Balmer
• Re: Is the memory argv points to writable ?
  • From: Joe Wright
• Re: Imagine: A GUI standard.
  • From: William Ahern
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: Imagine: A GUI standard.
  • From: goose
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Nelu
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Juuso Hukkanen
• Re: Programming challenges leading to a job?
  • From: Romeo Colacitti
• Re: Imagine: A GUI standard.
  • From: Walter Roberson
• Re: basics
  • From: Kenny McCormack
• Re: Imagine: A GUI standard.
  • From: Keith Thompson
• Re: finding largest numbers
  • From: Keith Thompson
• Re: Imagine: A GUI standard.
  • From: Eric Sosman
• Re: finding largest numbers
  • From: Morris Dovey
• Re: Programming challenges leading to a job?
  • From: Richard Heathfield
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Keith Thompson
• Re: Is the output of the preprocessor deterministic ?
  • From: Al Balmer
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Keith Thompson
• Re: Imagine: A GUI standard.
  • From: John Doe
• Re: Forward Declarations
  • From: Richard Heathfield
• Re: allocating space for local variables
  • From: Mark McIntyre
• Re: Forward Declarations
  • From: Tom Plunket
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Keith Thompson
• Re: Imagine: A GUI standard.
  • From: Andrew Poelstra
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Keith Thompson
• Re: Imagine: A GUI standard.
  • From: Frederick Gotham
• Re: automated coding standard validation?
  • From: Ian Collins
• Re: finding largest numbers
  • From: Frederick Gotham
• Re: Programming challenges leading to a job?
  • From: Tom St Denis
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Default User
• Imagine: A GUI standard.
  • From: noridotjabi@xxxxxxxxx
• Programming challenges leading to a job?
  • From: Romeo Colacitti
• Re: C Pointer problem
  • From: Mark McIntyre
• Re: Is the output of the preprocessor deterministic ?
  • From: Mark McIntyre
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Mark McIntyre
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Mark McIntyre
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Mark McIntyre
• Re: Error handling library
  • From: Mark McIntyre
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Babak
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Mark McIntyre
• Re: constructor?
  • From: Mark McIntyre
• Re: Multiple names... ?
  • From: Keith Thompson
• Re: Programming for Memory Management
  • From: Default User
• Re: Where can I learn about Multithreading for C
  • From: Dann Corbit
• Re: Forward Declarations
  • From: Keith Thompson
• Re: Error handling library
  • From: pete
• Re: Programming for Memory Management
  • From: Rich Gibbs
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: Programming for Memory Management
  • From: Keith Thompson
• Re: Where can I learn about Multithreading for C
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Roberto Waltman
• Re: Programming for Memory Management
  • From: Al Balmer
• Re: allocating space for local variables
  • From: Keith Thompson
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: finding largest numbers
  • From: Keith Thompson
• Re: Programming for Memory Management
  • From: Jay
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: Programming for Memory Management
  • From: Walter Roberson
• Re: automated coding standard validation?
  • From: Walter Roberson
• Re: Strange Segmentation Fault
  • From: Tim Evers
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Martin Ambuhl
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: basics
  • From: Keith Thompson
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Martin Ambuhl
• Re: How to connect SQL database in C programs
  • From: jacob navia
• Re: Forward Declarations
  • From: Tom Plunket
• Re: Error handling library
  • From: Bill Pursell
• Re: finding largest numbers
  • From: Dann Corbit
• Re: automated coding standard validation?
  • From: Al Balmer
• Re: Segfault City
  • From: Bill Pursell
• Programming for Memory Management
  • From: Jay
• Re: allocating space for local variables
  • From: "Nils O. Selåsdal"
• Re: Segfault City
  • From: Richard Heathfield
• Re: allocating space for local variables
  • From: Al Balmer
• Re: Arbitrary length multi-dimensional arrays
  • From: Michael Mair
• Re: Segfault City
  • From: Herbert Rosenau
• Re: automated coding standard validation?
  • From: Roberto Waltman
• Re: allocating space for local variables
  • From: Richard G. Riley
• Re: [OT]Re: How to connect SQL database in C programs
  • From: Juuso Hukkanen
• Re: allocating space for local variables
  • From: Al Balmer
• Re: Arbitrary length multi-dimensional arrays
  • From: Frederick Gotham
• Re: Error handling library
  • From: Andrew Poelstra
• Re: automated coding standard validation?
  • From: Robert Gamble
• Re: automated coding standard validation?
  • From: Richard G. Riley
• Re: Arbitrary length multi-dimensional arrays
  • From: Michael Mair
• Re: MD5 message digest conversion to 16 byte array
  • From: Default User
• Re: finding largest numbers
  • From: Christopher Benson-Manica
• Re: String data input and storage
  • From: Default User
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Default User
• Re: Arbitrary length multi-dimensional arrays
  • From: Ben C
• Re: automated coding standard validation?
  • From: Walter Roberson
• Re: Arbitrary length multi-dimensional arrays
  • From: Andrew Poelstra
• Re: Arbitrary length multi-dimensional arrays
  • From: Frederick Gotham
• Re: Where can I learn about Multithreading for C
  • From: P.J. Plauger
• Re: automated coding standard validation?
  • From: Roberto Waltman
• Re: automated coding standard validation?
  • From: Robert Gamble
• Re: Arbitrary length multi-dimensional arrays
  • From: Tom St Denis
• Re: automated coding standard validation?
  • From: Robert Gamble
• Re: allocating space for local variables
  • From: robertwessel2@xxxxxxxxx
• Re: finding largest numbers
  • From: Richard Tobin
• Re: allocating space for local variables
  • From: Kenneth Brody
• Arbitrary length multi-dimensional arrays
  • From: kd
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Kenneth Brody
• Re: automated coding standard validation?
  • From: Konrad Palczynski
• Re: Where can I learn about Multithreading for C
  • From: Al Balmer
• Re: allocating space for local variables
  • From: Richard G. Riley
• Re: MD5 message digest conversion to 16 byte array
  • From: Skarmander
• Re: [ot]Re: Segfault City
  • From: Kenneth Brody
• Re: new CCSID's for z/OS C/C++
  • From: Skarmander
• Re: automated coding standard validation?
  • From: Jack Klein
• Re: allocating space for local variables
  • From: Jack Klein
• Re: allocating space for local variables
  • From: Tom St Denis
• Re: allocating space for local variables
  • From: Jack Klein
• Re: allocating space for local variables
  • From: Al Balmer
• Re: A debugging implementation of malloc
  • From: Skarmander
• Re: Where can I learn about Multithreading for C
  • From: Nelu
• [OT]Re: How to connect SQL database in C programs
  • From: Al Balmer
• Re: Where can I learn about Multithreading for C
  • From: Tom St Denis
• Re: Where can I learn about Multithreading for C
  • From: bg_ie
• Re: Segfault City
  • From: Richard Bos
• Re: constructor?
  • From: Nelu
• Re: Segfault City
  • From: Dave Vandervies
• Re: Where can I learn about Multithreading for C
  • From: Nelu
• Re: allocating space for local variables
  • From: deepak
• Re: Segfault City
  • From: Frederick Gotham
• Re: finding largest numbers
  • From: Frederick Gotham
• Re: C Pointer problem
  • From: pete
• Re: Where can I learn about Multithreading for C
  • From: Tom St Denis
• Re: Where can I learn about Multithreading for C
  • From: Tom St Denis
• Re: Where can I learn about Multithreading for C
  • From: Nelu
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• Re: economizing with functions that do the same thing
  • From: Frederick Gotham
• Re: a little mistake
  • From: Chris Dollin
• Where can I learn about Multithreading for C
  • From: bg_ie
• Re: economizing with functions that do the same thing
  • From: Frederick Gotham
• Re: finding largest numbers
  • From: Richard Heathfield
• Re: finding largest numbers
  • From: Thad Smith
• Re: allocating space for local variables
  • From: Frederick Gotham
• Re: a little mistake
  • From: Frederick Gotham
• Re: A debugging implementation of malloc
  • From: Frederick Gotham
• Re: new CCSID's for z/OS C/C++
  • From: Kenny McCormack
• Re: finding largest numbers
  • From: Richard G. Riley
• Re: automated coding standard validation?
  • From: Richard G. Riley
• Re: finding largest numbers
  • From: Morris Dovey
• Re: redefine a function with a same name
  • From: Morris Dovey
• new CCSID's for z/OS C/C++
  • From: Ewald Sußner
• automated coding standard validation?
  • From: Konrad Palczynski
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Richard Tobin
• Re: Inherent inefficiency in domestic "for" loop?
  • From: SuperKoko
• Re: Segfault City
  • From: Chris Dollin
• Re: How to connect SQL database in C programs
  • From: Juuso Hukkanen
• Re: basics
  • From: Vladimir Oka
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: Error handling library
  • From: goose
• Re: Segfault City
  • From: Chris Dollin
• Re: Commutativity of operator []
  • From: Keith Thompson
• Re: economizing with functions that do the same thing
  • From: Keith Thompson
• Re: basics
  • From: Ian Collins
• Re: finding largest numbers
  • From: Keith Thompson
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Keith Thompson
• Re: How to connect SQL database in C programs
  • From: Juuso Hukkanen
• basics
  • From: chitu
• Re: MD5 message digest conversion to 16 byte array
  • From: Tom St Denis
• Re: Segfault City
  • From: Keith Thompson
• Re: How to connect SQL database in C programs
  • From: Tom St Denis
• Re: Segfault City
  • From: Keith Thompson
• Practical Programming Processes: LASER Summer School
  • From: Ilinca Ciupa
• Re: Inherent inefficiency in domestic "for" loop?
  • From: av
• Re: allocating space for local variables
  • From: "Nils O. Selåsdal"
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Ian Collins
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Martin Ambuhl
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Martin Ambuhl
• allocating space for local variables
  • From: junky_fellow@xxxxxxxxxxx
• Re: economizing with functions that do the same thing
  • From: av
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Chris Torek
• Re: finding largest numbers
  • From: Richard Heathfield
• Re: finding largest numbers
  • From: Richard Heathfield
• Re: Newbie help on string splitting
  • From: websnarf
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Richard Heathfield
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• Re: finding largest numbers
  • From: phus . lu
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• finding largest numbers
  • From: ramu
• Re: How to connect SQL database in C programs
  • From: jacob navia
• Re: Warning on assigning a function-returning-a-pointer-to-arrays
  • From: Ian Collins
• Re: Is the output of the preprocessor deterministic ?
  • From: Al Balmer
• Re: redefine a function with a same name
  • From: Richard Bos
• Warning on assigning a function-returning-a-pointer-to-arrays
  • From: I . M . !Knuth
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: Compiler Issue
  • From: Richard Bos
• Re: A debugging implementation of malloc
  • From: pete
• Re: MD5 message digest conversion to 16 byte array
  • From: Chris McDonald
• Re: String data input and storage
  • From: pete
• Re: Data structures
  • From: Neil
• Re: Learn recursion
  • From: Charles Richmond
• Re: C free
  • From: Charles Richmond
• Re: MD5 message digest conversion to 16 byte array
  • From: Neil
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: String data input and storage
  • From: Christoph Scholtes
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Neil
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Skarmander
• Re: String data input and storage
  • From: Chris Torek
• Re: Error handling library
  • From: Michael Mair
• Re: Is the memory argv points to writable ?
  • From: Herbert Rosenau
• Re: spinoza1111 resigns from "segfault city"
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: MD5 message digest conversion to 16 byte array
  • From: chaitali . pats
• Re: A debugging implementation of malloc
  • From: Skarmander
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Chris Torek
• Re: Data structures
  • From: Skarmander
• Re: MD5 message digest conversion to 16 byte array
  • From: Skarmander
• Data structures
  • From: Sidhu
• Re: Error handling library
  • From: Andrew Poelstra
• Re: Inherent inefficiency in [ordinary] "for" loop?
  • From: Chris Torek
• Re: Error handling library
  • From: Bill Pursell
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Thad Smith
• Re: C Pointer problem
  • From: Andrew Poelstra
• Re: Segfault City
  • From: Bill Pursell
• Re: Learn recursion
  • From: red_hax0r@xxxxxxxxx
• Re: Inherent inefficiency in domestic "for" loop?
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: L7
• Re: String data input and storage
  • From: Morris Dovey
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: String data input and storage
  • From: Digital Logic
• Re: String data input and storage
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: L7
• Re: Problem in compiling a C code with MSVC++6.00
  • From: pete
• Re: C Pointer problem
  • From: pete
• Re: String data input and storage
  • From: Christoph Scholtes
• Re: String data input and storage
  • From: Christoph Scholtes
• Re: a little mistake
  • From: Dave Thompson
• Re: C Pointer problem
  • From: Dave Thompson
• Re: Memory (read) access violation handling in C
  • From: Dave Thompson
• Re: segmentation fault
  • From: Dave Thompson
• Re: Educated guesses for efficiency?
  • From: Dave Thompson
• Re: Newbie help on string splitting
  • From: Dave Thompson
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Babak
• Re: economizing with functions that do the same thing
  • From: pete
• Re: Problem in compiling a C code with MSVC++6.00
  • From: pete
• Re: economizing with functions that do the same thing
  • From: Keith Thompson
• Re: Commutativity of operator []
  • From: Dik T. Winter
• Re: C free
  • From: Walter Roberson
• Re: economizing with functions that do the same thing
  • From: Frederick Gotham
• Re: Is the output of the preprocessor deterministic ?
  • From: Walter Roberson
• Re: economizing with functions that do the same thing
  • From: pete
• Re: economizing with functions that do the same thing
  • From: pete
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Babak
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Eric Sosman
• Re: economizing with functions that do the same thing
  • From: Kenny McCormack
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: How to connect SQL database in C programs
  • From: Keith Thompson
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: economizing with functions that do the same thing
  • From: Keith Thompson
• Re: String data input and storage
  • From: Digital Logic
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Richard Tobin
• Re: Problem in compiling a C code with MSVC++6.00
  • From: Frederick Gotham
• Re: String data input and storage
  • From: pete
• Re: String data input and storage
  • From: Morris Dovey
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Frederick Gotham
• Re: Problem in compiling a C code with MSVC++6.00
  • From: pete
• String data input and storage
  • From: Christoph Scholtes
• Problem in compiling a C code with MSVC++6.00
  • From: Babak
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Richard Tobin
• Re: beginner c question
  • From: mensanator@xxxxxxx
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Gordon Burditt
• Re: Inherent inefficiency in domestic "for" loop?
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Ben Pfaff
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Gryff Stokoe
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Frederick Gotham
• Re: Error handling library
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Frederick Gotham
• Re: Multiple names... ?
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Frederick Gotham
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Richard Tobin
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Gordon Burditt
• Re: Error handling library
  • From: Andrew Poelstra
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Alf P. Steinbach
• Re: Error handling library
  • From: pete
• Re: Inherent inefficiency in domestic "for" loop?
  • From: Ben Pfaff
• Re: Learn recursion
  • From: Frederick Gotham
• Re: Learn recursion
  • From: Morris Dovey
• Inherent inefficiency in domestic "for" loop?
  • From: Frederick Gotham
• Re: redefine a function with a same name
  • From: Joe Wright
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: A debugging implementation of malloc
  • From: Richard Tobin
• Re: A debugging implementation of malloc
  • From: websnarf
• Multiple names... ?
  • From: Frederick Gotham
• Error handling library
  • From: Andrew Poelstra
• Re: How to connect SQL database in C programs
  • From: Tom St Denis
• How to connect SQL database in C programs
  • From: Sachin
• Re: C free
  • From: Kenny McCormack
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: Learn recursion
  • From: Kenny McCormack
• Re: Is the output of the preprocessor deterministic ?
  • From: Kenny McCormack
• Learn recursion
  • From: red_hax0r@xxxxxxxxx
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: Is the output of the preprocessor deterministic ?
  • From: Gordon Burditt
• Re: Is the output of the preprocessor deterministic ?
  • From: Keith Thompson
• Re: Is the output of the preprocessor deterministic ?
  • From: Mark McIntyre
• Re: C free
  • From: pete
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: beginner c question
  • From: pete
• Re: types of 'Open' command
  • From: Kenny McCormack
• Re: C free
  • From: Keith Thompson
• Re: A debugging implementation of malloc
  • From: Skarmander
• Re: yacc under cygwin - undefined symbols
  • From: Keith Thompson
• Re: Is the output of the preprocessor deterministic ?
  • From: Al Balmer
• Re: beginner c question
  • From: Al Balmer
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: coderwiki.com is starting and needs you!
  • From: goose
• Re: comparing signed and unsigned integers
  • From: Tom St Denis
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: beginner c question
  • From: Andrew Poelstra
• Re: comparing signed and unsigned integers
  • From: Joe Wright
• Re: beginner c question
  • From: Richard Heathfield
• Re: beginner c question
  • From: mensanator@xxxxxxx
• Re: Value Bits Vs Object Bits
  • From: Frederick Gotham
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: Playing around with byte order
  • From: Frederick Gotham
• Re: Is the output of the preprocessor deterministic ?
  • From: Mark McIntyre
• Re: Is the output of the preprocessor deterministic ?
  • From: Mark McIntyre
• Re: Is the output of the preprocessor deterministic ?
  • From: Harald van Dijk
• Re: yacc under cygwin - undefined symbols
  • From: Mark McIntyre
• Re: clc-wiki gone?
  • From: Flash Gordon
• Re: A debugging implementation of malloc
  • From: Ben Pfaff
• Re: beginner c question
  • From: Christoph Scholtes
• Re: C free
  • From: Gordon Burditt
• Re: Is the output of the preprocessor deterministic ?
  • From: Gordon Burditt
• Re: Is the output of the preprocessor deterministic ?
  • From: spibou
• Re: Value Bits Vs Object Bits
  • From: Eric Sosman
• Re: Segfault City
  • From: pete
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: Is the output of the preprocessor deterministic ?
  • From: Barry Schwarz
• Re: A debugging implementation of malloc
  • From: Malcolm
• Re: Playing around with byte order
  • From: pete
• Re: Segfault City
  • From: Malcolm
• Re: Value Bits Vs Object Bits
  • From: pete
• Re: A debugging implementation of malloc
  • From: Barry Schwarz
• Re: Playing around with byte order
  • From: inmatarian
• Re: Playing around with byte order
  • From: pete
• Re: A debugging implementation of malloc
  • From: jacob navia
• Re: Is the output of the preprocessor deterministic ?
  • From: spibou
• Re: Segfault City
  • From: Malcolm
• Re: A debugging implementation of malloc
  • From: Eric Sosman
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Richard Heathfield
• Re: spinoza1111 resigns from "segfault city"
  • From: Morris Dovey
• Re: Segfault City
  • From: Malcolm
• Re: C free
  • From: Malcolm
• Re: Is the output of the preprocessor deterministic ?
  • From: Al Balmer
• Re: What do you think about the code?
  • From: Joe Wright
• Re: Value Bits Vs Object Bits
  • From: Frederick Gotham
• Re: C free
  • From: Flash Gordon
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: Segfault City
  • From: pete
• Re: Segfault City
  • From: Frederick Gotham
• Re: Is the output of the preprocessor deterministic ?
  • From: Harald van Dijk
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: pete
• Re: Segfault City
  • From: Bill Pursell
• Re: Segfault City
  • From: pete
• Re: Segfault City
  • From: Frederick Gotham
• Re: Is the output of the preprocessor deterministic ?
  • From: pete
• Playing around with byte order
  • From: Frederick Gotham
• Re: Is the output of the preprocessor deterministic ?
  • From: spibou
• Re: Segfault City
  • From: pete
• Re: Is the output of the preprocessor deterministic ?
  • From: Tom St Denis
• Re: Segfault City
  • From: Barry
• Re: C free
  • From: spibou
• C free
  • From: Reddy
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Herbert Rosenau
• Is the output of the preprocessor deterministic ?
  • From: spibou
• yacc under cygwin - undefined symbols
  • From: Christoph Kukulies
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: Is the memory argv points to writable ?
  • From: Bill Pursell
• Re: Segfault City
  • From: Malcolm
• Re: A debugging implementation of malloc
  • From: jacob navia
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: Is the memory argv points to writable ?
  • From: Richard Heathfield
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Richard Heathfield
• Re: Is the memory argv points to writable ?
  • From: Bill Pursell
• Re: Segfault City
  • From: Malcolm
• Re: Multiple Arguements like in printf
  • From: Malcolm
• Re: segmentation fault with getc()
  • From: Bill Pursell
• Re: A debugging implementation of malloc
  • From: Chris Torek
• Re: Multiple Arguements like in printf
  • From: Chris Torek
• Re: segmentation fault with getc()
  • From: Ian Collins
• Re: segmentation fault with getc()
  • From: hzmonte
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Chris Smith
• Re: segmentation fault with getc()
  • From: Tom St Denis
• Re: Segfault City
  • From: lovecreatesbeauty
• Re: Segfault City
  • From: blmblm
• Re: Segfault City
  • From: blmblm
• Re: segmentation fault with getc()
  • From: Keith Thompson
• Re: segmentation fault with getc()
  • From: Andrew Poelstra
• Re: A debugging implementation of malloc
  • From: Keith Thompson
• Re: segmentation fault with getc()
  • From: Andrew Poelstra
• Re: Segfault City
  • From: John Smith
• segmentation fault with getc()
  • From: hzmonte
• Re: Multiple Arguements like in printf
  • From: Keith Thompson
• Re: Commutativity of operator []
  • From: Andrew Poelstra
• Re: Commutativity of operator []
  • From: Kenneth Brody
• Re: fgets info
  • From: Kenneth Brody
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Ian Collins
• Re: A debugging implementation of malloc
  • From: Ian Collins
• [ot]Re: spinoza1111 resigns from "segfault city"
  • From: pete
• Re: redefine a function with a same name
  • From: Herbert Rosenau
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: pete
• Re: A debugging implementation of malloc
  • From: Barry Schwarz
• Re: Segfault City
  • From: Keith Thompson
• Re: spinoza1111 resigns from "segfault city"
  • From: Mark McIntyre
• Re: Named parameters
  • From: Mark McIntyre
• Re: Segfault City
  • From: Richard Heathfield
• Re: Named parameters
  • From: Mark McIntyre
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: Segfault City
  • From: Keith Thompson
• [ot]Re: Segfault City
  • From: pete
• Re: A debugging implementation of malloc
  • From: Ben C
• Re: Segfault City
  • From: Andrew Poelstra
• Re: A debugging implementation of malloc
  • From: Ian Collins
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Richard Heathfield
• A debugging implementation of malloc
  • From: jacob navia
• Re: Segfault City
  • From: Keith Thompson
• Re: Is the memory argv points to writable ?
  • From: Richard Heathfield
• Re: spinoza1111 resigns from "segfault city"
  • From: Malcolm
• Re: spinoza1111 resigns from "segfault city"
  • From: Richard Heathfield
• Re: Segfault City
  • From: Andrew Poelstra
• Re: Job: Algorithmic Search Engineers wanted
  • From: Keith Thompson
• Is the memory argv points to writable ?
  • From: spibou
• Re: spinoza1111 resigns from "segfault city"
  • From: Andrew Poelstra
• Re: Named parameters
  • From: Keith Thompson
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Dave Vandervies
• Re: Forward Declarations
  • From: Richard Heathfield
• spinoza1111 resigns from "segfault city"
  • From: spinoza1111
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Help requested - Application to use an IP interface
  • From: MikeC
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: CBFalconer
• Re: coderwiki.com is starting and needs you!
  • From: Malcolm
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: CBFalconer
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: spinoza1111
• Portable C in the real world (was: Re: Segfault City)
  • From: Dave Vandervies
• Re: Segfault City
  • From: spinoza1111
• Re: coderwiki.com is starting and needs you!
  • From: CBFalconer
• Re: Segfault City
  • From: spinoza1111
• Re: Commutativity of operator []
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Forward Declarations
  • From: Chris Torek
• Re: Segfault City
  • From: spinoza1111
• Job: Algorithmic Search Engineers wanted
  • From: Frenkel
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Chris Smith
• Re: Segfault City
  • From: Malcolm
• Re: Multiple Arguements like in printf
  • From: Malcolm
• Re: Segfault City
  • From: CBFalconer
• Re: Segfault City
  • From: spinoza1111
• Re: Commutativity of operator []
  • From: Simon Biber
• Re: Segfault City
  • From: pete
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Andrew Poelstra
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: Named parameters
  • From: Joe Wright
• Re: coderwiki.com is starting and needs you!
  • From: Thad Smith
• Re: // vs /*
  • From: Andrew Poelstra
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: Walter Roberson
• Re: Segfault City
  • From: Bill Pursell
• Re: Telecom programming
  • From: a.abdulwahab@xxxxxxxxx
• Re: Segfault City
  • From: Richard Heathfield
• Re: Wrong output - eliminate spaces in sentence.
  • From: av
• Re: Segfault City
  • From: Ben Pfaff
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: blmblm
• Re: Segfault City
  • From: blmblm
• Re: Segfault City
  • From: John Smith
• Re: Segfault City
  • From: blmblm
• Re: Segfault City
  • From: Roberto Waltman
• Re: Segfault City
  • From: Friedrich Dominicus
• Re: Segfault City
  • From: CBFalconer
• Re: Multiple Arguements like in printf
  • From: Michael Mair
• Re: sizeof
  • From: CBFalconer
• Multiple Arguements like in printf
  • From: bg_ie
• Re: Segfault City
  • From: CBFalconer
• Re: Segfault City
  • From: Michael Mair
• Re: // vs /*
  • From: Tom St Denis
• Re: Segfault City
  • From: Skarmander
• Re: Segfault City
  • From: Malcolm
• Re: Segfault City
  • From: Bill Pursell
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: Mark McIntyre
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Segfault City
  • From: Richard Heathfield
• Re: Named parameters
  • From: Mark McIntyre
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: pemo
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: spinoza1111
• Re: // vs /*
  • From: Richard Heathfield
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: pete
• Re: Segfault City
  • From: spinoza1111
• Re: economizing with functions that do the same thing
  • From: Michael Mair
• Re: Segfault City
  • From: spibou
• Re: Segfault City
  • From: spinoza1111
• Re: Segfault City
  • From: spibou
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: Forward Declarations
  • From: Richard Heathfield
• Re: Segfault City
  • From: Richard Heathfield
• Re: Segfault City
  • From: pemo
• Re: Segfault City
  • From: lovecreatesbeauty
• Re: Segfault City
  • From: Richard Heathfield
• Re: // vs /*
  • From: jaysome
• Re: // vs /*
  • From: Richard Heathfield
• Re: Segfault City
  • From: spibou
• Re: beginner c question
  • From: Al Balmer
• Re: Segfault City
  • From: Friedrich Dominicus
• How about *this* code? (Was: What do you think about the code?)
  • From: James Dow Allen
• Re: Segfault City
  • From: Andrew Poelstra
• Re: Segfault City
  • From: Friedrich Dominicus
• Re: Segfault City
  • From: Jack Klein
• Re: strange use of format specifier in printf
  • From: Jack Klein
• Re: coderwiki.com is starting and needs you!
  • From: Thad Smith
• Re: beginner c question
  • From: Malcolm
• Re: Strings, Strings and Damned Strings
  • From: Malcolm
• Re: strange use of format specifier in printf
  • From: Keith Thompson
• Re: Segfault City
  • From: Keith Thompson
• Re: Segfault City
  • From: Eric Sosman
• Re: Forward Declarations
  • From: Chris Torek
• Re: // vs /*
  • From: Andrew Poelstra
• Re: // vs /*
  • From: Keith Thompson
• Re: strange use of format specifier in printf
  • From: Andrew Poelstra
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Strings, Strings and Damned Strings
  • From: Andrew Poelstra
• Re: Segfault City
  • From: Andrew Poelstra
• Re: Segfault City
  • From: Keith Thompson
• Re: economizing with functions that do the same thing
  • From: pete
• Re: u_long valid C?
  • From: Keith Thompson
• Re: Strings, Strings and Damned Strings
  • From: Ben
• Re: economizing with functions that do the same thing
  • From: Keith Thompson
• Re: strange use of format specifier in printf
  • From: Keith Thompson
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Skarmander
• Re: redefine a function with a same name
  • From: Keith Thompson
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Keith Thompson
• Re: Named parameters
  • From: Keith Thompson
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: strange use of format specifier in printf
  • From: Money
• Re: economizing with functions that do the same thing
  • From: Ian Collins
• Re: economizing with functions that do the same thing
  • From: Your Uncle
• Re: economizing with functions that do the same thing
  • From: Richard Heathfield
• Re: u_long valid C?
  • From: Ian Collins
• Re: u_long valid C?
  • From: jjf
• Re: economizing with functions that do the same thing
  • From: Dann Corbit
• u_long valid C?
  • From: Joe Van Dyk
• economizing with functions that do the same thing
  • From: Your Uncle
• Re: strange use of format specifier in printf
  • From: Frederick Gotham
• Re: Named parameters
  • From: Mark McIntyre
• Re: Commutativity of operator []
  • From: Mark McIntyre
• Re: redefine a function with a same name
  • From: Andrew Poelstra
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Mark McIntyre
• Re: Compiler Issue
  • From: Ian Collins
• Re: Forward Declarations
  • From: Tom Plunket
• Re: coderwiki.com is starting and needs you!
  • From: Mark McIntyre
• Re: coderwiki.com is starting and needs you!
  • From: Mark McIntyre
• Re: Named parameters
  • From: Keith Thompson
• Re: Named parameters
  • From: Keith Thompson
• Re: Forward Declarations
  • From: Richard Heathfield
• Re: Forward Declarations
  • From: Tom Plunket
• Re: Named parameters
  • From: Mark McIntyre
• Re: Named parameters
  • From: Mark McIntyre
• Re: // vs /*
  • From: Mark McIntyre
• Re: redefine a function with a same name
  • From: Morris Dovey
• Re: Forward Declarations
  • From: Richard Heathfield
• Re: String macro as wchar_t pointer?
  • From: Heiner
• Forward Declarations
  • From: Tom Plunket
• Re: String macro as wchar_t pointer?
  • From: Eric Sosman
• Re: Unnamed members
  • From: Tom Plunket
• String macro as wchar_t pointer?
  • From: Heiner
• Re: beginner c question
  • From: Richard Heathfield
• Re: Unnamed members
  • From: Keith Thompson
• Re: strange use of format specifier in printf
  • From: Keith Thompson
• Re: pointer arithmetic
  • From: Keith Thompson
• Re: Commutativity of operator []
  • From: Keith Thompson
• Re: Commutativity of operator []
  • From: CBFalconer
• Re: Commutativity of operator []
  • From: lawrence . jones
• Re: Unnamed members
  • From: Tom Plunket
• Re: beginner c question
  • From: Richard Heathfield
• Re: beginner c question
  • From: Default User
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: Unnamed members
  • From: Tom Plunket
• Re: Unnamed members
  • From: Tom Plunket
• Re: beginner c question
  • From: Dann Corbit
• Re: Commutativity of operator []
  • From: Skarmander
• Re: strange use of format specifier in printf
  • From: Money
• Re: strange use of format specifier in printf
  • From: Richard Heathfield
• Re: beginner c question
  • From: goose
• Re: redefine a function with a same name
  • From: Keith Thompson
• Re: beginner c question
  • From: jacob navia
• Re: redefine a function with a same name
  • From: Keith Thompson
• Re: Compiler Issue
  • From: Keith Thompson
• Re: coderwiki.com is starting and needs you!
  • From: goose
• Re: Commutativity of operator []
  • From: Richard Heathfield
• Re: Compiler Issue
  • From: gw7rib
• Re: strange use of format specifier in printf
  • From: Money
• Re: Unnamed members
  • From: Frederick Gotham
• Re: Commutativity of operator []
  • From: Frederick Gotham
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: William Ahern
• Re: Help requested - Application to use an IP interface
  • From: Roberto Waltman
• Re: beginner c question
  • From: Nelu
• Re: beginner c question
  • From: Richard Heathfield
• Re: beginner c question
  • From: Nelu
• Re: redefine a function with a same name
  • From: CBFalconer
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Andrey Tarasevich
• Re: pointer arithmetic
  • From: Neil Ferguson
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Andrey Tarasevich
• Re: pointer arithmetic
  • From: swengineer001@xxxxxxxxx
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: pointer arithmetic
  • From: Walter Roberson
• Re: beginner c question
  • From: Richard Heathfield
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: Andrey Tarasevich
• Re: pointer arithmetic
  • From: Joshua Shinavier
• Re: redefine a function with a same name
  • From: goose
• Re: data mining
  • From: Juuso Hukkanen
• Re: regarding memset
  • From: Eric Sosman
• Re: sizeof
  • From: Richard Tobin
• Re: redefine a function with a same name
  • From: goose
• Re: regarding memset
  • From: Donkey Hot
• pointer arithmetic
  • From: barikat
• Re: redefine a function with a same name
  • From: CBFalconer
• Re: beginner c question
  • From: Andrew Poelstra
• Re: redefine a function with a same name
  • From: Andrew Poelstra
• Re: [OT] Help requested - Application to use an IP interface
  • From: Morris Dovey
• Re: beginner c question
  • From: CBFalconer
• Re: Commutativity of operator []
  • From: Robert Gamble
• Re: coderwiki.com is starting and needs you!
  • From: CBFalconer
• Help requested - Application to use an IP interface
  • From: MikeC
• Re: beginner c question
  • From: goose
• Commutativity of operator []
  • From: lwawrzyniak
• Re: Wrong output - eliminate spaces in sentence.
  • From: av
• Re: sizeof
  • From: CBFalconer
• Re: redefine a function with a same name
  • From: goose
• Re: sizeof
  • From: CBFalconer
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: fei.liu@xxxxxxxxx
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: "Nils O. Selåsdal"
• Re: What do you think about the code?
  • From: goose
• Re: Hi
  • From: Richard Heathfield
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Richard Tobin
• Re: coderwiki.com is starting and needs you!
  • From: goose
• Re: Compiler Issue
  • From: Harald van Dijk
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Richard Bos
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: Marc Boyer
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: spibou
• Re: Compiler Issue
  • From: Richard Bos
• Re: Hi
  • From: Veda
• Re: Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: "Nils O. Selåsdal"
• Re: coderwiki.com is starting and needs you!
  • From: Richard Bos
• Why pointer to "one past" is allowed but pointer to "one before" is not ?
  • From: spibou
• Re: Converting negative integer to octal/hexadecimal
  • From: Eric Sosman
• Re: sizeof
  • From: Richard Tobin
• Re: coderwiki.com is starting and needs you!
  • From: Richard Tobin
• Re: beginner c question
  • From: Asbjørn Sæbø
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: coderwiki.com is starting and needs you!
  • From: pemo
• Re: Compiler Issue
  • From: Richard Heathfield
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: beginner c question
  • From: Richard Heathfield
• Re: 16-Bit char pointers valid?
  • From: Harald van Dijk
• Re: beginner c question
  • From: Asbjørn Sæbø
• Re: bit fileds or bit manuplation
  • From: pete
• Re: Compiler Issue
  • From: Chris Dollin
• Re: Compiler Issue
  • From: Ian Collins
• Re: Template Engine like Smarty
  • From: Neurotic
• Re: redefine a function with a same name
  • From: Richard Bos
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: pete
• Re: coderwiki.com is starting and needs you!
  • From: Richard Bos
• Re: "Numerical Recipes in C" code
  • From: Richard Bos
• Re: sizeof
  • From: Richard Bos
• Re: coderwiki.com is starting and needs you!
  • From: pemo
• Re: Converting negative integer to octal/hexadecimal
  • From: Chris Dollin
• Re: beginner c question
  • From: pencilneck
• Re: Converting negative integer to octal/hexadecimal
  • From: spibou
• Re: Converting negative integer to octal/hexadecimal
  • From: Richard Heathfield
• Re: Converting negative integer to octal/hexadecimal
  • From: jaks . maths
• Re: Compiler Issue
  • From: Richard Heathfield
• Re: redefine a function with a same name
  • From: CBFalconer
• Re: Compiler Issue
  • From: Frederick Gotham
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: coderwiki.com is starting and needs you!
  • From: pemo
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: beginner c question
  • From: Richard Heathfield
• Re: beginner c question
  • From: Vladimir Oka
• Re: redefine a function with a same name
  • From: Chris Dollin
• Re: coderwiki.com is starting and needs you!
  • From: pemo
• Re: redefine a function with a same name
  • From: Chris Dollin
• beginner c question
  • From: pencilneck
• Re: redefine a function with a same name
  • From: rrs . matrix
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: redefine a function with a same name
  • From: Richard Heathfield
• Re: redefine a function with a same name
  • From: Richard Bos
• Re: Compiler Issue
  • From: Richard Heathfield
• Re: coderwiki.com is starting and needs you!
  • From: Chris Dollin
• Re: // vs /*
  • From: Richard Bos
• redefine a function with a same name
  • From: paytam
• Re: coderwiki.com is starting and needs you!
  • From: Richard G. Riley
• Re: Compiler Issue
  • From: Ian Collins
• Re: Wrong output - eliminate spaces in sentence.
  • From: Richard G. Riley
• Re: Compiler Issue
  • From: cyber citizen
• Re: fgets info
  • From: Salvatore Di Fazio
• Re: is it possible to access members of struct in loop?
  • From: Erich Pul
• Re: is it possible to access members of struct in loop?
  • From: Ian Collins
• Re: bit fileds or bit manuplation
  • From: Ian Collins
• Re: Compiler Issue
  • From: spibou
• Re: Compiler Issue
  • From: Ian Collins
• Re: is it possible to access members of struct in loop?
  • From: Gordon Burditt
• Re: What do you think about the code?
  • From: Richard Bos
• Re: strings in #if 0
  • From: Richard Bos
• is it possible to access members of struct in loop?
  • From: Erich Pul
• Re: // vs /*
  • From: Richard G. Riley
• Re: 16-Bit char pointers valid?
  • From: Keith Thompson
• Re: fgets info
  • From: Salvatore Di Fazio
• Re: coderwiki.com is starting and needs you!
  • From: Richard Bos
• Re: fgets info
  • From: Salvatore Di Fazio
• Re: strings in #if 0
  • From: Keith Thompson
• Re: // vs /*
  • From: Richard Bos
• bit fileds or bit manuplation
  • From: surendra
• Compiler Issue
  • From: cyber citizen
• Re: strange use of format specifier in printf
  • From: Peter Nilsson
• Re: 16-Bit char pointers valid?
  • From: Harald van Dijk
• Re: ifdefs
  • From: Your Uncle
• Re: Named parameters
  • From: Bill Pursell
• Re: strange use of format specifier in printf
  • From: Gordon Burditt
• Re: What do you think about the code?
  • From: Bill Pursell
• Re: strings in #if 0
  • From: Neil
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: Andrey Tarasevich
• Re: strange use of format specifier in printf
  • From: Tom St Denis
• Re: strange use of format specifier in printf
  • From: Money
• Re: strange use of format specifier in printf
  • From: Money
• Re: strange use of format specifier in printf
  • From: Andrey Tarasevich
• Re: What do you think about the code?
  • From: Tom St Denis
• Re: strange use of format specifier in printf
  • From: Your Uncle
• Re: What do you think about the code?
  • From: Ian Collins
• Re: strange use of format specifier in printf
  • From: Tom St Denis
• strange use of format specifier in printf
  • From: Money
• Re: What do you think about the code?
  • From: Andrew Poelstra
• Re: Strange malloc problem
  • From: Peter "Shaggy" Haywood
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: x=(x=5,11)
  • From: Barry Schwarz
• Re: sizeof
  • From: CBFalconer
• Re: Unnamed members
  • From: Peter Nilsson
• Re: comparing signed and unsigned integers
  • From: Eric Sosman
• Re: incorrect warning?
  • From: Chris Torek
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: pete
• Re: Unnamed members
  • From: $hiv.....
• Re: What do you think about the code?
  • From: milhous.30@xxxxxxxxx
• Re: Wrong output - eliminate spaces in sentence.
  • From: spibou
• comparing signed and unsigned integers
  • From: Joe Van Dyk
• Re: Unnamed members
  • From: L7
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: pete
• Unnamed members
  • From: Tom Plunket
• Re: sizeof
  • From: pete
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: Andrey Tarasevich
• Re: Wrong output - eliminate spaces in sentence.
  • From: pete
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: sizeof
  • From: CBFalconer
• Re: char * ptr = "hello" and char carray[] = "hello"
  • From: Keith Thompson
• Re: What do you think about the code?
  • From: pete
• char * ptr = "hello" and char carray[] = "hello"
  • From: fei.liu@xxxxxxxxx
• Re: Wrong output - eliminate spaces in sentence.
  • From: spibou
• Re: sizeof
  • From: ozbear
• Re: char confusion
  • From: poodles
• Re: Named parameters
  • From: pete
• Re: Named parameters
  • From: Frederick Gotham
• Re: // vs /*
  • From: Richard Heathfield
• Re: Named parameters
  • From: Keith Thompson
• Re: 16-Bit char pointers valid?
  • From: Keith Thompson
• What do you think about the code?
  • From: jaso
• Re: fgets info
  • From: Keith Thompson
• Re: fgets info
  • From: pete
• Re: Named parameters
  • From: Mark McIntyre
• Re: // vs /*
  • From: Mark McIntyre
• Re: 16-Bit char pointers valid?
  • From: Richard Heathfield
• Re: Program to toggle nth bit in C
  • From: Mark McIntyre
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: ifdefs
  • From: Keith Thompson
• Re: fgets info
  • From: Ben Pfaff
• Re: // vs /*
  • From: CBFalconer
• fgets info
  • From: Salvatore Di Fazio
• Re: 16-Bit char pointers valid?
  • From: pete
• Re: ifdefs
  • From: Ian Collins
• Re: ifdefs
  • From: Default User
• Re: strings in #if 0
  • From: Ben Pfaff
• strings in #if 0
  • From: tedu
• Re: ifdefs
  • From: Ian Collins
• Re: 16-Bit char pointers valid?
  • From: Keith Thompson
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: Template Engine like Smarty
  • From: Ian Collins
• Re: Wrong output - eliminate spaces in sentence.
  • From: spibou
• Re: coderwiki.com is starting and needs you!
  • From: Default User
• Re: ifdefs
  • From: Default User
• Re: sizeof
  • From: Richard G . Riley
• Re: ifdefs
  • From: Keith Thompson
• Re: coderwiki.com is starting and needs you!
  • From: Richard G . Riley
• Re: c source
  • From: pete
• Re: ifdefs
  • From: Your Uncle
• Re: ifdefs
  • From: Roberto Waltman
• Re: ifdefs
  • From: Roberto Waltman
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Re: coderwiki.com is starting and needs you!
  • From: pete
• Re: ifdefs
  • From: Harald van Dijk
• Re: ifdefs
  • From: Walter Roberson
• Re: 16-Bit char pointers valid?
  • From: Harald van Dijk
• Re: suppressing the console window
  • From: jacob navia
• Re: Hi
  • From: Eric Sosman
• Re: 16-Bit char pointers valid?
  • From: Gordon Burditt
• Re: ifdefs
  • From: Walter Roberson
• Re: Strange Segmentation Fault
  • From: Gordon Burditt
• Re: ifdefs
  • From: Your Uncle
• Re: Strange Segmentation Fault
  • From: Walter Roberson
• 16-Bit char pointers valid?
  • From: Frederick Gotham
• Re: Wrong output - eliminate spaces in sentence.
  • From: Nelu
• Re: sizeof
  • From: Frederick Gotham
• Re: Strings, Strings and Damned Strings
  • From: Walter Roberson
• Re: Hi
  • From: Frederick Gotham
• Re: ifdefs
  • From: Walter Roberson
• Re: ifdefs
  • From: Richard Heathfield
• Re: Strange Segmentation Fault
  • From: Ben Pfaff
• Re: Strange Segmentation Fault
  • From: Ben Pfaff
• Re: Strange Segmentation Fault
  • From: Tim Evers
• Re: Strange Segmentation Fault
  • From: Walter Roberson
• Re: Hi
  • From: Frederick Gotham
• Re: Strings, Strings and Damned Strings
  • From: Ben Pfaff
• ifdefs
  • From: Your Uncle
• Re: coderwiki.com is starting and needs you!
  • From: Richard Heathfield
• Strange Segmentation Fault
  • From: Tim Evers
• Re: Hi
  • From: Eric Sosman
• Re: // vs /*
  • From: Rob Thorpe
• Re: function * = void *
  • From: Al Balmer
• Re: sizeof
  • From: Andrew Poelstra
• Re: Hi
  • From: Andrew Poelstra
• Re: Hi
  • From: pnreddy1976
• Re: Hi
  • From: Frederick Gotham
• Hi
  • From: pnreddy1976
• Re: random data in structure - checking for no double values
  • From: Richard Tobin
• Re: suppressing the console window
  • From: Walter Roberson
• [OT] Re: Named parameters
  • From: Clever Monkey
• Re: // vs /*
  • From: Richard Heathfield
• Re: // vs /*
  • From: Kenneth Brody
• Re: // vs /*
  • From: Kenneth Brody
• Re: suppressing the console window
  • From: Simon Biber
• Re: suppressing the console window
  • From: Ulrich Eckhardt
• Re: Read-only string [OT]
  • From: Kenneth Brody
• Re: random data in structure - checking for no double values
  • From: Pofy
• suppressing the console window
  • From: pdmountaineer@xxxxxxxxxxx
• Re: random data in structure - checking for no double values
  • From: Richard Heathfield
• Re: random data in structure - checking for no double values
  • From: Chris Dollin
• Re: random data in structure - checking for no double values
  • From: Pofy
• Re: Read-only string
  • From: Chris Dollin
• Re: Wrong output - eliminate spaces in sentence.
  • From: deepak
• Re: Wrong output - eliminate spaces in sentence.
  • From: CBFalconer
• Re: Read-only string
  • From: pete
• Re: random data in structure - checking for no double values
  • From: Vladimir Oka
• Re: random data in structure - checking for no double values
  • From: Erich Pul
• Re: random data in structure - checking for no double values
  • From: CBFalconer
• Re: Read-only string
  • From: Chris Dollin
• Re: Named parameters
  • From: CBFalconer
• Re: random data in structure - checking for no double values
  • From: Richard Bos
• Re: about declaration of huge matrix in C
  • From: Richard Tobin
• Re: Read-only string
  • From: Rk
• Re: memory related concerns
  • From: pete
• Re: about declaration of huge matrix in C
  • From: Tom St Denis
• Re: near-TeraHertz processors no dream
  • From: xhoster
• Re: random data in structure - checking for no double values
  • From: Vladimir Oka
• Re: Strings, Strings and Damned Strings
  • From: Kenny McCormack
• Re: random data in structure - checking for no double values
  • From: Erich Pul
• Re: random data in structure - checking for no double values
  • From: Richard Heathfield
• Re: random data in structure - checking for no double values
  • From: Vladimir Oka
• Re: FAQ-Question
  • From: Nick Keighley
• Re: Named parameters
  • From: Richard Heathfield
• Re: random data in structure - checking for no double values
  • From: Erich Pul
• Re: sizeof
  • From: $hiv.....
• Re: FAQ-Question
  • From: Dik T. Winter
• Re: FAQ-Question
  • From: Dik T. Winter
• Re: Template Engine like Smarty
  • From: Neurotic
• Re: random data in structure - checking for no double values
  • From: Duncan Muirhead
• Re: random data in structure - checking for no double values
  • From: Erich Pul
• Re: incorrect warning?
  • From: Keith Thompson
• Re: Template Engine like Smarty
  • From: Erich Pul
• Re: Template Engine like Smarty
  • From: Neurotic
• Re: random data in structure - checking for no double values
  • From: Vladimir Oka
• Re: random data in structure - checking for no double values
  • From: Erich Pul
• Re: random data in structure - checking for no double values
  • From: Richard Bos
• Re: FAQ-Question
  • From: Keith Thompson
• Re: FAQ-Question
  • From: Keith Thompson
• Re: Template Engine like Smarty
  • From: Erich Pul
• Re: Template Engine like Smarty
  • From: Neurotic
• Re: Named parameters
  • From: Frederick Gotham
• Re: function * = void *
  • From: Keith Thompson
• Re: Wrong output - eliminate spaces in sentence.
  • From: Vladimir Oka
• Re: FAQ-Question
  • From: Richard Heathfield
• Re: Template Engine like Smarty
  • From: Erich Pul
• Re: Named parameters
  • From: Richard Heathfield
• Re: Template Engine like Smarty
  • From: global
• Re: OT: Re: near-TeraHertz processors no dream
  • From: Richard Heathfield
• Re: about declaration of huge matrix in C
  • From: Richard Heathfield
• Re: about declaration of huge matrix in C
  • From: Richard Heathfield
• Wrong output - eliminate spaces in sentence.
  • From: msundaram . visvanathan
• Re: incorrect warning?
  • From: Duncan Muirhead
• Re: Named parameters
  • From: Frederick Gotham
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: Template Engine like Smarty
  • From: Erich Pul
• Re: regarding memset
  • From: Novice
• Re: near-TeraHertz processors no dream
  • From: CBFalconer
• Template Engine like Smarty
  • From: global
• Re: Named parameters
  • From: jaysome
• Re: FAQ-Question
  • From: CBFalconer
• Re: Named parameters
  • From: Frederick Gotham
• Re: Program to toggle nth bit in C
  • From: CBFalconer
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: memory related concerns
  • From: jaysome
• Re: near-TeraHertz processors no dream
  • From: Frederick Gotham
• Re: which is const in "char *const argv[]"
  • From: Eric
• Re: Named parameters
  • From: Frederick Gotham
• Re: memory related concerns
  • From: "Nils O. Selåsdal"
• Re: function * = void *
  • From: jaysome
• Re: FAQ-Question
  • From: Frederick Gotham
• random data in structure - checking for no double values
  • From: Erich Pul
• memory related concerns
  • From: sam_cit
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: x=(x=5,11)
  • From: google
• Re: function * = void *
  • From: Simon Biber
• Re: function * = void *
  • From: Keith Thompson
• Re: function * = void *
  • From: jaysome
• Re: Program to toggle nth bit in C
  • From: Morris Dovey
• Re: Strings, Strings and Damned Strings
  • From: Ben
• Re: Strings, Strings and Damned Strings
  • From: Bill Pursell
• Re: Copy 4 byte block into a char array
  • From: "Nils O. Selåsdal"
• Re: FAQ-Question
  • From: Barry Schwarz
• Re: Program to toggle nth bit in C
  • From: Barry Schwarz
• Re: regarding memset
  • From: Novice
• Re: Strings, Strings and Damned Strings
  • From: Ben
• Re: Program to toggle nth bit in C
  • From: Walter Roberson
• Re: Strings, Strings and Damned Strings
  • From: Dann Corbit
• Re: Strings, Strings and Damned Strings
  • From: Dann Corbit
• Re: Strings, Strings and Damned Strings
  • From: santosh
• Re: Strings, Strings and Damned Strings
  • From: doug turnbull
• Strings, Strings and Damned Strings
  • From: Ben
• Re: Copy 4 byte block into a char array
  • From: CBFalconer
• Re: Program to toggle nth bit in C
  • From: Andrew Poelstra
• Re: c source
  • From: Arild Hystad
• Re: FAQ-Question
  • From: Keith Thompson
• Re: Copy 4 byte block into a char array
  • From: Barry Schwarz
• Re: Copy 4 byte block into a char array
  • From: Barry Schwarz
• Re: Bit field arrays unsupported?
  • From: pete
• OT: Re: near-TeraHertz processors no dream
  • From: jjf
• Re: FAQ-Question
  • From: Barry Schwarz
• Re: Program to toggle nth bit in C
  • From: Barry Schwarz
• Re: about declaration of huge matrix in C
  • From: Richard Tobin
• Re: x=(x=5,11)
  • From: Barry Schwarz
• Re: Named parameters
  • From: Martin Ambuhl
• Re: about declaration of huge matrix in C
  • From: Keith Thompson
• Re: about declaration of huge matrix in C
  • From: Tom St Denis
• Re: about declaration of huge matrix in C
  • From: Keith Thompson
• Re: about declaration of huge matrix in C
  • From: Tom St Denis
• Re: // vs /*
  • From: Richard Heathfield
• Re: // vs /*
  • From: Richard Heathfield
• Re: about declaration of huge matrix in C
  • From: Sjouke Burry
• Re: Program to toggle nth bit in C
  • From: Andrew Poelstra
• Re: // vs /*
  • From: Andrew Poelstra
• Re: sizeof
  • From: Richard Tobin
• Re: Read-only string
  • From: Mark McIntyre
• Re: // vs /*
  • From: Mark McIntyre
• Re: Program to toggle nth bit in C
  • From: Mark McIntyre
• Re: // vs /*
  • From: Keith Thompson
• Re: // vs /*
  • From: Andrew Poelstra
• Re: Copy 4 byte block into a char array
  • From: Keith Thompson
• Re: Bit field arrays unsupported?
  • From: Harald van Dijk
• Re: Copy 4 byte block into a char array
  • From: Tom St Denis
• Re: Bit field arrays unsupported?
  • From: Keith Thompson
• Re: Copy 4 byte block into a char array
  • From: James
• Re: Copy 4 byte block into a char array
  • From: Stephen Sprunk
• Re: // vs /*
  • From: Richard Heathfield
• Re: // vs /*
  • From: Harald van Dijk
• Re: // vs /*
  • From: Richard Heathfield
• Re: function * = void *
  • From: Keith Thompson
• Re: Named parameters
  • From: Clever Monkey
• Re: sscanf'ing floats into structure members
  • From: Keith Thompson
• Re: // vs /*
  • From: Ben Pfaff
• Re: // vs /*
  • From: Bill Pursell
• Re: Program to toggle nth bit in C
  • From: Keith Thompson
• Re: Copy 4 byte block into a char array
  • From: Nelu
• Re: about declaration of huge matrix in C
  • From: Keith Thompson
• Re: // vs /*
  • From: Richard Heathfield
• Re: Read-only string [OT]
  • From: Chris Torek
• Re: // vs /*
  • From: Keith Thompson
• Re: // vs /*
  • From: Keith Thompson
• Re: // vs /*
  • From: Keith Thompson
• Re: incorrect warning?
  • From: Keith Thompson
• Re: sizeof
  • From: CBFalconer
• Re: Named parameters
  • From: Malcolm
• Re: Copy 4 byte block into a char array
  • From: Tom St Denis
• Copy 4 byte block into a char array
  • From: bg_ie
• Re: // vs /*
  • From: Bill Pursell
• Re: Read-only string
  • From: Keith Thompson
• Re: sscanf'ing floats into structure members
  • From: Eric Sosman
• Re: Named parameters
  • From: Eric Sosman
• Re: sscanf'ing floats into structure members
  • From: Michael Mair
• Re: FAQ-Question
  • From: Keith Thompson
• Re: Named parameters
  • From: William Ahern
• Re: dependency checking
  • From: Michael Mair
• Re: function * = void *
  • From: William Ahern
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: function * = void *
  • From: Bill Pursell
• Re: function * = void *
  • From: Bill Pursell
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: Bit field arrays unsupported?
  • From: Harald van Dijk
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: sizeof
  • From: tedu
• dependency checking
  • From: Weiguang Shi
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: Read-only string
  • From: Andrew Poelstra
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: function * = void *
  • From: Gordon Burditt
• Re: // vs /*
  • From: Ryan Reich
• Re: function * = void *
  • From: Ben Pfaff
• Re: Named parameters
  • From: Ben Pfaff
• function * = void *
  • From: Bill Pursell
• sscanf'ing floats into structure members
  • From: Bernard Liang
• Named parameters
  • From: Bill Pursell
• Re: Read-only string [OT]
  • From: Richard Heathfield
• Re: // vs /*
  • From: Kenneth Brody
• Re: OT: [Re: near-TeraHertz processors no dream]
  • From: Tom St Denis
• Re: char confusion
  • From: Kenneth Brody
• Re: Read-only string [OT]
  • From: Kenneth Brody
• Re: char confusion
  • From: poodles
• Re: Program to toggle nth bit in C
  • From: Walter Roberson
• Re: OT: [Re: near-TeraHertz processors no dream]
  • From: Walter Roberson
• Re: about declaration of huge matrix in C
  • From: Richard Heathfield
• Re: Can We Read Text data From an EXE
  • From: Kenny McCormack
• Re: sizeof
  • From: Richard Tobin
• Re: sizeof
  • From: Richard Tobin
• Re: // vs /*
  • From: Ryan Reich
• Re: to access the large page(2112 bytes) NAND Flash from the bootloader
  • From: Morris Dovey
• Re: about declaration of huge matrix in C
  • From: Tom St Denis
• Re: about declaration of huge matrix in C
  • From: Eric Sosman
• OT: [Re: near-TeraHertz processors no dream]
  • From: Tom St Denis
• about declaration of huge matrix in C
  • From: luke.yolanda@xxxxxxxxx
• Re: about declaration of huge matrix in C
  • From: Marc Boyer
• Re: to access the large page(2112 bytes) NAND Flash from the bootloader
  • From: Tom St Denis
• to access the large page(2112 bytes) NAND Flash from the bootloader
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: near-TeraHertz processors no dream
  • From: v4vijayakumar
• near-TeraHertz processors no dream
  • From: v4vijayakumar
• Re: // vs /*
  • From: Tom St Denis
• Re: // vs /*
  • From: Kenny McCormack
• Re: char confusion
  • From: Harald van Dijk
• Re: esoteric C stuff, what is "debug_flag"??
  • From: syn1kk
• Re: char confusion
  • From: Kenneth Brody
• Re: Can We Read Text data From an EXE
  • From: Tom St Denis
• Re: Can We Read Text data From an EXE
  • From: sonofsun
• Re: Read-only string
  • From: Kenneth Brody
• Re: char confusion
  • From: Vladimir Oka
• Re: char confusion
  • From: Bart Rider
• Re: Read-only string [OT]
  • From: "Nils O. Selåsdal"
• Re: // vs /*
  • From: Christopher Benson-Manica
• Re: sizeof
  • From: Kenneth Brody
• Re: char confusion
  • From: Vladimir Oka
• Re: Can We Read Text data From an EXE
  • From: Walter Roberson
• Re: // vs /*
  • From: Joe Van Dyk
• Re: // vs /*
  • From: Joe Van Dyk
• Re: which is const in "char *const argv[]"
  • From: Dik T. Winter
• char confusion
  • From: poodles
• Re: Read-only string
  • From: Vladimir Oka
• Re: Read-only string
  • From: Vladimir Oka
• Re: sizeof
  • From: CBFalconer
• Re: Read-only string
  • From: Marc Thrun
• Re: Read-only string
  • From: Richard Bos
• Re: Read-only string
  • From: Richard Bos
• Re: // vs /*
  • From: Richard Bos
• Re: // vs /*
  • From: Kenny McCormack
• Re: Read-only string
  • From: Marc Boyer
• Re: Bit field arrays unsupported?
  • From: pete
• Re: data mining
  • From: pemo
• Re: Read-only string
  • From: v4vijayakumar
• Re: Read-only string
  • From: v4vijayakumar
• Re: data mining
  • From: Vladimir Oka
• Re: Assembly problem
  • From: Ben C
• data mining
  • From: vmishra85@xxxxxxxxx
• Re: permutation generation
  • From: lovecreatesbeauty
• Re: // vs /*
  • From: Nick Keighley
• Re: Read-only string
  • From: Marc Boyer
• Re: // vs /*
  • From: Kenny McCormack
• Re: which is const in "char *const argv[]"
  • From: lovecreatesbeauty
• Re: Read-only string
  • From: "Nils O. Selåsdal"
• Re: x=(x=5,11)
  • From: google
• Re: Read-only string
  • From: Vladimir Oka
• Re: incorrect warning?
  • From: Duncan Muirhead
• Re: sizeof
  • From: Ben C
• Re: permutation generation
  • From: Richard Heathfield
• Re: permutation generation
  • From: Richard Heathfield
• Re: sizeof
  • From: CBFalconer
• Re: // vs /*
  • From: Richard Heathfield
• Re: which is const in "char *const argv[]"
  • From: Harald van Dijk
• Re: which is const in "char *const argv[]"
  • From: lovecreatesbeauty
• Re: permutation generation
  • From: Jean-Marc Bourguet
• Read-only string
  • From: v4vijayakumar
• Re: Lex Question
  • From: Chris Dollin
• Re: sizeof
  • From: Richard Bos
• Re: sizeof
  • From: Ben C
• XOR
  • From: Neil
• Re: enum question
  • From: jaysome
• Re: sizeof
  • From: Richard Bos
• Re: Really basic..
  • From: Richard Bos
• Re: K&R exercise 1-18
  • From: Harald van Dijk
• Re: // vs /*
  • From: Keith Thompson
• Re: Assembly problem
  • From: jaysome
• Assembly problem
  • From: bilaribilari
• Re: can someone tell me if I'm going insane.
  • From: Old Wolf
• Re: // vs /*
  • From: Bill Pursell
• Re: // vs /*
  • From: Zara
• Re: can someone tell me if I'm going insane.
  • From: Barry Schwarz
• Re: FAQ-Question
  • From: Keith Thompson
• Re: Bit field arrays unsupported?
  • From: Old Wolf
• Re: Program to toggle nth bit in C
  • From: Old Wolf
• Re: // vs /*
  • From: Tim Prince
• Re: Program to toggle nth bit in C
  • From: Old Wolf
• Re: FAQ-Question
  • From: Keith Thompson
• Re: enum question
  • From: ramu
• Re: FAQ-Question
  • From: Old Wolf
• Re: // vs /*
  • From: CBFalconer
• Re: why this code dumps core?
  • From: Charles Richmond
• Re: FAQ-Question
  • From: Keith Thompson
• Re: permutation generation
  • From: Peter "Shaggy" Haywood
• Re: K&R exercise 1-18
  • From: Joe Van Dyk
• Re: // vs /*
  • From: CBFalconer
• Re: FAQ-Question
  • From: CBFalconer
• Re: Program to toggle nth bit in C
  • From: Keith Thompson
• enum question
  • From: Joe Van Dyk
• Re: Program to toggle nth bit in C
  • From: CBFalconer
• Re: Bit field arrays unsupported?
  • From: Jack Klein
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: // vs /*
  • From: Joe Van Dyk
• Re: permutation generation
  • From: CBFalconer
• Re: FAQ-Question
  • From: Jack Klein
• Re: K&R exercise 1-18
  • From: Eric
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: Program to toggle nth bit in C
  • From: Keith Thompson
• Re: sizeof
  • From: Keith Thompson
• Re: FAQ-Question
  • From: Robert Gamble
• Re: FAQ-Question
  • From: Robert Gamble
• Re: Bit field arrays unsupported?
  • From: pete
• Re: K&R exercise 1-18
  • From: pete
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: // vs /*
  • From: Robert Gamble
• Re: K&R exercise 1-18
  • From: Eric
• Re: permutation generation
  • From: lovecreatesbeauty
• Re: Bit field arrays unsupported?
  • From: pete
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: permutation generation
  • From: lovecreatesbeauty
• // vs /*
  • From: Joe Van Dyk
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: Bit field arrays unsupported?
  • From: Frederick Gotham
• Re: FAQ-Question
  • From: jjf
• Re: Malloc for array of string
  • From: Barry Schwarz
• Re: K&R exercise 1-18
  • From: Michael Mair
• Re: x=(x=5,11)
  • From: Barry Schwarz
• Re: FAQ-Question
  • From: dcorbit
• Re: Program to toggle nth bit in C
  • From: pete
• Re: FAQ-Question
  • From: Dann Corbit
• Re: Bit field arrays unsupported?
  • From: Michael Mair
• Re: Bit field arrays unsupported?
  • From: Dann Corbit
• Re: FAQ-Question
  • From: Keith Thompson
• Re: FAQ-Question
  • From: Dann Corbit
• Bit field arrays unsupported?
  • From: ballpointpenthief
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: FAQ-Question
  • From: Jack Klein
• Re: Program to toggle nth bit in C
  • From: Ben C
• Re: I need C complier.
  • From: Quas.co.ua
• Re: I need C complier.
  • From: Quas.co.ua
• Re: Program to toggle nth bit in C
  • From: Walter Roberson
• Re: I need C complier.
  • From: William Ahern
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• Re: Educated guesses for efficiency?
  • From: Richard Heathfield
• Re: sizeof
  • From: tedu
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Strange malloc problem
  • From: Quas.co.ua
• Re: FAQ-Question
  • From: Frederick Gotham
• Re: I need C complier.
  • From: Dann Corbit
• Re: Educated guesses for efficiency?
  • From: xhoster
• Re: FAQ-Question
  • From: Robert Gamble
• I need C complier.
  • From: Quas.co.ua
• Re: why this code dumps core?
  • From: Keith Thompson
• Re: FAQ-Question
  • From: Christopher Benson-Manica
• Re: sizeof
  • From: Keith Thompson
• Re: FAQ-Question
  • From: Dann Corbit
• Re: FAQ-Question
  • From: Robert Gamble
• FAQ-Question
  • From: Till Crueger
• Re: "Numerical Recipes in C" code
  • From: Dann Corbit
• Re: which is const in "char *const argv[]"
  • From: John Bode
• Re: why this code dumps core?
  • From: Martin Ambuhl
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Really basic..
  • From: Keith Thompson
• Re: can someone tell me if I'm going insane.
  • From: Keith Thompson
• Re: Really basic..
  • From: Frederick Gotham
• Re: incorrect warning?
  • From: Harald van Dijk
• Re: incorrect warning?
  • From: Keith Thompson
• Re: Program to toggle nth bit in C
  • From: CBFalconer
• Re: incorrect warning?
  • From: Chris Torek
• Re: incorrect warning?
  • From: Richard Heathfield
• Re: mxFree
  • From: Martin Jørgensen
• Re: Macros and Variables
  • From: Cristian . D . Guajardo
• Re: Really basic..
  • From: August Karlstrom
• Re: incorrect warning?
  • From: parcour@xxxxxxxxx
• Re: Macros and Variables
  • From: Eric Sosman
• Re: can someone tell me if I'm going insane.
  • From: Frederick Gotham
• Re: Lex Question
  • From: David Shin
• Re: sizeof
  • From: Kenneth Brody
• Re: Macros and Variables
  • From: Cristian . D . Guajardo
• Re: Lex Question
  • From: Keith Thompson
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• Re: Lex Question
  • From: Vladimir Oka
• Lex Question
  • From: David Shin
• Lex Question
  • From: David Shin
• Re: Macros and Variables
  • From: Vladimir Oka
• Re: can someone tell me if I'm going insane.
  • From: thomas.luce@xxxxxxxxx
• Re: permutation generation
  • From: Keith Thompson
• Re: can someone tell me if I'm going insane.
  • From: Eric Sosman
• Re: c------->c++ and c++------>c
  • From: Default User
• Re: why this code dumps core?
  • From: Nelu
• Macros and Variables
  • From: Cristian . D . Guajardo
• can someone tell me if I'm going insane.
  • From: thomas . luce
• Re: convert a float to a short
  • From: Keith Thompson
• Re: Program to toggle nth bit in C
  • From: Ben C
• Re: why this code dumps core?
  • From: Keith Thompson
• Re: sizeof
  • From: Keith Thompson
• incorrect warning?
  • From: Duncan Muirhead
• Re: Program to toggle nth bit in C
  • From: Frederick Gotham
• Re: mxFree
  • From: Nelu
• Re: problem about function pointer
  • From: Betaver
• Re: convert a float to a short
  • From: Partho
• Re: mxFree
  • From: Christopher Benson-Manica
• Re: Strange malloc problem
  • From: Me
• Re: mxFree
  • From: Nelu
• Re: Is the behaviour of * operator an example of operator oveloading in c?
  • From: karthik
• Re: why this code dumps core?
  • From: Nelu
• Re: permutation generation
  • From: lovecreatesbeauty
• Re: x=(x=5,11)
  • From: google
• Re: Strange malloc problem
  • From: Vladimir Oka
• Re: Strange malloc problem
  • From: Me
• Re: Strange malloc problem
  • From: Chris Dollin
• Re: Strange malloc problem
  • From: Me
• Re: sizeof
  • From: Kenneth Brody
• Re: Program to toggle nth bit in C
  • From: Chris Dollin
• Re: Strange malloc problem
  • From: pemo
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Program to toggle nth bit in C
  • From: Vladimir Oka
• Re: Program to toggle nth bit in C
  • From: pete
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• Re: mxFree
  • From: Christopher Hulbert
• Re: Program to toggle nth bit in C
  • From: Eric Sosman
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• Re: Program to toggle nth bit in C
  • From: Andre Reffhaug
• Re: Strange malloc problem
  • From: Vladimir Oka
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• mxFree
  • From: dkumar142
• Re: Program to toggle nth bit in C
  • From: Ian Malone
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: Subtracting unsigned ints
  • From: Eric Sosman
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: Program to toggle nth bit in C
  • From: Chris Dollin
• Re: Program to toggle nth bit in C
  • From: Andre Reffhaug
• Strange malloc problem
  • From: Me
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: Program to toggle nth bit in C
  • From: Richard Heathfield
• Re: Malloc for array of string
  • From: "Nils O. Selåsdal"
• Malloc for array of string
  • From: dkumar142
• Re: Program to toggle nth bit in C
  • From: nsimeonov
• Re: permutation generation
  • From: lovecreatesbeauty
• Re: "Numerical Recipes in C" code
  • From: micans
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: "Numerical Recipes in C" code
  • From: Keith Thompson
• Re: K&R exercise 1-18
  • From: Richard Heathfield
• Re: sizeof
  • From: Chris Dollin
• Re: why this code dumps core?
  • From: Ian Collins
• why this code dumps core?
  • From: v4vijayakumar
• Re: Is the behaviour of * operator an example of operator oveloading in c?
  • From: Michael Mair
• Re: which is const in "char *const argv[]"
  • From: Michael Mair
• Re: Subtracting unsigned ints
  • From: Peter Nilsson
• Re: Is the behaviour of * operator an example of operator oveloading in c?
  • From: Peter Nilsson
• Re: "Numerical Recipes in C" code
  • From: jaysome
• Re: K&R exercise 1-18
  • From: Peter Nilsson
• Is the behaviour of * operator an example of operator oveloading in c?
  • From: karthik
• Re: Program to toggle nth bit in C
  • From: Peter Nilsson
• Re: K&R exercise 1-18
  • From: Eric
• Program to toggle nth bit in C
  • From: sksoule
• Re: "Numerical Recipes in C" code
  • From: Abhi
• Re: K&R exercise 1-18
  • From: qiangchen81
• Re: Subtracting unsigned ints
  • From: CBFalconer
• which is const in "char *const argv[]"
  • From: Eric
• Re: Subtracting unsigned ints
  • From: Nelu
• Re: permutation generation
  • From: Dann Corbit
• Re: Subtracting unsigned ints
  • From: Jack Klein
• K&R exercise 1-18
  • From: Eric
• Re: who had used pclint for amcc?
  • From: Jack Klein
• Re: Subtracting unsigned ints
  • From: pete
• Re: Subtracting unsigned ints
  • From: Eric Sosman
• Re: permutation generation
  • From: Peter Nilsson
• Re: a little mistake
  • From: Old Wolf
• Re: Subtracting unsigned ints
  • From: Nelu
• Re: Subtracting unsigned ints
  • From: Peter Nilsson
• Re: sentence
  • From: pete
• Re: Subtracting unsigned ints
  • From: Ian Collins
• Subtracting unsigned ints
  • From: bg_ie
• Re: sizeof
  • From: Keith Thompson
• Re: sizeof
  • From: Ian Collins
• Re: sizeof
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: Barry Schwarz
• Re: sizeof
  • From: Joe Wright
• Re: sizeof
  • From: Andrew Poelstra
• Re: sizeof
  • From: Malcolm
• Re: any info on graphs algorithms examples ?
  • From: Malcolm
• Re: any info on graphs algorithms examples ?
  • From: Robert Gamble
• Re: sentence
  • From: av
• Re: a little mistake
  • From: av
• Re: permutation generation
  • From: Michael Mair
• Re: coin toss problem
  • From: Mark McIntyre
• Re: sizeof 'a' returns 4
  • From: Mark McIntyre
• Re: sizeof 'a' returns 4
  • From: Mark McIntyre
• Re: a little mistake
  • From: Keith Thompson
• Re: problem about function pointer
  • From: CBFalconer
• Re: any info on graphs algorithms examples ?
  • From: CBFalconer
• Re: "Numerical Recipes in C" code
  • From: David Wade
• Re: sentence
  • From: CBFalconer
• Re: a little mistake
  • From: CBFalconer
• Re: a little mistake
  • From: CBFalconer
• Re: a little mistake
  • From: CBFalconer
• Re: permutation generation
  • From: Bill Pursell
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: a little mistake
  • From: Kenneth Brody
• Re: a little mistake
  • From: Frederick Gotham
• Re: sizeof
  • From: Skarmander
• Re: esoteric C stuff, what is "debug_flag"??
  • From: Walter Roberson
• Re: Reference
  • From: parcour@xxxxxxxxx
• Re: sentence
  • From: Martin Jørgensen
• esoteric C stuff, what is "debug_flag"??
  • From: syn1kk
• Re: permutation generation
  • From: Richard Heathfield
• Re: opensolaris C library vs. GNU C Library
  • From: websnarf
• Re: a little mistake
  • From: Tom St Denis
• Re: a little mistake
  • From: Kenny McCormack
• Re: problem about function pointer
  • From: kleuske
• Re: permutation generation
  • From: lovecreatesbeauty
• Re: any info on graphs algorithms examples ?
  • From: Robert Gamble
• problem about function pointer
  • From: neilcancer@xxxxxxxxx
• Re: a little mistake
  • From: Richard Heathfield
• Re: a little mistake
  • From: Richard Heathfield
• Re: convert a float to a short
  • From: John Smith
• Re: a little mistake
  • From: Kenny McCormack
• Re: a little mistake
  • From: Richard Heathfield
• Re: a little mistake
  • From: Tom St Denis
• Re: a little mistake
  • From: Andrew Poelstra
• Re: a little mistake
  • From: Tom St Denis
• any info on graphs algorithms examples ?
  • From: johnny
• Re: Why occur the mistake in runtime about strtok()?
  • From: John Bode
• Re: a little mistake
  • From: Richard Bos
• Re: Why occur the mistake in runtime about strtok()?
  • From: CBFalconer
• Re: a little mistake
  • From: CBFalconer
• Re: Why occur the mistake in runtime about strtok()?
  • From: Chris Dollin
• Re: c source
  • From: Morris Dovey
• Re: a little mistake
  • From: Frederick Gotham
• Re: Why occur the mistake in runtime about strtok()?
  • From: pete
• Re: a little mistake
  • From: Richard Heathfield
• Re: convert a float to a short
  • From: pete
• Re: C Pointer problem
  • From: pete
• Re: a little mistake
  • From: Richard Bos
• Re: a little mistake
  • From: Tom St Denis
• Re: convert a float to a short
  • From: Keith Thompson
• Re: how to deal with this problem
  • From: Richard Bos
• Re: permutation generation
  • From: spibou
• Re: convert a float to a short
  • From: Ian Collins
• Re: convert a float to a short
  • From: Chris Dollin
• convert a float to a short
  • From: Partho
• Re: How to decide whether it is an English letter or a number?
  • From: CBFalconer
• Re: c source
  • From: CBFalconer
• Re: types of 'Open' command
  • From: Richard Bos
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: Chris McDonald
• Re: Educated guesses for efficiency?
  • From: CBFalconer
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: Richard Bos
• Re: sentence
  • From: av
• Re: How to decide whether it is an English letter or a number?
  • From: Richard Bos
• Re: learning C with a C++ background
  • From: Ian Collins
• Re: Educated guesses for efficiency?
  • From: Chris Dollin
• Re: permutation generation
  • From: Richard Heathfield
• Re: permutation generation
  • From: pemo
• Re: cast from function call of type int to non-matching type double
  • From: CBFalconer
• Re: Problem with graphics
  • From: Richard Heathfield
• Re: a little mistake
  • From: Richard Heathfield
• Re: c source
  • From: Richard Heathfield
• permutation generation
  • From: onkar
• Problem with graphics
  • From: rchitra . r
• Re: sizeof
  • From: lovecreatesbeauty
• Re: sizeof 'a' returns 4
  • From: Richard Heathfield
• Re: sizeof
  • From: Richard Heathfield
• Re: sizeof 'a' returns 4
  • From: Harald van Dijk
• Re: a little mistake
  • From: Tom St Denis
• Re: coin toss problem
  • From: Richard Heathfield
• Re: c source
  • From: sathyashrayan
• Re: coin toss problem
  • From: Richard Heathfield
• Re: segmentation fault
  • From: jussij
• Re: cast from function call of type int to non-matching type double
  • From: Richard Heathfield
• Re: Calling macros from outside the definition
  • From: Ben
• Re: a little mistake
  • From: lovecreatesbeauty
• Re: sentence
  • From: av
• Re: sizeof
  • From: Barry Schwarz
• Re: segmentation fault
  • From: Barry Schwarz
• Re: sizeof
  • From: Keith Thompson
• Re: coin toss problem
  • From: Keith Thompson
• Re: a little mistake
  • From: Peter Nilsson
• Re: c source
  • From: Andrew Poelstra
• Re: learning C with a C++ background
  • From: Stephen Sprunk
• Re: sizeof
  • From: Dave Vandervies
• Re: sizeof
  • From: lovecreatesbeauty
• Re: sizeof 'a' returns 4
  • From: Old Wolf
• Re: sizeof 'a' returns 4
  • From: lovecreatesbeauty
• Re: opensolaris C library vs. GNU C Library
  • From: Dave Thompson
• Re: #define p
  • From: Dave Thompson
• Re: How to decide whether it is an English letter or a number?
  • From: Dave Thompson
• Re: C Pointer problem
  • From: Dave Thompson
• Re: sizeof
  • From: Dave Vandervies
• Re: knowing exact string array length ?
  • From: CBFalconer
• Re: sizeof
  • From: lovecreatesbeauty
• Re: The performance of all kinds of C operations
  • From: Dave Vandervies
• Re: coin toss problem
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: Eric Sosman
• Re: sizeof
  • From: ada
• Re: wit's end
  • From: Old Wolf
• who had used pclint for amcc?
  • From: saspt
• Re: coin toss problem
  • From: Eric Sosman
• Re: a little mistake
  • From: lovecreatesbeauty
• c source
  • From: fegge
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: Old Wolf
• Re: sizeof
  • From: pete
• Re: sizeof 'a' returns 4
  • From: Old Wolf
• Re: Pointers
  • From: Barry Schwarz
• Re: sizeof 'a' returns 4
  • From: Dik T. Winter
• Re: coin toss problem
  • From: Old Wolf
• Re: knowing exact string array length ?
  • From: Barry Schwarz
• Re: sizeof 'a' returns 4
  • From: Barry Schwarz
• Re: sizeof 'a' returns 4
  • From: Nelu
• Re: "Numerical Recipes in C" code
  • From: Nelu
• Re: coin toss problem
  • From: Old Wolf
• Re: coin toss problem
  • From: Old Wolf
• Re: code hangs
  • From: spibou
• Re: cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: coin toss problem
  • From: Ben C
• Re: cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: r- r-value vs l-value?
  • From: Ben C
• Re: Memory (read) access violation handling in C
  • From: spibou
• Re: sizeof 'a' returns 4
  • From: Kenny McCormack
• Re: sizeof 'a' returns 4
  • From: Kenny McCormack
• Re: coin toss problem
  • From: Keith Thompson
• Re: The performance of all kinds of C operations
  • From: spibou
• "Numerical Recipes in C" code
  • From: Abhi
• Re: clc-wiki gone?
  • From: Netocrat
• Re: cast from function call of type int to non-matching type double
  • From: Richard Heathfield
• Re: sizeof
  • From: Richard Heathfield
• Re: Printing "tab"
  • From: Jordan Abel
• Re: The performance of all kinds of C operations
  • From: Stephen Sprunk
• Re: sizeof 'a' returns 4
  • From: Default User
• Re: sizeof 'a' returns 4
  • From: Keith Thompson
• Re: coin toss problem
  • From: Keith Thompson
• Re: cast from function call of type int to non-matching type double
  • From: Keith Thompson
• Re: sizeof 'a' returns 4
  • From: Simon Lewis
• Re: sizeof 'a' returns 4
  • From: Keith Thompson
• Re: sizeof 'a' returns 4
  • From: Keith Thompson
• Re: a little mistake
  • From: Keith Thompson
• Re: Pointers
  • From: Keith Thompson
• Re: sizeof
  • From: Keith Thompson
• Re: Memory (read) access violation handling in C
  • From: Keith Thompson
• Re: The performance of all kinds of C operations
  • From: Keith Thompson
• Re: Value Bits Vs Object Bits
  • From: Hallvard B Furuseth
• Re: sizeof
  • From: Xicheng Jia
• Re: segmentation fault
  • From: pemo
• Re: a little mistake
  • From: CBFalconer
• Re: cast from function call of type int to non-matching type double
  • From: Barry Schwarz
• Re: cast from function call of type int to non-matching type double
  • From: Barry Schwarz
• Re: knowing exact string array length ?
  • From: Barry Schwarz
• Re: cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: knowing exact string array length ?
  • From: Joe Estock
• Re: knowing exact string array length ?
  • From: Joe Estock
• Re: sizeof 'a' returns 4
  • From: Kenny McCormack
• Re: a little mistake
  • From: Frederick Gotham
• Re: sizeof
  • From: Andrew Poelstra
• Re: segmentation fault
  • From: Andrew Poelstra
• Re: a little mistake
  • From: Barry Schwarz
• Re: sizeof 'a' returns 4
  • From: Frederick Gotham
• Re: coin toss problem
  • From: Andrew Poelstra
• Re: sizeof 'a' returns 4
  • From: Kenny McCormack
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Kenny McCormack
• Re: Pointers
  • From: lovecreatesbeauty
• Re: sizeof
  • From: Frederick Gotham
• Re: cast from function call of type int to non-matching type double
  • From: Jack Klein
• Re: sizeof
  • From: Marc Thrun
• Re: Managed String Library
  • From: Malcolm
• Re: sizeof
  • From: lovecreatesbeauty
• Re: sizeof
  • From: Frederick Gotham
• Re: sizeof
  • From: Malcolm
• Re: sizeof
  • From: Xicheng Jia
• Re: sizeof 'a' returns 4
  • From: Frederick Gotham
• Re: Pointers
  • From: Richard Heathfield
• Re: a little mistake
  • From: Frederick Gotham
• Re: sizeof 'a' returns 4
  • From: Richard Heathfield
• Re: sizeof
  • From: Richard Heathfield
• Re: Pointers
  • From: lovecreatesbeauty
• Re: sizeof 'a' returns 4
  • From: lovecreatesbeauty
• Re: code hangs
  • From: Andrew Poelstra
• Re: sizeof
  • From: Madhav
• Re: copying a 2-dimension array into another
  • From: Nelu
• Re: segmentation fault
  • From: CBFalconer
• copying a 2-dimension array into another
  • From: johnny
• Re: a little mistake
  • From: Tom St Denis
• Re: sizeof 'a' returns 4
  • From: Richard Heathfield
• Re: The performance of all kinds of C operations
  • From: CBFalconer
• Re: code hangs
  • From: mdh
• Re: Pointers
  • From: Xicheng Jia
• Re: code hangs
  • From: Xicheng Jia
• Re: sizeof 'a' returns 4
  • From: Frederick Gotham
• Re: a little mistake
  • From: Frederick Gotham
• Re: Educated guesses for efficiency?
  • From: Eric Sosman
• code hangs
  • From: mdh
• Re: sizeof
  • From: Richard Heathfield
• Re: Pointers
  • From: pete
• Re: Memory (read) access violation handling in C
  • From: pete
• sizeof
  • From: pnreddy1976
• Re: segmentation fault
  • From: Piotr S.
• Memory (read) access violation handling in C
  • From: Bit byte
• Re: segmentation fault
  • From: rrs . matrix
• segmentation fault
  • From: Piotr S.
• Re: The performance of all kinds of C operations
  • From: jacob navia
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: knowing exact string array length ?
  • From: Keith Thompson
• Re: Managed String Library
  • From: jacob navia
• Re: Educated guesses for efficiency?
  • From: jacob navia
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: Pointers
  • From: Malcolm
• Re: Managed String Library
  • From: Malcolm
• Re: cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: knowing exact string array length ?
  • From: Richard Heathfield
• Re: sentence
  • From: Malcolm
• Re: Pointers
  • From: Richard Heathfield
• Re: sizeof 'a' returns 4
  • From: Richard Heathfield
• Re: cast from function call of type int to non-matching type double
  • From: Richard Heathfield
• Re: cast from function call of type int to non-matching type double
  • From: Keith Thompson
• Re: a variable use of variables is what i'm after i think
  • From: Chris Torek
• Re: sizeof 'a' returns 4
  • From: Sidhu
• Pointers
  • From: Sidhu
• Re: sizeof 'a' returns 4
  • From: lnitsu
• Re: sizeof 'a' returns 4
  • From: Xicheng Jia
• Re: knowing exact string array length ?
  • From: johnny
• sizeof 'a' returns 4
  • From: lnitsu
• Re: coin toss problem
  • From: Ben
• Re: cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: Really basic..
  • From: Barry Schwarz
• Re: Educated guesses for efficiency?
  • From: Malcolm
• Re: cast from function call of type int to non-matching type double
  • From: Robert Gamble
• Re: knowing exact string array length ?
  • From: Malcolm
• Re: cast from function call of type int to non-matching type double
  • From: Nelu
• Re: Why occur the mistake in runtime about strtok()?
  • From: Keith Thompson
• Re: how to deal with this problem
  • From: Keith Thompson
• Re: knowing exact string array length ?
  • From: Keith Thompson
• Re: Why occur the mistake in runtime about strtok()?
  • From: Ian Collins
• Re: how to deal with this problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Charles Richmond
• cast from function call of type int to non-matching type double
  • From: Martin Jørgensen
• Re: a little mistake
  • From: lovecreatesbeauty
• how to deal with this problem
  • From: dchen
• Re: Printing "tab"
  • From: Joe Wright
• Re: Question about the *= (and similar) operator
  • From: Joe Wright
• Re: knowing exact string array length ?
  • From: Barry Schwarz
• Re: Really basic..
  • From: Richard Heathfield
• Re: knowing exact string array length ?
  • From: Barry Schwarz
• Re: coin toss problem
  • From: Richard Heathfield
• Re: Really basic..
  • From: Barry Schwarz
• Re: coin toss problem
  • From: Ian Collins
• Re: Really basic..
  • From: Barry Schwarz
• Re: Really basic..
  • From: Frederick Gotham
• Re: wit's end
  • From: Kenny McCormack
• Re: coin toss problem
  • From: pete
• Re: coin toss problem
  • From: Richard Heathfield
• Re: coin toss problem
  • From: Richard Heathfield
• Re: Really basic..
  • From: Ian Collins
• Re: Really basic..
  • From: August Karlstrom
• Re: coin toss problem
  • From: Ben Pfaff
• Re: Educated guesses for efficiency?
  • From: Ben Pfaff
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Keith Thompson
• Re: r- r-value vs l-value?
  • From: Ian Collins
• Re: coin toss problem
  • From: Ben C
• Re: coin toss problem
  • From: CBFalconer
• Re: r- r-value vs l-value?
  • From: Ben C
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Ian Collins
• Re: Educated guesses for efficiency?
  • From: Keith Thompson
• Re: wit's end
  • From: Keith Thompson
• Re: coin toss problem
  • From: Keith Thompson
• Re: coin toss problem
  • From: Richard Heathfield
• Re: coin toss problem
  • From: Keith Thompson
• Re: coin toss problem
  • From: Eric Sosman
• Re: Educated guesses for efficiency?
  • From: Richard Heathfield
• Re: Pointer passing
  • From: Keith Thompson
• Re: The performance of all kinds of C operations
  • From: jacob navia
• Re: coin toss problem
  • From: Ian Collins
• Re: knowing exact string array length ?
  • From: Richard Heathfield
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: The performance of all kinds of C operations
  • From: Ian Collins
• Re: Sentence input and replacing
  • From: Keith Thompson
• Re: coin toss problem
  • From: Richard Heathfield
• Re: sentence
  • From: Keith Thompson
• Re: Educated guesses for efficiency?
  • From: Michael Mair
• Re: The performance of all kinds of C operations
  • From: Keith Thompson
• Re: knowing exact string array length ?
  • From: Keith Thompson
• Re: Educated guesses for efficiency?
  • From: jacob navia
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Keith Thompson
• Re: wit's end
  • From: Your Uncle
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: Keith Thompson
• Re: coin toss problem
  • From: Ian Collins
• Re: Pointer passing
  • From: Richard Heathfield
• Re: Pointer passing
  • From: quigstah@xxxxxxxxx
• Re: Pointer passing
  • From: Richard Heathfield
• Re: Printing "tab"
  • From: Jordan Abel
• Pointer passing
  • From: quigstah@xxxxxxxxx
• Re: Really basic..
  • From: Richard Heathfield
• Re: Educated guesses for efficiency?
  • From: Richard Heathfield
• Re: coin toss problem
  • From: CBFalconer
• Re: thankx
  • From: CBFalconer
• Re: Really basic..
  • From: Frederick Gotham
• Re: Question about the *= (and similar) operator
  • From: CBFalconer
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: CBFalconer
• Re: r- r-value vs l-value?
  • From: Chris Torek
• Re: Newbie help on string splitting
  • From: Frederick Gotham
• Re: Educated guesses for efficiency?
  • From: Eric Sosman
• Re: realloc question
  • From: Stan Milam
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: pete
• Re: knowing exact string array length ?
  • From: Joe Estock
• Re: coin toss problem
  • From: pete
• Re: thankx
  • From: Joe Estock
• Re: coin toss problem
  • From: pete
• Re: Educated guesses for efficiency?
  • From: Tim Prince
• Re: Educated guesses for efficiency?
  • From: Morris Dovey
• Re: wit's end
  • From: Joe Wright
• Re: r- r-value vs l-value?
  • From: pete
• thankx
  • From: ash
• Re: coin toss problem
  • From: Joe Smith
• Re: Educated guesses for efficiency?
  • From: jacob navia
• Educated guesses for efficiency?
  • From: Frederick Gotham
• Re: Using static to init vars?
  • From: Michael Mair
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: wit's end
  • From: Joe Smith
• Re: knowing exact string array length ?
  • From: Joe Wright
• Re: a little mistake
  • From: Joe Estock
• Re: Printing "tab"
  • From: Joe Wright
• Re: coin toss problem
  • From: Bill Pursell
• Re: Printing "tab"
  • From: phil
• Re: sentence
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: CBFalconer
• Re: a little mistake
  • From: Richard Heathfield
• Sorry wrong language
  • From: fgothamNO
• Re: r- r-value vs l-value?
  • From: whyglinux
• Re: a little mistake
  • From: Frederick Gotham
• Re: Using static to init vars?
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: Joe Wright
• Re: knowing exact string array length ?
  • From: Michael Mair
• Re: knowing exact string array length ?
  • From: Richard Heathfield
• Re: knowing exact string array length ?
  • From: Malcolm
• Re: coin toss problem
  • From: Richard Heathfield
• Re: r- r-value vs l-value?
  • From: pete
• Re: Sentence input and replacing
  • From: sea-shadow
• Re: Sentence input and replacing
  • From: Markus Moll
• Re: Sentence input and replacing
  • From: spibou
• Sentence input and replacing
  • From: Sidhu
• Re: sentence
  • From: spibou
• sentence
  • From: Sidhu
• Re: wit's end
  • From: ada
• Re: clc-wiki gone?
  • From: Netocrat
• Re: a little mistake
  • From: Peter Nilsson
• Re: The performance of all kinds of C operations
  • From: Nick Keighley
• Re: knowing exact string array length ?
  • From: alberto
• Re: r- r-value vs l-value?
  • From: whyglinux
• Re: coin toss problem
  • From: Ian Collins
• Re: coin toss problem
  • From: CBFalconer
• Re: knowing exact string array length ?
  • From: Michael Mair
• Re: realloc question
  • From: CBFalconer
• Re: knowing exact string array length ?
  • From: Martin Jørgensen
• Re: Question about style
  • From: CBFalconer
• Re: knowing exact string array length ?
  • From: alberto
• Re: knowing exact string array length ?
  • From: alberto
• Re: a little mistake
  • From: lovecreatesbeauty
• Re: knowing exact string array length ?
  • From: Keith Thompson
• Re: knowing exact string array length ?
  • From: Bill Pursell
• knowing exact string array length ?
  • From: alberto
• Re: r- r-value vs l-value?
  • From: pete
• coin toss problem
  • From: celerysoup16
• Re: r- r-value vs l-value?
  • From: whyglinux
• Re: wit's end
  • From: av
• Post Ur Job Requirements/Resumes Free ........
  • From: gmail_girl
• Re: realloc question
  • From: Gordon Burditt
• Re: realloc question
  • From: spibou
• Re: realloc question
  • From: Ian Collins
• realloc question
  • From: Jack
• Re: Printing "tab"
  • From: Julian V. Noble
• Re: a little mistake
  • From: Julian V. Noble
• Re: Printing "tab"
  • From: mdh
• Re: Printing "tab"
  • From: mdh
• Re: wit's end
  • From: Chris Torek
• Re: types of 'Open' command
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Keith Thompson
• Re: What gcc options guarantee more portable C code
  • From: Peter Nilsson
• Re: clc-wiki gone?
  • From: those who know me have no need of my name
• Re: The performance of all kinds of C operations
  • From: Eric Sosman
• Re: types of 'Open' command
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Keith Thompson
• Re: types of 'Open' command
  • From: Nelu
• Re: types of 'Open' command
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Nelu
• Re: What gcc options guarantee more portable C code
  • From: Ian Collins
• Re: wit's end
  • From: Michael Mair
• Re: wit's end
  • From: Keith Thompson
• Re: types of 'Open' command
  • From: Richard Heathfield
• Re: wit's end
  • From: Frank Silvermann
• Re: What gcc options guarantee more portable C code
  • From: Ian Collins
• Re: Unnamed struct members allowed?
  • From: SM Ryan
• Re: What gcc options guarantee more portable C code
  • From: Ian Collins
• Re: What gcc options guarantee more portable C code
  • From: Andrew Poelstra
• Re: types of 'Open' command
  • From: Andrew Poelstra
• Re: Printing "tab"
  • From: Andrew Poelstra
• Re: Unnamed struct members allowed?
  • From: Keith Thompson
• Re: What gcc options guarantee more portable C code
  • From: Keith Thompson
• Re: What gcc options guarantee more portable C code
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Richard Tobin
• Re: <well OT> types of 'Open' command
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Ian Collins
• Re: types of 'Open' command
  • From: Richard Heathfield
• Re: What gcc options guarantee more portable C code
  • From: Andrew Poelstra
• Re: wit's end
  • From: Richard Heathfield
• Re: wit's end
  • From: Richard Heathfield
• Re: types of 'Open' command
  • From: Andrew Poelstra
• Re: Printing "tab"
  • From: mdh
• Re: gcc knows about malloc()
  • From: Mark McIntyre
• Re: wit's end
  • From: Frank Silvermann
• Re: Printing "tab"
  • From: mdh
• Re: Printing "tab"
  • From: Andrew Poelstra
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: a little mistake
  • From: CBFalconer
• Re: wit's end
  • From: Keith Thompson
• Re: wit's end
  • From: Keith Thompson
• Re: Undefined
  • From: CBFalconer
• Re: Which is more portable / is there a better way?
  • From: Skarmander
• Re: wit's end
  • From: Keith Thompson
• Re: Printing "tab"
  • From: CBFalconer
• Re: gcc knows about malloc()
  • From: Mark McIntyre
• Re: Unnamed struct members allowed?
  • From: CBFalconer
• Re: ANNOUNCE ggets revised
  • From: CBFalconer
• Re: types of 'Open' command
  • From: Mark McIntyre
• Re: wit's end
  • From: Joe Smith
• Re: Question about the *= (and similar) operator
  • From: CBFalconer
• Re: Printing "tab"
  • From: mdh
• Re: Printing "tab"
  • From: mdh
• Re: wit's end
  • From: Nelu
• Re: wit's end
  • From: Richard Heathfield
• Re: wit's end
  • From: Roberto Waltman
• Re: Printing "tab"
  • From: Mike S
• wit's end
  • From: Frank Silvermann
• Re: Printing "tab"
  • From: Mike S
• Re: MPI tutorial live
  • From: Keith Thompson
• Re: a little mistake
  • From: Default User
• Re: Printing "tab"
  • From: Thomas J. Gritzan
• Re: a little mistake
  • From: Keith Thompson
• Re: Printing "tab"
  • From: mdh
• Re: a little mistake
  • From: santosh
• Re: Question about style
  • From: Malcolm
• MPI tutorial live
  • From: Malcolm
• Re: a little mistake
  • From: Malcolm
• Re: memory
  • From: Keith Thompson
• Re: Undefined
  • From: mdh
• Re: memory
  • From: Keith Thompson
• Re: Unnamed struct members allowed?
  • From: Keith Thompson
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Keith Thompson
• Re: Undefined
  • From: Eric Sosman
• a little mistake
  • From: ash
• Re: Question about style
  • From: lovecreatesbeauty
• Re: Undefined
  • From: mdh
• Re: Undefined
  • From: Tom St Denis
• Re: Printing "tab"
  • From: mdh
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Undefined
  • From: mdh
• Re: ANNOUNCE ggets revised
  • From: Keith Thompson
• Re: Question about style
  • From: Tom St Denis
• Re: Undefined
  • From: Roberto Waltman
• Re: Undefined
  • From: pete
• Re: Printing "tab"
  • From: Tom St Denis
• Re: Printing "tab"
  • From: mdh
• Re: Question about style
  • From: Keith Thompson
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: Printing "tab"
  • From: Tom St Denis
• Re: Printing "tab"
  • From: mdh
• Undefined
  • From: mdh
• Re: Printing "tab"
  • From: Tom St Denis
• Re: Which is more portable / is there a better way?
  • From: pete
• Printing "tab"
  • From: mdh
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: memory
  • From: Richard Heathfield
• Re: Unnamed struct members allowed?
  • From: Jalapeno
• Re: Unnamed struct members allowed?
  • From: Jalapeno
• Re: What gcc options guarantee more portable C code
  • From: Andrew Poelstra
• Re: memory
  • From: Chris Dollin
• Re: memory
  • From: deepak
• Re: What gcc options guarantee more portable C code
  • From: lovecreatesbeauty
• Re: memory
  • From: CBFalconer
• Re: memory
  • From: CBFalconer
• Re: zero lengh arrays.
  • From: Roberto Waltman
• Re: Unnamed struct members allowed?
  • From: SM Ryan
• Which is more portable / is there a better way?
  • From: octangle
• Re: memory
  • From: Chris Dollin
• Re: Unnamed struct members allowed?
  • From: Jalapeno
• Re: memory
  • From: Tom St Denis
• Re: Unnamed struct members allowed?
  • From: Jalapeno
• Re: memory
  • From: deepak
• Re: memory
  • From: Chris Dollin
• Re: what do we understand by advanced C
  • From: tomstdenis
• Re: memory
  • From: tomstdenis
• Re: The performance of all kinds of C operations
  • From: Eric Sosman
• Re: memory
  • From: Richard Heathfield
• Re: [ot]Re: Question about the *= (and similar) operator
  • From: CBFalconer
• memory
  • From: pnreddy1976
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Richard Heathfield
• Re: casting
  • From: pete
• Re: casting
  • From: Richard Heathfield
• Re: casting
  • From: Richard Heathfield
• [ot]Re: Question about the *= (and similar) operator
  • From: pete
• Re: The performance of all kinds of C operations
  • From: Nick Keighley
• Re: Calling macros from outside the definition
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: CBFalconer
• Re: What gcc options guarantee more portable C code
  • From: CBFalconer
• Re: ANNOUNCE ggets revised
  • From: CBFalconer
• what do we understand by advanced C
  • From: noor.fatma@xxxxxxxxx
• Re: zero lengh arrays.
  • From: Richard Bos
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: CBFalconer
• Re: Unnamed struct members allowed?
  • From: Charles Richmond
• Re: C isn't for timid souls !
  • From: Richard Bos
• Re: types of 'Open' command
  • From: Charles Richmond
• Re: types of 'Open' command
  • From: Richard Bos
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Richard Bos
• Re: gcc knows about malloc()
  • From: Walter Roberson
• Re: Calling macros from outside the definition
  • From: $hiv.....
• Re: debugging C/C++ program with COFF information
  • From: vbezard
• Re: debugging C/C++ program with COFF information
  • From: Skarmander
• Re: zero lengh arrays.
  • From: spibou
• debugging C/C++ program with COFF information
  • From: vbezard
• Re: Arrays issue
  • From: Chris Torek
• Re: zero lengh arrays.
  • From: seni.yin
• Re: zero lengh arrays.
  • From: Michael Mair
• Re: gcc knows about malloc()
  • From: James Dow Allen
• Re: ANNOUNCE ggets revised
  • From: Michael Mair
• zero lengh arrays.
  • From: $hiv.....
• Re: C call tree
  • From: James Dow Allen
• Re: ANNOUNCE ggets revised
  • From: Michael Mair
• Re: Question about style
  • From: lovecreatesbeauty
• Re: The performance of all kinds of C operations
  • From: websnarf
• Re: Question about the *= (and similar) operator
  • From: James Dow Allen
• Re: C isn't for timid souls !
  • From: Thad Smith
• Re: The performance of all kinds of C operations
  • From: spibou
• Re: What gcc options guarantee more portable C code
  • From: Harald van Dijk
• Re: types of 'Open' command <OT: HTML Standards>
  • From: Ian Collins
• Re: types of 'Open' command <OT: HTML Standards>
  • From: Andrew Poelstra
• Re: What gcc options guarantee more portable C code
  • From: Ben Pfaff
• Re: What gcc options guarantee more portable C code
  • From: Andrew Poelstra
• Re: Calling macros from outside the definition
  • From: Ben
• Re: types of 'Open' command
  • From: CBFalconer
• Re: Calling macros from outside the definition
  • From: Barry Schwarz
• Re: learning C with a C++ background
  • From: CBFalconer
• Calling macros from outside the definition
  • From: Ben
• Re: Question about style
  • From: Arild Hystad
• Re: The performance of all kinds of C operations
  • From: Eric Sosman
• Re: ANNOUNCE ggets revised
  • From: Old Wolf
• Re: Using static to init vars?
  • From: Old Wolf
• Re: types of 'Open' command
  • From: Nelu
• Re: Newbie help on string splitting
  • From: Barry Schwarz
• clc-wiki gone?
  • From: Arild Hystad
• Re: Question about style
  • From: Mike S
• Re: Why?
  • From: Barry Schwarz
• Re: Reference
  • From: Keith Thompson
• Re: learning C with a C++ background
  • From: Jonathan Mcdougall
• Re: What gcc options guarantee more portable C code
  • From: Keith Thompson
• Re: Question about style
  • From: spibou
• Re: Reference
  • From: parcour@xxxxxxxxx
• Re: Question about style
  • From: Mike S
• Re: types of 'Open' command
  • From: Richard Tobin
• Re: The performance of all kinds of C operations
  • From: websnarf
• Question about style
  • From: spibou
• Re: Address of array behavior in pointer arithmetic
  • From: Joe Wright
• Re: The performance of all kinds of C operations
  • From: Kevin D . Quitt
• Re: ANNOUNCE ggets revised
  • From: Frank Silvermann
• Re: C call tree
  • From: Ben C
• Re: Unnamed struct members allowed?
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: CBFalconer
• Re: types of 'Open' command
  • From: CBFalconer
• Re: ANNOUNCE ggets revised
  • From: Keith Thompson
• Re: What gcc options guarantee more portable C code
  • From: CBFalconer
• Re: ANNOUNCE ggets revised
  • From: CBFalconer
• Re: The performance of all kinds of C operations
  • From: Chris Torek
• Re: What gcc options guarantee more portable C code
  • From: spibou
• Re: The performance of all kinds of C operations
  • From: spibou
• Re: ANNOUNCE ggets revised
  • From: Michael Mair
• Re: comp.lang.c Answers (Abridged) to Frequently Asked Questions (FAQ)
  • From: Keith Thompson
• Re: types of 'Open' command
  • From: Keith Thompson
• Re: ANNOUNCE ggets revised
  • From: Frank Silvermann
• Re: The performance of all kinds of C operations
  • From: Roberto Waltman
• Re: Reference
  • From: Michael Mair
• Re: Reference
  • From: Lew Pitcher
• Re: The performance of all kinds of C operations
  • From: Tim Prince
• Reference
  • From: fireangel
• Re: What gcc options guarantee more portable C code
  • From: Keith Thompson
• Re: Unnamed struct members allowed?
  • From: Walter Roberson
• Re: Address of array behavior in pointer arithmetic
  • From: Keith Thompson
• Unnamed struct members allowed?
  • From: Jalapeno
• Re: The performance of all kinds of C operations
  • From: Ronald Bruck
• Re: comp.lang.c Answers (Abridged) to Frequently Asked Questions (FAQ)
  • From: parcour@xxxxxxxxx
• Re: ISO C 90 standard
  • From: Harald van Dijk
• Re: ISO C 90 standard
  • From: Randy Howard
• Re: Using static to init vars?
  • From: Ronald Bruck
• Re: Address of array behavior in pointer arithmetic
  • From: Chris Torek
• Re: printing
  • From: Joe Smith
• Re: What gcc options guarantee more portable C code
  • From: tomstdenis
• Re: What gcc options guarantee more portable C code
  • From: John Bode
• Re: C isn't for timid souls !
  • From: Ian Malone
• Re: types of 'Open' command
  • From: CBFalconer
• Re: What gcc options guarantee more portable C code
  • From: CBFalconer
• Re: types of 'Open' command
  • From: Nelu
• Re: What gcc options guarantee more portable C code
  • From: Andrew Poelstra
• Re: What gcc options guarantee more portable C code
  • From: tomstdenis
• Re: Managed String Library
  • From: Andrew Poelstra
• Re: types of 'Open' command
  • From: Richard Tobin
• Re: What gcc options guarantee more portable C code
  • From: lovecreatesbeauty
• Re: types of 'Open' command
  • From: Nelu
• Re: C isn't for timid souls !
  • From: gw7rib
• Re: types of 'Open' command
  • From: Banfa
• Re: Bit shifting vs Bitfields
  • From: Roberto Waltman
• Re: What gcc options guarantee more portable C code
  • From: tomstdenis
• Re: What gcc options guarantee more portable C code
  • From: lovecreatesbeauty
• Re: types of 'Open' command
  • From: Eric Sosman
• Re: How to use 64 bit integer in 16 Bit Dos ?
  • From: Mark McIntyre
• Re: tmpfile and freopen
  • From: Barry Schwarz
• Re: printing
  • From: Christopher Benson-Manica
• Re: C isn't for timid souls !
  • From: Ian Malone
• Re: types of 'Open' command
  • From: CBFalconer
• Re: What gcc options guarantee more portable C code
  • From: CBFalconer
• Re: Address of array behavior in pointer arithmetic
  • From: pete
• Re: Address of array behavior in pointer arithmetic
  • From: pete
• Re: Address of array behavior in pointer arithmetic
  • From: joshc
• Re: Address of array behavior in pointer arithmetic
  • From: joshc
• Re: How to use 64 bit integer in 16 Bit Dos ?
  • From: Imayam
• Re: What gcc options guarantee more portable C code
  • From: Marc Boyer
• Re: Address of array behavior in pointer arithmetic
  • From: deepak
• Re: Address of array behavior in pointer arithmetic
  • From: jackdorse
• Re: Address of array behavior in pointer arithmetic
  • From: jackdorse
• Re: types of 'Open' command
  • From: Keith Thompson
• Re: How to use 64 bit integer in 16 Bit Dos ?
  • From: Keith Thompson
• Re: Address of array behavior in pointer arithmetic
  • From: Keith Thompson
• Re: Address of array behavior in pointer arithmetic
  • From: Chris Dollin
• Re: types of 'Open' command
  • From: Ico
• Re: Address of array behavior in pointer arithmetic
  • From: "Nils O. Selåsdal"
• types of 'Open' command
  • From: prabhu . pravin
• Re: Address of array behavior in pointer arithmetic
  • From: deepak
• How to use 64 bit integer in 16 Bit Dos ?
  • From: Imayam
• What gcc options guarantee more portable C code
  • From: lovecreatesbeauty
• Re: Telecom programming
  • From: Nick Keighley
• Re: Address of array behavior in pointer arithmetic
  • From: jackdorse
• Re: ISO C 90 standard
  • From: Harald van Dijk
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Keith Thompson
• Re: Managed String Library
  • From: jacob navia
• Re: Bit shifting vs Bitfields
  • From: Ian Collins
• Re: C Programming: A Modern Approach 2nd Edition
  • From: jacob navia
• Re: Address of array behavior in pointer arithmetic
  • From: pete
• Address of array behavior in pointer arithmetic
  • From: joshc
• Re: How to detect the entry point of a function?
  • From: Keith Thompson
• Re: OT: Re: How to detect the entry point of a function?
  • From: Johnny
• Re: How to detect the entry point of a function?
  • From: Johnny
• line2string.c, Re: Critic of the given code.
  • From: pete
• Re: ISO C 90 standard
  • From: Randy Howard
• Re: Critic of the given code.
  • From: Giorgos Keramidas
• Re: Bit shifting vs Bitfields
  • From: Chris Torek
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Robert Gamble
• Re: C isn't for timid souls !
  • From: Keith Thompson
• Re: Bit shifting vs Bitfields
  • From: Keith Thompson
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Al Balmer
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Andrew Poelstra
• Re: Bit shifting vs Bitfields
  • From: Roberto Waltman
• Re: How to prevent the quick disappearance of window
  • From: Jordan Abel
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Jordan Abel
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: converting int to string
  • From: Keith Thompson
• Simple recursive preprocessor meta-program implementation...
  • From: Chris Thomasson
• Re: memory and subroutines
  • From: Frank Silvermann
• Re: Bit shifting vs Bitfields
  • From: Ian Collins
• Re: Managed String Library
  • From: Robert Seacord
• Re: memory and subroutines
  • From: Eric Sosman
• Re: Bit shifting vs Bitfields
  • From: Roberto Waltman
• Re: Bit shifting vs Bitfields
  • From: Walter Roberson
• Re: Managed String Library
  • From: jacob navia
• Re: C Programming: A Modern Approach 2nd Edition
  • From: jacob navia
• Re: printing
  • From: c language
• Re: memory and subroutines
  • From: Frank Silvermann
• Re: Bit shifting vs Bitfields
  • From: Ian Collins
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: av
• Re: need some help
  • From: av
• Managed String Library
  • From: rCs
• Re: Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: Kevin D . Quitt
• Re: Bit shifting vs Bitfields
  • From: pete
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Robert Gamble
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Al Balmer
• Re: Question about the *= (and similar) operator
  • From: Skarmander
• Re: printing
  • From: kleuske
• Re: printing
  • From: Christopher Benson-Manica
• printing
  • From: c language
• Re: c++ developer
  • From: Default User
• Re: C isn't for timid souls !
  • From: Christopher Benson-Manica
• Re: Why this is wrong?
  • From: Lew Pitcher
• Re: learning C with a C++ background
  • From: Default User
• Re: learning C with a C++ background
  • From: santosh
• Re: learning C with a C++ background
  • From: Charles Richmond
• Re: Why this is wrong?
  • From: Charles Richmond
• Re: gcc knows about malloc()
  • From: Walter Roberson
• Re: Telecom programming
  • From: Walter Roberson
• Re: C Programming: A Modern Approach 2nd Edition
  • From: Andrew Poelstra
• Re: memory and subroutines
  • From: Eric Sosman
• Re: C isn't for timid souls !
  • From: Chris Dollin
• Re: Question about the *= (and similar) operator
  • From: Andrew Poelstra
• Re: learning C with a C++ background
  • From: Andrew Poelstra
• Re: gcc knows about malloc()
  • From: Andrew Poelstra
• Re: C isn't for timid souls !
  • From: Andrew Poelstra
• memory and subroutines
  • From: Frank Silvermann
• Re: C isn't for timid souls !
  • From: Andrew Poelstra
• Re: Shift operators.
  • From: Tim Prince
• Re: converting int to string
  • From: Richard Bos
• Re: Bit shifting vs Bitfields
  • From: Roberto Waltman
• Telecom programming
  • From: a . abdulwahab
• Re: C isn't for timid souls !
  • From: tomstdenis
• Re: Shift operators.
  • From: Chris Dollin
• Re: c++ developer
  • From: Kenneth Brody
• Re: C isn't for timid souls !
  • From: Chris Dollin
• Re: Shift operators.
  • From: deepak
• Re: converting int to string
  • From: richard_l
• Re: Bit shifting vs Bitfields
  • From: richard_l
• Re: Shift operators.
  • From: pete
• Re: C isn't for timid souls !
  • From: tomstdenis
• Re: C isn't for timid souls !
  • From: Roberto Waltman
• Re: Question about the *= (and similar) operator
  • From: Kenneth Brody
• Re: c++ developer
  • From: tomstdenis
• Re: C isn't for timid souls !
  • From: tomstdenis
• c++ developer
  • From: googlegroups
• Re: C call tree
  • From: Roberto Waltman
• Re: gcc knows about malloc()
  • From: Harald van Dijk
• Re: C isn't for timid souls !
  • From: Chris Dollin
• Re: Shift operators.
  • From: Chris Dollin
• Re: Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: Lee Xuzhang
• C call tree
  • From: Max
• Re: gcc knows about malloc()
  • From: Eric Sosman
• Re: Shift operators.
  • From: Marc Boyer
• Re: C isn't for timid souls !
  • From: tomstdenis
• Re: C isn't for timid souls !
  • From: tomstdenis
• Re: Shift operators.
  • From: Chris Dollin
• Re: Shift operators.
  • From: tomstdenis
• Re: Shift operators.
  • From: Marc Boyer
• Shift operators.
  • From: deepak
• Re: Question about the *= (and similar) operator
  • From: CBFalconer
• Re: Bit shifting vs Bitfields
  • From: swengineer001@xxxxxxxxx
• Re: Question about the *= (and similar) operator
  • From: James Dow Allen
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: Question about the *= (and similar) operator
  • From: Harald van Dijk
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: Why this is wrong?
  • From: rain.man
• Re: gcc knows about malloc()
  • From: James Dow Allen
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: Question about the *= (and similar) operator
  • From: jaysome
• Re: Question about the *= (and similar) operator
  • From: Harald van Dijk
• Re: gcc knows about malloc()
  • From: SuperKoko
• Re: Why this is wrong?
  • From: jaysome
• Re: casting
  • From: jaysome
• Re: Question about the *= (and similar) operator
  • From: Nick Keighley
• Re: Compiling with -O option gives different running time!
  • From: SuperKoko
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: C isn't for timid souls !
  • From: Chris Dollin
• Re: Compiling with -O option gives different running time!
  • From: SuperKoko
• Re: Why this is wrong?
  • From: Keith Thompson
• Re: C isn't for timid souls !
  • From: SuperKoko
• Re: Question about the *= (and similar) operator
  • From: jaysome
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: Why this is wrong?
  • From: Chris Dollin
• Re: How to prevent the quick disappearance of window
  • From: Richard Bos
• Re: gcc knows about malloc()
  • From: Richard Bos
• Re: Why this is wrong?
  • From: jaysome
• Re: How to prevent the quick disappearance of window
  • From: spibou
• How to prevent the quick disappearance of window
  • From: kcwcuttingedge
• Re: gcc knows about malloc()
  • From: jaysome
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: learning C with a C++ background
  • From: Ian Collins
• Re: C isn't for timid souls !
  • From: Keith Thompson
• Re: converting int to string
  • From: Jack Klein
• Re: learning C with a C++ background
  • From: Bill Pursell
• Re: learning C with a C++ background
  • From: Chris Torek
• Re: Why this is wrong?
  • From: Jack Klein
• Re: free(): invalid pointer
  • From: Michael Mair
• Re: free(): invalid pointer
  • From: seni.yin
• Re: converting int to string
  • From: Michael Mair
• Re: converting int to string
  • From: seni.yin
• Re: learning C with a C++ background
  • From: William Ahern
• converting int to string
  • From: Michael
• Re: gcc knows about malloc()
  • From: Harald van Dijk
• Re: C isn't for timid souls !
  • From: spibou
• Re: Weighted Bipartite Matching Implementation
  • From: Joe Smith
• Re: learning C with a C++ background
  • From: Friedrich Dominicus
• Re: Serial Port and Library
  • From: Srikanth
• Re: Serial Port and Library
  • From: Neil
• Re: free(): invalid pointer
  • From: Robert Gamble
• Re: free(): invalid pointer
  • From: Ian Collins
• Re: gcc knows about malloc()
  • From: Old Wolf
• Re: learning C with a C++ background
  • From: CBFalconer
• free(): invalid pointer
  • From: c language
• Re: C isn't for timid souls !
  • From: William J. Leary Jr.
• Serial Port and Library
  • From: zdicklin
• Re: Bit shifting vs Bitfields
  • From: Walter Roberson
• Re: C isn't for timid souls !
  • From: tomstdenis
• Re: gcc knows about malloc()
  • From: Dave Vandervies
• Re: learning C with a C++ background
  • From: Ian Collins
• Re: learning C with a C++ background
  • From: Jonathan Mcdougall
• Re: Question about the *= (and similar) operator
  • From: Andrew Poelstra
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: learning C with a C++ background
  • From: Andrew Poelstra
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Peter Nilsson
• Re: learning C with a C++ background
  • From: Ian Collins
• Re: learning C with a C++ background
  • From: Ian Collins
• C isn't for timid souls !
  • From: spibou
• Re: learning C with a C++ background
  • From: Jonathan Mcdougall
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: The Nature of the "Unix Philosophy" (long)
  • From: Frank Silvermann
• Re: learning C with a C++ background
  • From: Ian Collins
• Re: Question about the *= (and similar) operator
  • From: Thomas J. Gritzan
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Robert Allison
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• learning C with a C++ background
  • From: jonathanmcdougall
• Re: Question about the *= (and similar) operator
  • From: Rafael Almeida
• Re: Why this is wrong?
  • From: Richard Tobin
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Question about the *= (and similar) operator
  • From: Rafael Almeida
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Why this is wrong?
  • From: Rafael Almeida
• Re: Question about the *= (and similar) operator
  • From: spibou
• Why this is wrong?
  • From: linq936
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Bit shifting vs Bitfields
  • From: swengineer001@xxxxxxxxx
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: Question about the *= (and similar) operator
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: Chris McDonald
• Re: Question about the *= (and similar) operator
  • From: Giannis Papadopoulos
• Re: Question about the *= (and similar) operator
  • From: Rafael Almeida
• Re: gcc knows about malloc()
  • From: Old Wolf
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: Question about the *= (and similar) operator
  • From: Richard Tobin
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Default User
• Re: Question about the *= (and similar) operator
  • From: Giannis Papadopoulos
• Re: Question about the *= (and similar) operator
  • From: spibou
• Re: Question about the *= (and similar) operator
  • From: Chris McDonald
• Question about the *= (and similar) operator
  • From: spibou
• Re: gcc knows about malloc()
  • From: Mark McIntyre
• Re: functions that take many arguments...... + extern - what about it?
  • From: Malcolm
• Re: freeing memory
  • From: Joe Smith
• Re: Using static to init vars?
  • From: tedu
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: Bit shifting vs Bitfields
  • From: Malcolm
• Re: gcc knows about malloc()
  • From: Eric Sosman
• Re: gcc knows about malloc()
  • From: Ian Collins
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Default User
• Re: Earthquake and Tornado Forecasting Programs June 13, 2006
  • From: Default User
• Re: Compiling with -O option gives different running time!
  • From: tomstdenis
• Re: String formatting
  • From: Keith Thompson
• Re: gcc knows about malloc()
  • From: Nelu
• OT: Re: How to detect the entry point of a function?
  • From: kleuske
• Re: Compiling with -O option gives different running time!
  • From: Keith Thompson
• Re: comma expression
  • From: Keith Thompson
• Re: freeing memory
  • From: Keith Thompson
• Re: String formatting
  • From: Andrew Poelstra
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Compiling with -O option gives different running time!
  • From: CBFalconer
• Re: Earthquake and Tornado Forecasting Programs June 13, 2006
  • From: Frank Silvermann
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Frank Silvermann
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: Compiling with -O option gives different running time!
  • From: tomstdenis
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Keith Thompson
• Re: Earthquake and Tornado Forecasting Programs June 13, 2006
  • From: Default User
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Default User
• Re: gcc knows about malloc()
  • From: Ian Collins
• Re: functions that take many arguments...... + extern - what about it?
  • From: Michael Mair
• Re: functions that take many arguments...... + extern - what about it?
  • From: Keith Thompson
• Re: Compiling with -O option gives different running time!
  • From: tomstdenis
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: Compiling with -O option gives different running time!
  • From: Stephen Sprunk
• Re: Compiling with -O option gives different running time!
  • From: CBFalconer
• Re: Compiling with -O option gives different running time!
  • From: CBFalconer
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: String formatting
  • From: Brand Bogard
• Re: Compiling with -O option gives different running time!
  • From: Stephen Sprunk
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: Compiling with -O option gives different running time!
  • From: tomstdenis
• Re: functions that take many arguments...... + extern - what about it?
  • From: John Bode
• Re: freeing memory
  • From: Frank Silvermann
• Re: How to detect the entry point of a function?
  • From: octangle
• Re: Bit shifting vs Bitfields
  • From: Jack Klein
• Re: Compiling with -O option gives different running time!
  • From: aamircheema
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Jack Klein
• Re: Compiling with -O option gives different running time!
  • From: Stephen Sprunk
• Re: Newbie help on string splitting
  • From: Nelu
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: String formatting
  • From: santosh
• Re: comma expression
  • From: JAY
• Re: comma expression
  • From: JAY
• Re: comma expression
  • From: JAY
• String formatting
  • From: Shastri
• Re: freeing memory
  • From: Chris Dollin
• Re: freeing memory
  • From: jackdorse
• Re: Compiling with -O option gives different running time!
  • From: SuperKoko
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: lovecreatesbeauty
• Re: gcc knows about malloc()
  • From: Erik Trulsson
• Re: gcc knows about malloc()
  • From: Eric Sosman
• Re: Compiling with -O option gives different running time!
  • From: Chris Dollin
• Re: Compiling with -O option gives different running time!
  • From: tomstdenis
• Compiling with -O option gives different running time!
  • From: aamircheema
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: CBFalconer
• Re: casting
  • From: Keith Thompson
• Re: Really basic..
  • From: Vladimir Oka
• Re: Really basic..
  • From: Marc Boyer
• Re: Really basic..
  • From: Chris Dollin
• Re: Newbie help on string splitting
  • From: Smurff
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Bit shifting vs Bitfields
  • From: Ian Collins
• Re: Really basic..
  • From: Vladimir Oka
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Really basic..
  • From: Vladimir Oka
• Re: gcc knows about malloc()
  • From: SuperKoko
• Really basic..
  • From: deepak
• Bit shifting vs Bitfields
  • From: richard_l
• Re: gcc knows about malloc()
  • From: James Dow Allen
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Richard Heathfield
• Re: gcc knows about malloc()
  • From: Ian Collins
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Ian Collins
• Re: gcc knows about malloc()
  • From: SuperKoko
• Re: functions that take many arguments...... + extern - what about it?
  • From: Chris Dollin
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Richard Heathfield
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: CBFalconer
• Re: gcc knows about malloc()
  • From: Richard Heathfield
• Re: gcc knows about malloc()
  • From: Richard Heathfield
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: lovecreatesbeauty
• Re: functions that take many arguments...... + extern - what aboutit?
  • From: CBFalconer
• Re: gcc knows about malloc()
  • From: jaysome
• Re: GetKeyboardLayoutList
  • From: Vladimir Oka
• Re: gcc knows about malloc()
  • From: jaysome
• Re: struct in C99
  • From: SuperKoko
• Re: gcc knows about malloc()
  • From: Richard Heathfield
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: lovecreatesbeauty
• Re: gcc knows about malloc()
  • From: Ian Collins
• Re: casting
  • From: Richard Heathfield
• GetKeyboardLayoutList
  • From: sonu
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Richard Heathfield
• Re: Help with array/pointer segmentation fault needed
  • From: Ben
• Re: gcc knows about malloc()
  • From: jaysome
• Re: library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: Peter Nilsson
• Re: casting
  • From: jaysome
• library implementation strncpy() modifies string literal, legal? more doubts need more suggestion?
  • From: lovecreatesbeauty
• Re: Using static to init vars?
  • From: Chris Torek
• Re: casting
  • From: Richard Heathfield
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: struct in C99
  • From: Michael Mair
• Re: rand in a closed interval on the ints
  • From: Richard Heathfield
• Re: Using static to init vars?
  • From: Michael Mair
• Re: casting
  • From: Old Wolf
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Help with array/pointer segmentation fault needed
  • From: Ben
• Re: Newbie help on string splitting
  • From: CBFalconer
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Old Wolf
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: Newbie help on string splitting
  • From: CBFalconer
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: gcc knows about malloc()
  • From: Old Wolf
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: Weighted Bipartite Matching Implementation
  • From: CBFalconer
• Re: getchar() after EOF
  • From: CBFalconer
• Re: freeing memory
  • From: SM Ryan
• Re: rand in a closed interval on the ints
  • From: CBFalconer
• Re: gcc knows about malloc()
  • From: Richard Heathfield
• Re: easy pointer question...
  • From: lovecreatesbeauty
• Re: How to detect the entry point of a function?
  • From: Johnny
• Re: gcc knows about malloc()
  • From: Rafael Almeida
• freeing memory
  • From: Frank Silvermann
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: gcc knows about malloc()
  • From: Rafael Almeida
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: How to detect the entry point of a function?
  • From: Jack Klein
• Re: Weighted Bipartite Matching Implementation
  • From: Jack Klein
• Re: How to detect the entry point of a function?
  • From: Gordon Burditt
• How to detect the entry point of a function?
  • From: Johnny
• Re: gcc knows about malloc()
  • From: Gordon Burditt
• Re: Newbie help on string splitting
  • From: Andrew Poelstra
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Richard Heathfield
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Richard Heathfield
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: dcorbit
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Richard Heathfield
• Re: struct in C99
  • From: Rafael Almeida
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Dann Corbit
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: Why?
  • From: seni.yin
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Dann Corbit
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Dann Corbit
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Dann Corbit
• Re: gcc knows about malloc()
  • From: Eric Sosman
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Dann Corbit
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: Using static to init vars?
  • From: Eric Sosman
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: functions that take many arguments...... + extern - what about it?
  • From: Al Balmer
• Re: struct in C99
  • From: Keith Thompson
• Re: struct in C99
  • From: pocmatos
• Re: struct in C99
  • From: pocmatos
• Re: Using static to init vars?
  • From: Ronald Bruck
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: functions that take many arguments...... + extern - what about it?
  • From: Peter Nilsson
• Re: Newbie help on string splitting
  • From: Smurff
• Re: getchar() after EOF
  • From: Richard Tobin
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Newbie help on string splitting
  • From: Smurff
• Re: globals again
  • From: Glenn Hutchings
• Re: [OT] gcc knows about malloc()
  • From: Morris Dovey
• Re: Using static to init vars?
  • From: William Ahern
• Re: gcc knows about malloc()
  • From: Mark McIntyre
• Re: Why?
  • From: Mark McIntyre
• Re: globals again
  • From: Glenn Hutchings
• Re: functions that take many arguments...... + extern - what about it?
  • From: Rafael Almeida
• Re: functions that take many arguments...... + extern - what about it?
  • From: Dann Corbit
• Re: gcc knows about malloc()
  • From: SuperKoko
• Re: [OT] gcc knows about malloc()
  • From: Chris McDonald
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• functions that take many arguments...... + extern - what about it?
  • From: Martin Jørgensen
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Default User
• Weighted Bipartite Matching Implementation
  • From: Michael McGarry
• Re: struct in C99
  • From: SuperKoko
• Re: struct in C99
  • From: Keith Thompson
• Re: Using static to init vars?
  • From: Walter Roberson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Keith Thompson
• Re: rand in a closed interval on the ints
  • From: Frank Silvermann
• Re: getchar() after EOF
  • From: Keith Thompson
• Re: Using static to init vars?
  • From: Keith Thompson
• Re: RWTPtrSlist core dumps, while removing entries.
  • From: Martin Ambuhl
• Re: struct in C99
  • From: Eric Sosman
• Re: getchar() after EOF
  • From: Eric Sosman
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• Re: gcc knows about malloc()
  • From: Martin Ambuhl
• Re: struct in C99
  • From: Michael Mair
• Re: getchar() after EOF
  • From: Keith Thompson
• Re: EXECryptor software protection
  • From: Keith Thompson
• Re: Using static to init vars?
  • From: Michael Mair
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• struct in C99
  • From: pocmatos
• Re: gcc knows about malloc()
  • From: Keith Thompson
• Re: getchar() after EOF
  • From: Michael Brennan
• Re: Using static to init vars?
  • From: Mark Odell
• Re: easy pointer question...
  • From: Kenneth Brody
• Re: Using static to init vars?
  • From: Al Balmer
• Re: rand in a closed interval on the ints
  • From: Dann Corbit
• Re: A quit strange coredump
  • From: Keith Thompson
• Re: getchar() after EOF
  • From: CBFalconer
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Default User
• Re: Using static to init vars?
  • From: Eric Sosman
• Re: getchar() after EOF
  • From: Michael Brennan
• Re: getchar() after EOF
  • From: Walter Roberson
• Re: Need some help compiling something
  • From: Walter Roberson
• Re: Need some help compiling something
  • From: Walter Roberson
• Re: Using static to init vars?
  • From: Al Balmer
• Re: getchar() after EOF
  • From: Jim Cook
• Re: rand in a closed interval on the ints
  • From: Frank Silvermann
• Re: Using static to init vars?
  • From: Walter Roberson
• Re: Need some help compiling something
  • From: Kileran
• Re: Need some help compiling something
  • From: Walter Roberson
• Re: Need some help compiling something
  • From: CBFalconer
• Using static to init vars?
  • From: Ronald Bruck
• Re: Need some help compiling something
  • From: Kileran
• Re: getchar() after EOF
  • From: Walter Roberson
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: Richard Heathfield
• Re: Help with array/pointer segmentation fault needed
  • From: Fred Kleinschmidt
• Re: gcc knows about malloc()
  • From: Thomas J. Gritzan
• Re: NEED HELP WITH A PROGRAM....ANYONE PLEASE HELP!
  • From: genestarwing
• getchar() after EOF
  • From: Michael Brennan
• Re: [OT] gcc knows about malloc()
  • From: Morris Dovey
• Re: How do I make my own custom C compiler?
  • From: Giannis Papadopoulos
• Re: Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: lovecreatesbeauty
• Re: globals again
  • From: SuperKoko
• Re: Can u tell me the explanation reg this problem
  • From: Wolfgang Riedel
• Re: ddj 29
  • From: Richard Bos
• Re: casting
  • From: Richard Bos
• Re: Stripping html
  • From: Asbjørn Sæbø
• Re: easy pointer question...
  • From: Walter Roberson
• Re: Help with array/pointer segmentation fault needed
  • From: Kenneth Brody
• Re: easy pointer question...
  • From: Vladimir Oka
• Re: easy pointer question...
  • From: Lew Pitcher
• easy pointer question...
  • From: Michael
• Re: gcc knows about malloc()
  • From: SuperKoko
• Re: Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: Haider
• Re: EXECryptor software protection
  • From: Richard Heathfield
• Re: Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: Richard Heathfield
• Re: EXECryptor software protection
  • From: tomstdenis
• Re: Stripping html
  • From: Ian Collins
• Re: Stripping html
  • From: Morris Dovey
• Re: EXECryptor software protection
  • From: Vladimir Oka
• Re: gcc knows about malloc()
  • From: Jordan Abel
• Re: EXECryptor software protection
  • From: jeanjean_5
• Can I passing a funtion pointer to a FUNTION which point to THE FUNTION?
  • From: Lee Xuzhang
• Re: RWTPtrSlist core dumps, while removing entries.
  • From: Vladimir Oka
• Re: Why?
  • From: Richard Bos
• RWTPtrSlist core dumps, while removing entries.
  • From: Neha
• Re: gcc knows about malloc()
  • From: Mark McIntyre
• Re: Why?
  • From: Mark McIntyre
• Re: gcc knows about malloc()
  • From: jjf
• Re: A quit strange coredump
  • From: spibou
• Re: A quit strange coredump
  • From: tomy
• Re: A quit strange coredump
  • From: Keith Thompson
• Re: A quit strange coredump
  • From: Walter Roberson
• Re: A quit strange coredump
  • From: tomy
• gcc knows about malloc()
  • From: James Dow Allen
• Re: A quit strange coredump
  • From: Walter Roberson
• Re: Need some help compiling something
  • From: santosh
• Re: globals again
  • From: Geometer
• Re: matrix memory allocation
  • From: acab
• Re: globals again
  • From: Bob Martin
• Re: Stripping html
  • From: Bill Latvin
• Re: A quit strange coredump
  • From: tomy
• Re: matrix memory allocation
  • From: Ben C
• Re: A quit strange coredump
  • From: Igmar Palsenberg
• Re: globals again
  • From: Glenn Hutchings
• Re: problem with getchar
  • From: spibou
• globals again
  • From: Geometer
• Re: Problem with socket programming
  • From: Ben Pfaff
• Re: undefined reference to ...
  • From: Ian Collins
• Re: Problem with socket programming
  • From: Carl
• Re: Stripping html
  • From: Richard Heathfield
• Re: Stripping html
  • From: Morris Dovey
• Re: Problem with socket programming
  • From: Jack Klein
• Re: undefined reference to ...
  • From: Jack Klein
• Stripping html
  • From: Medros
• Problem with socket programming
  • From: Carl
• Re: matrix memory allocation
  • From: Richard Heathfield
• Re: matrix memory allocation
  • From: tomstdenis
• Re: matrix memory allocation
  • From: Dave Vandervies
• matrix memory allocation
  • From: acab
• Re: shift a block of memory content
  • From: tomstdenis
• undefined reference to ...
  • From: benzasu
• Re: shift a block of memory content
  • From: Richard Heathfield
• Re: opinions on code
  • From: spibou
• Re: How do I make my own custom C compiler?
  • From: Morris Dovey
• Re: shift a block of memory content
  • From: tomstdenis
• Re: Why?
  • From: spibou
• Re: Masks: Why?
  • From: Nelu
• Re: shift a block of memory content
  • From: Richard Heathfield
• Re: Strange Question
  • From: spibou
• Re: Masks: Why?
  • From: spibou
• Re: shift a block of memory content
  • From: tomstdenis
• Re: How do I make my own custom C compiler?
  • From: spibou
• Re: A quit strange coredump
  • From: Keith Thompson
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Dave Vandervies
• Re: problem with getchar
  • From: Keith Thompson
• Re: how do I tell whether the read is an English letter or a number
  • From: spibou
• Re: shift a block of memory content
  • From: spibou
• Re: opinions on code
  • From: spibou
• Re: need some help
  • From: Default User
• Re: Need some help compiling something
  • From: bcaller
• Re: Need some help compiling something
  • From: kleuske
• Need some help compiling something
  • From: kileran
• Re: problem
  • From: Walter Roberson
• Re: problem
  • From: Ico
• Re: A quit strange coredump
  • From: Ben C
• Re: A quit strange coredump
  • From: Ico
• Re: problem
  • From: Nelu
• problem
  • From: fireangel
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: William J. Leary Jr.
• opinions on code
  • From: jaso
• Re: A quit strange coredump
  • From: Michael Mair
• A quit strange coredump
  • From: tomy
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: William J. Leary Jr.
• Re: Why?
  • From: Morris Dovey
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Morris Dovey
• Re: Why?
  • From: mdh
• Re: need some help
  • From: CBFalconer
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Chris Hills
• Re: problems with strtok()
  • From: Michael
• Re: problems with strtok()
  • From: Michael Mair
• Re: Why?
  • From: Alessandro [AkiRoss] Re
• problems with strtok()
  • From: Michael
• Re: Help with array/pointer segmentation fault needed
  • From: Ben
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: jjf
• Re: need some help
  • From: av
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Chris Hills
• Re: problem with getchar
  • From: CBFalconer
• Re: shift a block of memory content
  • From: Richard Heathfield
• shift a block of memory content
  • From: yancheng . cheok
• Re: benchmarking c programs
  • From: russell kym horsell
• Re: problem with getchar
  • From: shekhardeodhar
• benchmarking c programs
  • From: Ben
• Re: How do I make my own custom C compiler?
  • From: Allan Adler
• Re: Why?
  • From: Keith Thompson
• Re: allocating double arrays dynamically
  • From: Allan Adler
• Re: How do I make my own custom C compiler?
  • From: Morris Dovey
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: P.J. Plauger
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: P.J. Plauger
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: P.J. Plauger
• Re: Why?
  • From: mdh
• Re: rand in a closed interval on the ints
  • From: Frank Silvermann
• Re: Why?
  • From: Peter "Shaggy" Haywood
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Peter "Shaggy" Haywood
• Re: How do I make my own custom C compiler?
  • From: Peter "Shaggy" Haywood
• Re: Strange Question
  • From: Peter "Shaggy" Haywood
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Richard Heathfield
• Re: newbie question: difference between (*ptr) and *ptr thnkx
  • From: hans christian
• Re: how to iterate through all members in a struct
  • From: Richard Heathfield
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Malcolm
• Re: newbie question: difference between (*ptr) and *ptr
  • From: xhoster
• Re: Why?
  • From: mdh
• Re: how to iterate through all members in a struct
  • From: Malcolm
• Re: the difference * **
  • From: Malcolm
• Re: newbie question: difference between (*ptr) and *ptr
  • From: Ben Pfaff
• Re: newbie question: difference between (*ptr) and *ptr
  • From: hans christian
• Re: newbie question: difference between (*ptr) and *ptr
  • From: Ben Pfaff
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Ben Pfaff
• newbie question: difference between (*ptr) and *ptr
  • From: hans christian
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Keith Thompson
• Re: Example for an dynamically allocated associative array in C
  • From: Keith Thompson
• Re: exercise 1-20 K&R
  • From: Michael Mair
• Re: problem with getchar
  • From: Michael Mair
• Re: problem with getchar
  • From: kleuske
• Re: Why the C committee doesn't provide an implementation when the standard is published?
  • From: Mark McIntyre
• Re: problem with getchar
  • From: Michael Mair
• Re: rand in a closed interval on the ints
  • From: Michael Mair
• Re: problem with getchar
  • From: keltanokka
• Re: problem with getchar
  • From: Michael Mair
• Re: how to iterate through all members in a struct
  • From: jaso
• Re: rand in a closed interval on the ints
  • From: Frank Silvermann
• Re: problem with getchar
  • From: Michael Mair
• Re: problem with getchar
  • From: kleuske
• Re: Why the C committee doesn't provide an implement