comp.lang.c

• Thread Index

---

• Re: Simplicity has a future
  • From: Mike S
• Re: C Pointer problem
  • From: Richard Heathfield
• Re: C Pointer problem
  • From: Default User
• Re: malloc() implementation
  • From: Keith Thompson
• Re: Help is need immidiately
  • From: W Marsh
• Re: Help is need immidiately
  • From: Al Balmer
• Re: Help is need immidiately
  • From: Richard Heathfield
• Re: malloc() implementation
  • From: Clever Monkey
• Re: Help is need immidiately
  • From: W Marsh
• Re: Help is need immidiately
  • From: Keith Thompson
• Re: Help is need immidiately
  • From: Walter Roberson
• Re: Help is need immidiately
  • From: Eric Sosman
• Re: C Pointer problem
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: jacob navia
• C Pointer problem
  • From: Markus
• Re: Help is need immidiately
  • From: vinod . bhavnani
• Re: Simplicity has a future
  • From: Default User
• Re: Simplicity has a future
  • From: SuperKoko
• Re: Simplicity has a future
  • From: Marc Boyer
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: malloc() implementation
  • From: kyle.tk
• Re: Simplicity has a future
  • From: Marc Boyer
• Re: legality of forward declaration
  • From: Harald van Dijk
• Re: Bit fiddling
  • From: Eric Sosman
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Marc Boyer
• Re: Simplicity has a future
  • From: Richard Bos
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: legality of forward declaration
  • From: Vladimir Oka
• Re: malloc() implementation
  • From: Flash Gordon
• Re: legality of forward declaration
  • From: Flash Gordon
• Re: legality of forward declaration
  • From: Kenneth Brody
• Re: Simplicity has a future
  • From: Vladimir Oka
• Re: malloc() implementation
  • From: Richard Tobin
• Re: Simplicity has a future
  • From: Marc Boyer
• Re: legality of forward declaration
  • From: Vladimir Oka
• Re: Simplicity has a future
  • From: Richard Bos
• Re: malloc() implementation
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Vladimir Oka
• Re: malloc() implementation
  • From: Flash Gordon
• Re: malloc() implementation
  • From: Flash Gordon
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Hiding a file
  • From: Flash Gordon
• Re: Bit fiddling
  • From: Ralf Schallenberg
• Re: Simplicity has a future
  • From: Marc Boyer
• Re: malloc() implementation
  • From: Haider
• Re: Hiding a file
  • From: santosh
• Re: malloc() implementation
  • From: John Devereux
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Regarding free function
  • From: Flash Gordon
• Re: Hiding a file
  • From: Sync_net
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Regarding free function
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: problem with size of
  • From: Barry Schwarz
• Regarding free function
  • From: Vijay
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Ian Collins
• Re: malloc() implementation
  • From: Vladimir Oka
• Re: Simplicity has a future
  • From: Harald van Dijk
• Re: malloc() implementation
  • From: Flash Gordon
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Harald van Dijk
• malloc() implementation
  • From: Karsten Jung
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: output from program - why?
  • From: Allan M. Bruce
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: James Dow Allen
• Re: Simplicity has a future
  • From: Harald van Dijk
• Re: problem with size of
  • From: Flash Gordon
• Re: Simplicity has a future
  • From: Flash Gordon
• Re: lower number
  • From: jaks . maths
• Re: Writing a custom libc
  • From: Ico
• Re: -Bstatic flag
  • From: Keith Thompson
• Re: Writing a custom libc
  • From: Levi Campbell
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Simplicity has a future
  • From: Ben Pfaff
• Re: -Bstatic flag
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Friedrich Dominicus
• Re: Random Number Generation
  • From: Michael Mair
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Bit fiddling
  • From: Harald van Dijk
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: Bit fiddling
  • From: jaks . maths
• -Bstatic flag
  • From: seema
• Re: Bit fiddling
  • From: Andrew Poelstra
• Re: Bit fiddling
  • From: Andrew Poelstra
• Re: bibliography
  • From: Jack Klein
• JKop isn't home, can I take a message?
  • From: Tomás
• Re: Random Number Generation
  • From: Eric
• Re: Simplicity has a future
  • From: Old Wolf
• Re: Writing a custom libc
  • From: Eric Sosman
• bibliography
  • From: mito19651996
• Re: Writing a custom libc
  • From: Ian Collins
• Writing a custom libc
  • From: Levi Campbell
• Re: Simplicity has a future
  • From: Tomás
• Re: Simplicity has a future
  • From: Tomás
• Re: problem with size of
  • From: newbie
• Re: error 'unnamed fields'
  • From: Ian Collins
• Re: Help is need immidiately
  • From: Barry Schwarz
• Re: problem with size of
  • From: Barry Schwarz
• Re: linked list - struct problem
  • From: Barry Schwarz
• Re: scope q
  • From: Barry Schwarz
• Re: error 'unnamed fields'
  • From: Keith Thompson
• Re: error 'unnamed fields'
  • From: Barry Schwarz
• Re: Simplicity has a future
  • From: Ian Collins
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: Really easy cygwin / gcc question
  • From: Michael
• Re: Simplicity has a future
  • From: Walter Roberson
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Bit fiddling
  • From: Walter Roberson
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: Really easy cygwin / gcc question
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: Tomás
• Re: Bit fiddling
  • From: Eric Sosman
• Re: Simplicity has a future
  • From: Ian Collins
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: Really easy cygwin / gcc question
  • From: Default User
• Re: Simplicity has a future
  • From: Malcolm
• Re: Simplicity has a future
  • From: SuperKoko
• Re: Bit fiddling
  • From: Andrew Poelstra
• Re: Simplicity has a future
  • From: jacob navia
• Re: Bit fiddling
  • From: Kevin Handy
• Re: Simplicity has a future
  • From: jacob navia
• Re: Simplicity has a future
  • From: Clever Monkey
• Re: Help is need immidiately
  • From: Default User
• Re: Simplicity has a future
  • From: Keith Thompson
• Re: traffic counter in linux or bsd
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: Richard Heathfield
• Re: Really easy cygwin / gcc question
  • From: Keith Thompson
• Re: Really easy cygwin / gcc question
  • From: Richard Heathfield
• Re: Really easy cygwin / gcc question
  • From: Keith Thompson
• Re: Really easy cygwin / gcc question
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: spibou
• Re: Bit fiddling
  • From: Keith Thompson
• Re: Simplicity has a future
  • From: Tomás
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Eric Sosman
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Flash Gordon
• Re: traffic counter in linux or bsd
  • From: Walter Roberson
• Simplicity has a future
  • From: jacob navia
• Re: Really easy cygwin / gcc question
  • From: Flash Gordon
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Walter Roberson
• Re: traffic counter in linux or bsd
  • From: guilherme . oliveira
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Alberto Giménez
• Re: traffic counter in linux or bsd
  • From: Walter Roberson
• Re: Help is need immidiately
  • From: Eric Sosman
• Re: Help is need immidiately
  • From: vinod . bhavnani
• Re: Really easy cygwin / gcc question
  • From: Default User
• Re: Help is need immidiately
  • From: vinod . bhavnani
• Re: Help is need immidiately
  • From: Walter Roberson
• Re: Really easy cygwin / gcc question
  • From: Martin Jørgensen
• traffic counter in linux or bsd
  • From: guilherme . oliveira
• Re: Help is need immidiately
  • From: Robert Gamble
• Help is need immidiately
  • From: vinod . bhavnani
• Re: output from program - why?
  • From: Thad Smith
• Re: output from program - why?
  • From: Bob
• Re: Really easy cygwin / gcc question
  • From: Clever Monkey
• Re: Bit fiddling
  • From: Andrew Poelstra
• Re: Bit fiddling
  • From: Eric Sosman
• Re: Not necessarily contiguous
  • From: Andrew Poelstra
• Re: Need experts suggestion
  • From: Vladimir Oka
• Re: Bit fiddling
  • From: Andrew Poelstra
• Re: EXECryptor software protection
  • From: Vladimir Oka
• Re: EXECryptor software protection
  • From: Bill
• Re: Storing variable arguments for future use in C?
  • From: tobiasoed
• Re: problem with size of
  • From: Ico
• Re: output from program - why?
  • From: Flash Gordon
• Re: output from program - why?
  • From: Haider
• Re: Really easy cygwin / gcc question
  • From: Flash Gordon
• Re: x=(x=5,11)
  • From: google
• Re: Really easy cygwin / gcc question
  • From: Richard Bos
• Re: problem with size of
  • From: Vladimir Oka
• Re: problem with size of
  • From: Captain Winston
• Re: Really easy cygwin / gcc question
  • From: Michael
• problem with size of
  • From: seema
• Re: Really easy cygwin / gcc question
  • From: Vladimir Oka
• Re: Really easy cygwin / gcc question
  • From: Vladimir Oka
• Re: output from program - why?
  • From: Bart Rider
• Re: linked list - struct problem
  • From: Flash Gordon
• output from program - why?
  • From: Allan M. Bruce
• Really easy cygwin / gcc question
  • From: Michael
• Re: linked list - struct problem
  • From: Erik
• Re: error 'unnamed fields'
  • From: Roman Mashak
• Re: scope q
  • From: Frank Silvermann
• Re: LL help
  • From: Steve Chow
• Re: scope q
  • From: Richard Heathfield
• Re: applying C preprocessor partially
  • From: Richard Bos
• Re: LL help
  • From: Michael Mair
• Re: Bit fiddling
  • From: jaks . maths
• Re: Bit fiddling
  • From: Neil
• Re: error 'unnamed fields'
  • From: Ian Collins
• Re: LL help
  • From: Steve Chow
• Re: LL help
  • From: Walter Roberson
• Re: Not necessarily contiguous
  • From: Jack
• LL help
  • From: Steve Chow
• Re: Not necessarily contiguous
  • From: Andrew Poelstra
• Re: error 'unnamed fields'
  • From: Roman Mashak
• Re: error 'unnamed fields'
  • From: Ian Collins
• error 'unnamed fields'
  • From: Roman Mashak
• Re: Not necessarily contiguous
  • From: Jack
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Arrays issue
  • From: Chris Torek
• Re: scope q
  • From: Barry Schwarz
• Re: x=(x=5,11)
  • From: Old Wolf
• scope q
  • From: Frank Silvermann
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: What is the purpose of the construct ``if (m <<= 0)'' ?
  • From: Ian Collins
• Re: What is the purpose of the construct ``if (m <<= 0)'' ?
  • From: spibou
• Re: What is the purpose of the construct ``if (m <<= 0)'' ?
  • From: Walter Roberson
• Re: Not necessarily contiguous
  • From: Andrew Poelstra
• Re: What is the purpose of the construct ``if (m <<= 0)'' ?
  • From: Keith Thompson
• Re: DOS using C
  • From: Walter Roberson
• Re: applying C preprocessor partially
  • From: Keith Thompson
• What is the purpose of the construct ``if (m <<= 0)'' ?
  • From: spibou
• Re: memory allocation
  • From: Malcolm
• Re: Structure through sendto()
  • From: Stephen Sprunk
• Re: applying C preprocessor partially
  • From: Ira Baxter
• Re: UNIX libraries in windows
  • From: Clever Monkey
• Re: linked list - struct problem
  • From: Keith Thompson
• UNIX libraries in windows
  • From: anand . ba
• Re: memory allocation
  • From: Keith Thompson
• Re: DOS using C
  • From: Keith Thompson
• Re: Taking a test for a job
  • From: Keith Thompson
• Re: Diffrence
  • From: Keith Thompson
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Keith Thompson
• Re: memory allocation
  • From: Walter Roberson
• Re: memory allocation
  • From: Joe Wright
• Re: memory allocation
  • From: Frank Silvermann
• Re: PLease help me.Wots the problem with following code....?
  • From: codergem
• Re: Diffrence
  • From: Chris Hills
• Re: Arrays issue
  • From: Clever Monkey
• Re: Structure through sendto()
  • From: Walter Roberson
• Re: PLease help me.Wots the problem with following code....?
  • From: Barry Schwarz
• Re: PLease help me.Wots the problem with following code....?
  • From: Richard Tobin
• Re: PLease help me.Wots the problem with following code....?
  • From: santosh
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Skarmander
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Diffrence
  • From: W Marsh
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Not necessarily contiguous
  • From: Jack
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Marc Thrun
• Re: Difficulty
  • From: Clever Monkey
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Jordan Abel
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: google
• Re: Taking a test for a job
  • From: Tomás
• Re: memory allocation
  • From: bert
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Tomás
• Re: Diffrence
  • From: Tomás
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: PLease help me.Wots the problem with following code....?
  • From: alankrit
• Re: x=(x=5,11)
  • From: google
• Re: Not necessarily contiguous
  • From: Andrew Poelstra
• Re: Storing variable arguments for future use in C?
  • From: Andrew Poelstra
• Re: pointer
  • From: Andrew Poelstra
• Re: DOS using C
  • From: santosh
• Re: applying C preprocessor partially
  • From: Joe Estock
• Re: Diffrence
  • From: Erik Wikström
• Re: PLease help me.Wots the problem with following code....?
  • From: Richard Heathfield
• Re: DOS using C
  • From: Richard Heathfield
• Re: PLease help me.Wots the problem with following code....?
  • From: santosh
• Re: memory allocation
  • From: santosh
• Re: Flexible array member and alignement
  • From: tobiasoed
• Re: applying C preprocessor partially
  • From: Richard Heathfield
• Re: memory allocation
  • From: Richard Tobin
• PLease help me.Wots the problem with following code....?
  • From: alankrit
• Re: linked list - struct problem
  • From: santosh
• DOS using C
  • From: enjoywithneha@xxxxxxxxx
• Re: Storing variable arguments for future use in C?
  • From: Richard Bos
• Re: pointer
  • From: Joe Wright
• Re: x=(x=5,11)
  • From: Harald van Dijk
• applying C preprocessor partially
  • From: Urs Thuermann
• Re: x=(x=5,11)
  • From: Erik Wikström
• Re: x=(x=5,11)
  • From: google
• Re: Taking a test for a job
  • From: spibou
• Re: Difficulty
  • From: ballpointpenthief
• Storing variable arguments for future use in C?
  • From: prasanthag
• memory allocation
  • From: Emil Huseynli
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: SM Ryan
• Re: Diffrence
  • From: Vijay
• Re: Diffrence
  • From: Vijay
• Diffrence
  • From: Vijay
• Re: linked list - struct problem
  • From: Erik
• Re: linked list - struct problem
  • From: Richard Heathfield
• Re: Difficulty
  • From: Richard Heathfield
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Ico
• Re: Hiding a file
  • From: Jaspreet
• Re: linked list - struct problem
  • From: Erik
• Difficulty
  • From: Vijay
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Richard Bos
• Re: linked list - struct problem
  • From: santosh
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: santosh
• linked list - struct problem
  • From: Erik
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: santosh
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: newbie
• Re: x=(x=5,11)
  • From: Richard Tobin
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Richard Heathfield
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Ico
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: Richard Heathfield
• Re: String Handling
  • From: Richard Heathfield
• Re: How can we perfom multiplication programatically without using + or * operator.
  • From: santosh
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: String Handling
  • From: santosh
• How can we perfom multiplication programatically without using + or * operator.
  • From: mjdeesh_hi
• String Handling
  • From: Vijay
• Re: Hiding a file
  • From: Keith Thompson
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Keith Thompson
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Richard Bos
• Re: Hiding a file
  • From: santosh
• Re: x=(x=5,11)
  • From: Richard Bos
• Hiding a file
  • From: Sync_net
• Re: x=(x=5,11)
  • From: google
• Re: Help with threads
  • From: santosh
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: santosh
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: pc
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: santosh
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Stephen Sprunk
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: russell kym horsell
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: v4vijayakumar
• Re: printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: Keith Thompson
• printf("%s\n", __FILE__); /* why SIGSEGV? */
  • From: v4vijayakumar
• Re: x=(x=5,11)
  • From: Gordon Burditt
• Re: pointer-to-pointer to char
  • From: Keith Thompson
• Re: Not necessarily contiguous
  • From: Jack
• Re: x=(x=5,11)
  • From: Jordan Abel
• Not necessarily contiguous
  • From: Tomás
• Re: Help with threads
  • From: Frank Silvermann
• Re: pointer
  • From: Andrew Poelstra
• Re: pointer-to-pointer to char
  • From: Jack
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: x=(x=5,11)
  • From: Jack Klein
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: Structure through sendto()
  • From: Stephen Sprunk
• Re: short or int
  • From: Richard Heathfield
• Re: varargs question: va_list in structure
  • From: Dave Thompson
• Re: pointer
  • From: Dave Thompson
• Re: va_list
  • From: Dave Thompson
• Re: short or int
  • From: Dave Thompson
• Re: x=(x=5,11)
  • From: Peter "Shaggy" Haywood
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: krbyxtrm
• Re: x=(x=5,11)
  • From: Kenneth Brody
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Help with threads
  • From: Ian Collins
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: Bit fiddling
  • From: Thad Smith
• Help with threads
  • From: matt
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: Old Wolf
• Re: A stylistic question.
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: A stylistic question.
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: efficient code to do left shit on 64-bit values
  • From: Richard Heathfield
• Re: efficient code to do left shit on 64-bit values
  • From: Default User
• Re: Structure through sendto()
  • From: Keith Thompson
• Re: pointer-to-pointer to char
  • From: Tomás
• Re: pointer-to-pointer to char
  • From: Ben Pfaff
• Re: Arrays issue
  • From: Keith Thompson
• Re: pointer-to-pointer to char
  • From: Jack
• Re: efficient code to do left shit on 64-bit values
  • From: Andrew Poelstra
• Re: efficient code to do left shit on 64-bit values
  • From: Ben Pfaff
• Re: efficient code to do left shit on 64-bit values
  • From: Default User
• using mbcs and wide functions (was: Re: 8 bit character string to 16 bit character string)
  • From: those who know me have no need of my name
• Re: Arrays issue
  • From: ataanis
• Re: x=(x=5,11)
  • From: Robert Gamble
• Re: removing a printf statement from my program causes it to crash!?
  • From: ballpointpenthief
• Re: pointer-to-pointer to char
  • From: Tomás
• Re: x=(x=5,11)
  • From: Andrew Poelstra
• Re: pointer-to-pointer to char
  • From: Joe Wright
• Re: x=(x=5,11)
  • From: Kenneth Brody
• Re: efficient code to do left shit on 64-bit values
  • From: Andrew Poelstra
• Re: pointer-to-pointer to char
  • From: Tomás
• Re: pointer-to-pointer to char
  • From: Joe Wright
• Re: x=(x=5,11)
  • From: Harald van Dijk
• Re: pointer-to-pointer to char
  • From: Tomás
• Re: Bit fiddling
  • From: Tim Woodall
• Re: Bit fiddling
  • From: Eric Sosman
• Re: Bit fiddling
  • From: Richard Heathfield
• Re: Need experts suggestion
  • From: Gsec
• Bit fiddling
  • From: saurabhnsit2001
• Re: Bit fiddling
  • From: W Marsh
• Bit fiddling
  • From: saurabhnsit2001
• Re: pointer-to-pointer to char
  • From: Joe Wright
• Re: x=(x=5,11)
  • From: Tim Woodall
• Re: Arrays issue
  • From: santosh
• Re: Arrays issue
  • From: Frank Silvermann
• Re: Arrays issue
  • From: ataanis
• Re: efficient code to do left shit on 64-bit values
  • From: santosh
• Re: Structure through sendto()
  • From: Malcolm
• Re: Taking a test for a job
  • From: Malcolm
• Re: efficient code to do left shift on 64-bit values
  • From: aurgathor
• Re: String Buffers?
  • From: Malcolm
• Re: Need experts suggestion
  • From: Malcolm
• Re: pointer-to-pointer to char
  • From: Ian Collins
• Re: pointer-to-pointer to char
  • From: Ian Collins
• pointer-to-pointer to char
  • From: Jack
• Re: String Buffers?
  • From: SM Ryan
• Re: AI stuff, Was Re: Taking a test for a job
  • From: Keith Thompson
• Re: String Buffers?
  • From: Jamie
• Re: efficient code to do left shit on 64-bit values
  • From: Default User
• Re: String Buffers?
  • From: SM Ryan
• Re: No more time for stupid questions
  • From: Jack Klein
• Re: Trapping bits and the like...
  • From: pete
• Re: x=(x=5,11)
  • From: pete
• Re: Trapping bits and the like...
  • From: Harald van Dijk
• Re: Trapping bits and the like...
  • From: Tomás
• Re: Trapping bits and the like...
  • From: Tomás
• Re: Trapping bits and the like...
  • From: Ben Pfaff
• Re: Trapping bits and the like...
  • From: Harald van Dijk
• Trapping bits and the like...
  • From: Tomás
• Re: efficient code to do left shit on 64-bit values
  • From: Rod Pemberton
• Re: Taking a test for a job
  • From: Harald van Dijk
• Re: Taking a test for a job
  • From: Rod Pemberton
• Re: Taking a test for a job
  • From: Tomás
• Re: Arrays issue
  • From: Barry Schwarz
• Re: Taking a test for a job
  • From: Harald van Dijk
• Re: efficient code to do left shit on 64-bit values
  • From: Joe Wright
• Re: A stylistic question.
  • From: Richard Heathfield
• Re: A stylistic question.
  • From: Rod Pemberton
• Re: Taking a test for a job
  • From: Tomás
• Re: Taking a test for a job
  • From: Richard Heathfield
• Re: A stylistic question.
  • From: Richard Heathfield
• Re: efficient code to do left shit on 64-bit values
  • From: Rod Pemberton
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: Taking a test for a job
  • From: Tomás
• Re: x=(x=5,11)
  • From: Default User
• Re: Taking a test for a job
  • From: Harald van Dijk
• Re: Taking a test for a job
  • From: Richard Heathfield
• Re: Has anyone tried something like this to speed up programs?
  • From: Rod Pemberton
• Re: Taking a test for a job
  • From: Tomás
• Re: AI stuff, Was Re: Taking a test for a job
  • From: Rod Pemberton
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: efficient code to do left shit on 64-bit values
  • From: Rod Pemberton
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Andrew Poelstra
• Re: Need experts suggestion
  • From: Andrew Poelstra
• Re: SYNTAX AND SEMANTICS
  • From: Keith Thompson
• Re: SYNTAX AND SEMANTICS
  • From: Joe Estock
• Re: AI stuff, Was Re: Taking a test for a job
  • From: Keith Thompson
• Re: Arrays issue
  • From: Andrew Poelstra
• Re: String Buffers?
  • From: Frank Silvermann
• Re: defines and structure instantiation
  • From: Robert Gamble
• Re: SYNTAX AND SEMANTICS
  • From: Martin Ambuhl
• Re: SYNTAX AND SEMANTICS
  • From: Frank Silvermann
• Re: defines and structure instantiation
  • From: Robert Gamble
• Re: efficient code to do left shit on 64-bit values
  • From: Ben Pfaff
• Re: AI stuff, Was Re: Taking a test for a job
  • From: Allan M. Bruce
• Re: x=(x=5,11)
  • From: Robert Gamble
• Re: x=(x=5,11)
  • From: Richard Tobin
• Re: Need experts suggestion
  • From: Joe Wright
• Re: Need experts suggestion
  • From: Mark McIntyre
• String Buffers?
  • From: Jamie
• Re: x=(x=5,11)
  • From: Robert Gamble
• Re: efficient code to do left shit on 64-bit values
  • From: Eric Sosman
• Re: SYNTAX AND SEMANTICS
  • From: Marc Thrun
• Re: efficient code to do left shit on 64-bit values
  • From: pete
• SYNTAX AND SEMANTICS
  • From: Prof.Stanley
• Re: Generic Sort
  • From: pete
• Re: constant expression with float type
  • From: Erik Wikström
• Re: No more time for stupid questions
  • From: pemo
• Re: No more time for stupid questions
  • From: Richard Heathfield
• Re: No more time for stupid questions
  • From: justfuckengoogleit
• Re: removing a printf statement from my program causes it to crash!?
  • From: James Dow Allen
• Re: problem with functions
  • From: jaysome
• Re: x=(x=5,11)
  • From: pemo
• Re: x=(x=5,11)
  • From: pete
• Re: efficient code to do left shit on 64-bit values
  • From: CBFalconer
• Re: AI stuff, Was Re: Taking a test for a job
  • From: pemo
• Re: Arrays issue
  • From: CBFalconer
• efficient code to do left shit on 64-bit values
  • From: aurgathor
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: x=(x=5,11)
  • From: pemo
• Re: x=(x=5,11)
  • From: pemo
• Re: x=(x=5,11)
  • From: Richard Heathfield
• Re: Generic Sort
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: AI stuff, Was Re: Taking a test for a job
  • From: Allan M. Bruce
• Re: Generic Sort
  • From: AB
• AI stuff, Was Re: Taking a test for a job
  • From: Rod Pemberton
• Re: x=(x=5,11)
  • From: Keith Thompson
• Re: Need experts suggestion
  • From: pete
• Re: x=(x=5,11)
  • From: pete
• Re: Arrays issue
  • From: ataanis
• Re: use same library, other result currupt..
  • From: Ian Collins
• use same library, other result currupt..
  • From: fallleaf
• Re: Taking a test for a job
  • From: Malcolm
• Re: defines and structure instantiation
  • From: Rich
• Re: x=(x=5,11)
  • From: Default User
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: Need experts suggestion
  • From: Malcolm
• Re: x=(x=5,11)
  • From: Frodo Baggins
• Re: x=(x=5,11)
  • From: CBFalconer
• Re: Need experts suggestion
  • From: Artie Gold
• Re: x=(x=5,11)
  • From: Robert Gamble
• Re: Critic of the given code.
  • From: CBFalconer
• Re: x=(x=5,11)
  • From: Jordan Abel
• Re: x=(x=5,11)
  • From: Robert Gamble
• Re: Variable of type DOUBLE converts number strangely.
  • From: Frodo Baggins
• Re: Variable of type DOUBLE converts number strangely.
  • From: Frodo Baggins
• x=(x=5,11)
  • From: Jordan Abel
• Re: defines and structure instantiation
  • From: Robert Gamble
• defines and structure instantiation
  • From: Rich
• constant expression with float type
  • From: aegis
• Re: 8 bit character string to 16 bit character string
  • From: Stephen Sprunk
• Re: Need experts suggestion
  • From: pete
• Re: Has anyone tried something like this to speed up programs?
  • From: Stephen Sprunk
• Re: Generic Sort
  • From: pete
• Re: 8 bit character string to 16 bit character string
  • From: Simon Biber
• Re: Taking a test for a job
  • From: Christopher Benson-Manica
• Re: Arrays issue
  • From: Barry Schwarz
• Re: Generic Sort
  • From: Barry Schwarz
• Re: Taking a test for a job
  • From: Ian Collins
• Re: Taking a test for a job
  • From: Allan M. Bruce
• Re: Variable of type DOUBLE converts number strangely.
  • From: Keith Thompson
• Re: Arrays issue
  • From: Keith Thompson
• Re: Variable of type DOUBLE converts number strangely.
  • From: John
• Re: Variable of type DOUBLE converts number strangely.
  • From: pete
• Re: Variable of type DOUBLE converts number strangely.
  • From: Martin Ambuhl
• Re: Taking a test for a job
  • From: Frank Silvermann
• Re: Arrays issue
  • From: ataanis
• Variable of type DOUBLE converts number strangely.
  • From: John
• Re: Arrays issue
  • From: ataanis
• Re: Arrays issue
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: Arrays issue
  • From: ataanis
• Re: Taking a test for a job
  • From: Ian Collins
• Re: Arrays issue
  • From: ataanis
• Re: Critic of the given code.
  • From: Ian Collins
• Re: Arrays issue
  • From: Richard Heathfield
• Re: Arrays issue
  • From: ataanis
• Re: Arrays issue
  • From: ataanis
• Re: Arrays issue
  • From: ataanis
• Re: Arrays issue
  • From: santosh
• Re: Arrays issue
  • From: ataanis
• Re: Arrays issue
  • From: Flash Gordon
• Re: Arrays issue
  • From: Richard Heathfield
• Re: Arrays issue
  • From: ataanis
• Re: Critic of the given code.
  • From: CBFalconer
• Re: Critic of the given code.
  • From: CBFalconer
• Re: Arrays issue
  • From: santosh
• Re: Critic of the given code.
  • From: CBFalconer
• Re: problem with functions
  • From: CBFalconer
• Re: problem with functions
  • From: CBFalconer
• Re: Taking a test for a job
  • From: Allan M. Bruce
• Re: DEVCPP + rewind(stdin)
  • From: Walter Roberson
• Arrays issue
  • From: ataanis
• Re: Taking a test for a job
  • From: Joe Wright
• Re: Taking a test for a job
  • From: Keith Thompson
• Re: problem with functions
  • From: Keith Thompson
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: problem with functions
  • From: Richard Heathfield
• Re: 8 bit character string to 16 bit character string
  • From: Walter Roberson
• Re: problem with functions
  • From: jacob navia
• Re: Structure through sendto()
  • From: Walter Roberson
• Re: Structure through sendto()
  • From: Kenneth Brody
• Re: Need experts suggestion
  • From: Keith Thompson
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Taking a test for a job
  • From: Allan M. Bruce
• Re: problem with functions
  • From: Keith Thompson
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: 8 bit character string to 16 bit character string
  • From: Brand Bogard
• Structure through sendto()
  • From: ataanis
• Re: problem with functions
  • From: jacob navia
• Re: Need experts suggestion
  • From: Default User
• Re: Need experts suggestion
  • From: Tomás
• Re: Asignments and different signness of the variables
  • From: Tomás
• Re: Router [speedtouch585]
  • From: santosh
• Re: Critic of the given code.
  • From: santosh
• Router [speedtouch585]
  • From: alsowerby
• Re: Critic of the given code.
  • From: Chris Dollin
• Re: about design consideration of strcpy()
  • From: Charles Richmond
• Re: DEVCPP + rewind(stdin)
  • From: Kenneth Brody
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: Frank Silvermann
• Re: Critic of the given code.
  • From: Old Wolf
• Re: Critic of the given code.
  • From: CBFalconer
• Re: Need experts suggestion
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: CBFalconer
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: santosh
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: Critic of the given code.
  • From: santosh
• Re: Critic of the given code.
  • From: Chris Dollin
• Re: Critic of the given code.
  • From: Richard Heathfield
• Re: Need experts suggestion
  • From: CBFalconer
• Re: Need experts suggestion
  • From: Vladimir Oka
• Re: Generic Sort
  • From: Robert Latest
• Critic of the given code.
  • From: santosh
• Re: Need experts suggestion
  • From: CBFalconer
• Re: problem with functions
  • From: Robert Latest
• Re: reading multiple files
  • From: Robert Latest
• Re: 8 bit character string to 16 bit character string
  • From: Haider
• Re: Need experts suggestion
  • From: pemo
• Re: Need experts suggestion
  • From: Gsec
• Re: Need experts suggestion
  • From: Eric Sosman
• Re: Need experts suggestion
  • From: pete
• Re: Need experts suggestion
  • From: Richard Tobin
• Re: [ot]Re: Need experts suggestion
  • From: Vladimir Oka
• Re: Need experts suggestion
  • From: Jordan Abel
• Re: Need experts suggestion
  • From: santosh
• Re: Need experts suggestion
  • From: pete
• [ot]Re: Need experts suggestion
  • From: pete
• Re: Need experts suggestion
  • From: Vladimir Oka
• Re: Need experts suggestion
  • From: Vladimir Oka
• Re: Need experts suggestion
  • From: Richard Heathfield
• Re: Need experts suggestion
  • From: Richard Heathfield
• Re: Need experts suggestion
  • From: santosh
• Re: Need experts suggestion
  • From: Chris Dollin
• Re: Need experts suggestion
  • From: Richard Heathfield
• Re: Need experts suggestion
  • From: Gsec
• [ot]Re: +0.3 microsecond delay for iterating empty vectors
  • From: pete
• Re: Need experts suggestion
  • From: pete
• Re: Need experts suggestion
  • From: Rod Pemberton
• Re: Need experts suggestion
  • From: Gsec
• Re: Need experts suggestion
  • From: Vladimir Oka
• Need experts suggestion
  • From: Gsec
• Re: 8 bit character string to 16 bit character string
  • From: those who know me have no need of my name
• Re: Generic Sort
  • From: AB
• Re: alphabet q
  • From: Keith Thompson
• Re: about design consideration of strcpy()
  • From: pete
• Re: alphabet q
  • From: pete
• Re: alphabet q
  • From: Sjouke Burry
• Re: alphabet q
  • From: Dik T. Winter
• Re: removing a printf statement from my program causes it to crash!?
  • From: Joe Smith
• Re: alphabet q
  • From: Joe Smith
• Re: WHERE can I get the `ANSI C89 specification' related?
  • From: Keith Thompson
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: Keith Thompson
• Re: ++ devils
  • From: jjf
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: krbyxtrm
• Re: WHERE can I get the `ANSI C89 specification' related?
  • From: jjf
• Re: WHERE can I get the `ANSI C89 specification' related?
  • From: alsor.zhou@xxxxxxxxx
• Re: Asignments and different signness of the variables
  • From: pete
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: pete
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: Keith Thompson
• Re: Warning comes when using Unions
  • From: jjf
• Re: Asignments and different signness of the variables
  • From: Barry Schwarz
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: krbyxtrm
• Re: alphabet q
  • From: Keith Thompson
• Re: alphabet q
  • From: Joe Smith
• Re: Asignments and different signness of the variables
  • From: Robert Gamble
• Re: removing a printf statement from my program causes it to crash!?
  • From: Espen Myrland
• Re: Asignments and different signness of the variables
  • From: Walter Roberson
• Re: removing a printf statement from my program causes it to crash!?
  • From: CBFalconer
• Re: Asignments and different signness of the variables
  • From: Tomás
• Re: about design consideration of strcpy()
  • From: CBFalconer
• Re: removing a printf statement from my program causes it to crash!?
  • From: Richard Heathfield
• Re: alphabet q
  • From: Joe Smith
• Asignments and different signness of the variables
  • From: gamehack
• Re: alphabet q
  • From: CBFalconer
• Re: Breaking strings apart
  • From: CBFalconer
• Re: removing a printf statement from my program causes it to crash!?
  • From: Default User
• Re: alphabet q
  • From: Peter Nilsson
• Re: alphabet q
  • From: Keith Thompson
• Re: removing a printf statement from my program causes it to crash!?
  • From: Keith Thompson
• Re: alphabet q
  • From: Ian Collins
• Re: alphabet q
  • From: Joe Smith
• Re: removing a printf statement from my program causes it to crash!?
  • From: Joe Smith
• Re: removing a printf statement from my program causes it to crash!?
  • From: Richard Heathfield
• Re: removing a printf statement from my program causes it to crash!?
  • From: harmanpal@xxxxxxxxx
• Re: alphabet q
  • From: Ian Collins
• Re: removing a printf statement from my program causes it to crash!?
  • From: Marc Thrun
• Re: removing a printf statement from my program causes it to crash!?
  • From: Joe Smith
• Re: DEVCPP + rewind(stdin)
  • From: Jordan Abel
• Re: removing a printf statement from my program causes it to crash!?
  • From: Snis Pilbor
• Re: Breaking strings apart
  • From: noridotjabi@xxxxxxxxx
• removing a printf statement from my program causes it to crash!?
  • From: Harman Dhaliwal
• Re: alphabet q
  • From: Joe Smith
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: Warning comes when using Unions
  • From: Keith Thompson
• Re: Generic Sort
  • From: Michael Mair
• Re: 8 bit character string to 16 bit character string
  • From: Walter Roberson
• Re: alphabet q
  • From: Eric Sosman
• Re: alphabet q
  • From: Walter Roberson
• Re: about design consideration of strcpy()
  • From: Charles Richmond
• Re: problem with functions
  • From: Keith Thompson
• Re: Has anyone tried something like this to speed up programs?
  • From: Snis Pilbor
• Re: about design consideration of strcpy()
  • From: Default User
• Re: Flexible array member and alignement
  • From: Michael Mair
• 8 bit character string to 16 bit character string
  • From: Brand Bogard
• Re: problem with functions
  • From: Eric Sosman
• Re: alphabet q
  • From: Joe Smith
• Re: problem with functions
  • From: jacob navia
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Re: Problem with include header file
  • From: CBFalconer
• Re: Generic Sort
  • From: Ben Pfaff
• Re: Warning comes when using Unions
  • From: CBFalconer
• Re: Generic Sort
  • From: pete
• Re: about design consideration of strcpy()
  • From: CBFalconer
• Re: about design consideration of strcpy()
  • From: Andrew Poelstra
• Re: Generic Sort
  • From: CBFalconer
• Re: Generic Sort
  • From: Ben Pfaff
• Re: problem with functions
  • From: Flash Gordon
• Re: Has anyone tried something like this to speed up programs?
  • From: Kenneth Brody
• Re: DEVCPP + rewind(stdin)
  • From: Kenneth Brody
• Re: about design consideration of strcpy()
  • From: Tomás
• Re: problem with functions
  • From: Eric Sosman
• Re: Problem with include header file
  • From: pete
• Re: Warning comes when using Unions
  • From: William J. Leary Jr.
• Re: problem with functions
  • From: Flash Gordon
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: pete
• Re: Warning comes when using Unions
  • From: Srikanth
• Re: Problem with include header file
  • From: chat
• Re: Generic Sort
  • From: pete
• Re: Has anyone tried something like this to speed up programs?
  • From: jacob navia
• Re: Has anyone tried something like this to speed up programs?
  • From: robertwessel2@xxxxxxxxx
• Re: problem with functions
  • From: Richard Heathfield
• Re: problem with functions
  • From: jacob navia
• Re: Problem with include header file
  • From: Ian Malone
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Re: Warning comes when using Unions
  • From: santosh
• Re: Has anyone tried something like this to speed up programs?
  • From: jacob navia
• Re: Warning comes when using Unions
  • From: Srikanth
• Re: problem with functions
  • From: jacob navia
• Re: Has anyone tried something like this to speed up programs?
  • From: santosh
• Re: reading multiple files
  • From: Richard Heathfield
• Re: Problem with include header file
  • From: Richard Heathfield
• Re: Problem with include header file
  • From: chat
• Re: Problem with include header file
  • From: Martin Ambuhl
• Re: reading multiple files
  • From: Keith Thompson
• Re: Problem with include header file
  • From: Keith Thompson
• Re: about design consideration of strcpy()
  • From: Richard Heathfield
• Re: Problem with include header file
  • From: Ico
• Re: Has anyone tried something like this to speed up programs?
  • From: Keith Thompson
• Re: problem with functions
  • From: Richard Heathfield
• Re: Warning comes when using Unions
  • From: Keith Thompson
• Re: reading multiple files
  • From: Richard Heathfield
• Re: about design consideration of strcpy()
  • From: Keith Thompson
• Re: problem with functions
  • From: Keith Thompson
• Problem with include header file
  • From: chat
• Re: Warning comes when using Unions
  • From: jjf
• Re: Warning comes when using Unions
  • From: Srikanth
• Re: Has anyone tried something like this to speed up programs?
  • From: robertwessel2@xxxxxxxxx
• Re: Generic Sort
  • From: AB
• Re: Warning comes when using Unions
  • From: William J. Leary Jr.
• Re: Has anyone tried something like this to speed up programs?
  • From: Gordon Burditt
• Warning comes when using Unions
  • From: Kantha
• Re: about design consideration of strcpy()
  • From: jacob navia
• Re: about design consideration of strcpy()
  • From: Andrew Poelstra
• Re: about design consideration of strcpy()
  • From: steve yee
• about design consideration of strcpy()
  • From: steve yee
• Re: Has anyone tried something like this to speed up programs?
  • From: jacob navia
• Re: Has anyone tried something like this to speed up programs?
  • From: Jack Klein
• Re: Local structs
  • From: Barry Schwarz
• Re: problem with functions
  • From: jacob navia
• Has anyone tried something like this to speed up programs?
  • From: Snis Pilbor
• Re: -1>>4 and -1<<4
  • From: Walter Roberson
• Re: reading multiple files
  • From: Roberto Waltman
• Re: +0.3 microsecond delay for iterating empty vectors
  • From: Keith Thompson
• Re: Pointer to an array
  • From: Christopher Benson-Manica
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• +0.3 microsecond delay for iterating empty vectors
  • From: krbyxtrm
• Re: Local structs
  • From: Barry Schwarz
• Re: problem with functions
  • From: Eric Sosman
• Re: DEVCPP + rewind(stdin)
  • From: CBFalconer
• Re: [ot]Re: ++ devils
  • From: Joe Smith
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Re: [ot]Re: ++ devils
  • From: Old Wolf
• Re: General rules on interface (function) design
  • From: lovecreatesbeauty
• Re: DEVCPP + rewind(stdin)
  • From: Jordan Abel
• Re: DEVCPP + rewind(stdin)
  • From: Jordan Abel
• Re: fork call
  • From: Joe Smith
• Re: Pointer to an array
  • From: pete
• Re: -1>>4 and -1<<4
  • From: pete
• Re: fork call
  • From: pete
• Re: single-quoting a macro argument
  • From: Marius Lazer
• Re: problem with functions
  • From: Keith Thompson
• Re: single-quoting a macro argument
  • From: Robert Gamble
• Re: problem with functions
  • From: jacob navia
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: single-quoting a macro argument
  • From: Keith Thompson
• Re: problem with functions
  • From: Clever Monkey
• Re: single-quoting a macro argument
  • From: Marius Lazer
• Re: single-quoting a macro argument
  • From: Marius Lazer
• Re: single-quoting a macro argument
  • From: Marius Lazer
• Re: problem with functions
  • From: Keith Thompson
• Re: problem with functions
  • From: jacob navia
• Re: problem with functions
  • From: jacob navia
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Re: single-quoting a macro argument
  • From: CBFalconer
• Re: alphabet q
  • From: Joe Smith
• Re: DEVCPP + rewind(stdin)
  • From: CBFalconer
• Re: single-quoting a macro argument
  • From: Keith Thompson
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: single-quoting a macro argument
  • From: Ben Pfaff
• Re: single-quoting a macro argument
  • From: Andrew Poelstra
• Re: Pointer to an array
  • From: Keith Thompson
• Re: single-quoting a macro argument
  • From: Robert Gamble
• Re: DEVCPP + rewind(stdin)
  • From: Richard Tobin
• Re: DEVCPP + rewind(stdin)
  • From: Keith Thompson
• Re: -1>>4 and -1<<4
  • From: CBFalconer
• Re: fork call
  • From: CBFalconer
• Re: Cannot call a C module from Fortran
  • From: Keith Thompson
• Re: alphabet q
  • From: Keith Thompson
• Re: reading multiple files
  • From: Keith Thompson
• Re: -1>>4 and -1<<4
  • From: Keith Thompson
• Re: alphabet q
  • From: Eric Sosman
• Re: Pointer to an array
  • From: C. Benson Manica
• Re: alphabet q
  • From: Joe Smith
• Re: Pointer to an array
  • From: Keith Thompson
• Re: reading multiple files
  • From: leorulez
• Re: reading multiple files
  • From: SM Ryan
• Re: Pointer to an array
  • From: C. Benson Manica
• Re: alphabet q
  • From: Joe Smith
• Re: problem with functions
  • From: Flash Gordon
• Re: alphabet q
  • From: Eric Sosman
• Re: alphabet q
  • From: Eric Sosman
• Re: alphabet q
  • From: John Devereux
• Re: alphabet q
  • From: Walter Roberson
• Re: alphabet q
  • From: Richard Heathfield
• Re: alphabet q
  • From: Eric Sosman
• Re: single-quoting a macro argument
  • From: David Resnick
• Re: alphabet q
  • From: Walter Roberson
• Re: problem with functions
  • From: Eric Sosman
• Re: alphabet q
  • From: Kenneth Brody
• Re: single-quoting a macro argument
  • From: David Resnick
• Re: single-quoting a macro argument
  • From: Kenneth Brody
• Re: single-quoting a macro argument
  • From: David Resnick
• alphabet q
  • From: Joe Smith
• Re: problem with functions
  • From: jacob navia
• Re: problem with functions
  • From: strictly_mk
• Re: problem with functions
  • From: Walter Roberson
• Re: single-quoting a macro argument
  • From: Kenneth Brody
• problem with functions
  • From: strictly_mk
• Re: single-quoting a macro argument
  • From: Joe Smith
• Re: reading multiple files
  • From: Eric Sosman
• Re: fork call
  • From: Walter Roberson
• Re: reading multiple files
  • From: Richard Heathfield
• Re: fork call
  • From: Sensei
• Re: fork call
  • From: Joe Smith
• Re: single-quoting a macro argument
  • From: Ben Pfaff
• Re: single-quoting a macro argument
  • From: Marius Lazer
• Re: reading multiple files
  • From: leorulez
• Re: Breaking strings apart
  • From: Vladimir Oka
• Re: reading multiple files
  • From: Roberto Waltman
• Re: single-quoting a macro argument
  • From: SM Ryan
• Re: reading multiple files
  • From: SM Ryan
• Re: reading multiple files
  • From: leorulez
• Re: [ot]Re: ++ devils
  • From: Al Balmer
• Re: reading multiple files
  • From: Roberto Waltman
• single-quoting a macro argument
  • From: Marius Lazer
• reading multiple files
  • From: leorulez
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: -1>>4 and -1<<4
  • From: Joe Wright
• Re: Breaking strings apart
  • From: CBFalconer
• Re: Pointer to an array
  • From: John Bode
• Re: About sleep() in child process
  • From: SM Ryan
• Re: Find the size of a datatype
  • From: rmeenaks
• Re: About sleep() in child process
  • From: CBFalconer
• Re: What this mean? Compiler output
  • From: Roberto Waltman
• Re: General rules on interface (function) design
  • From: CBFalconer
• Re: Curses for win32 with VT100/ANSI support
  • From: Andrew Poelstra
• Re: Generic Sort
  • From: pete
• Re: About sleep() in child process
  • From: Kenneth Brody
• Re: Breaking strings apart
  • From: Vladimir Oka
• Re: Breaking strings apart
  • From: pete
• Re: Breaking strings apart
  • From: C. Benson Manica
• Re: Generic Sort
  • From: pete
• Breaking strings apart
  • From: noridotjabi@xxxxxxxxx
• Re: General rules on interface (function) design
  • From: Robert Latest
• Re: General rules on interface (function) design
  • From: pete
• Re: hi hope u dont mined
  • From: noridotjabi@xxxxxxxxx
• Re: [ot]Re: ++ devils
  • From: pete
• Re: Generic Sort
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Richard Bos
• Re: ++ devils
  • From: Richard Tobin
• Re: About sleep() in child process
  • From: pete
• Re: Bytes to bits
  • From: Flash Gordon
• Re: fork call
  • From: pete
• Re: General rules on interface (function) design
  • From: Eric Sosman
• Re: ++ devils
  • From: Dik T. Winter
• Re: Generic Sort
  • From: Tomás
• Re: [ot]Re: ++ devils
  • From: pete
• Re: why can't we use static type as structure member?
  • From: pete
• Re: Generic Sort
  • From: pete
• Re: Generic Sort
  • From: pete
• Re: Local structs
  • From: Tomás
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Const array initialization problem
  • From: Tomás
• Re: [ot]Re: ++ devils
  • From: Richard Heathfield
• [ot]Re: ++ devils
  • From: pete
• hi hope u dont mined
  • From: wazza
• Re: fork call
  • From: CBFalconer
• Re: fork call
  • From: sandy
• Re: ++ devils
  • From: Chris Dollin
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: About sleep() in child process
  • From: sandy
• Re: Generic Sort
  • From: sandy
• Re: Generic Sort
  • From: Richard Heathfield
• Re: What this mean? Compiler output
  • From: Vladimir Oka
• Re: Local structs
  • From: sandy
• Re: exact time
  • From: CBFalconer
• Generic Sort
  • From: AB
• Re: why can't we use static type as structure member?
  • From: sandy
• Re: Const array initialization problem
  • From: Ico
• Re: why can't we use static type as structure member?
  • From: Ben Bacarisse
• Re: Bytes to bits
  • From: CBFalconer
• Re: ++ devils
  • From: Richard Heathfield
• Re: Const array initialization problem
  • From: Richard Heathfield
• What this mean? Compiler output
  • From: Olaf \"El Blanco\"
• Re: ++ devils
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: why can't we use static type as structure member?
  • From: Ian Collins
• Const array initialization problem
  • From: Louis Caron
• Re: ++ devils
  • From: pete
• Re: ++ devils
  • From: Richard Heathfield
• Re: ++ devils
  • From: Chris Dollin
• Re: ++ devils
  • From: Richard Tobin
• why can't we use static type as structure member?
  • From: sandeep
• Re: DEVCPP + rewind(stdin)
  • From: Richard Heathfield
• Re: DEVCPP + rewind(stdin)
  • From: Flash Gordon
• Re: Local structs
  • From: Flash Gordon
• Re: About sleep() in child process
  • From: Anunay
• Re: General rules on interface (function) design
  • From: Robert Latest
• Re: Local structs
  • From: Graham J Lee
• DEVCPP + rewind(stdin)
  • From: Olaf \"El Blanco\"
• Re: How to create a format string used by eg sscanf
  • From: devrobcom
• Re: ++ devils
  • From: Richard Heathfield
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Local structs
  • From: Christian Christmann
• Re: ++ devils
  • From: Nick Keighley
• Re: About sleep() in child process
  • From: Ian Collins
• Re: Cannot call a C module from Fortran
  • From: Cottonwood
• About sleep() in child process
  • From: newgoat
• Re: General rules on interface (function) design
  • From: lovecreatesbeauty
• Re: How to create a format string used by eg sscanf
  • From: mdler
• How to create a format string used by eg sscanf
  • From: devrobcom
• Re: General rules on interface (function) design
  • From: lovecreatesbeauty
• Re: comma expression
  • From: Herbert Rosenau
• Re: fork call
  • From: Keith Thompson
• Re: gcc and command line symbols
  • From: Keith Thompson
• Re: Bytes to bits
  • From: vire
• Re: gcc and command line symbols
  • From: SM Ryan
• Re: fork call
  • From: SM Ryan
• Re: Find the size of a datatype
  • From: vire
• Re: allocate a multidimensional array dynamically
  • From: Yvad
• [ot]Re: Curses for win32 with VT100/ANSI support
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: Alogol-60 [Was: ++ devils]
  • From: Dik T. Winter
• Re: When/why to use size_t
  • From: Joe Smith
• Re: Find the size of a datatype
  • From: Dik T. Winter
• Re: When/why to use size_t
  • From: Keith Thompson
• Re: GTK Libraries in WIndows
  • From: Clever Monkey
• Re: GTK Libraries in WIndows
  • From: Martin Jørgensen
• Re: ++ devils
  • From: Richard Heathfield
• Re: When/why to use size_t
  • From: Richard Heathfield
• Re: Curses for win32 with VT100/ANSI support
  • From: Andrew Poelstra
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Re: Cannot call a C module from Fortran
  • From: Andrew Poelstra
• Re: ++ devils
  • From: Mark McIntyre
• Re: GTK Libraries in WIndows
  • From: Richard Heathfield
• Re: Curses for win32 with VT100/ANSI support
  • From: Mark McIntyre
• Re: Cannot call a C module from Fortran
  • From: Andrew Poelstra
• Re: Cannot call a C module from Fortran
  • From: Flash Gordon
• Re: exact time
  • From: Walter Roberson
• Re: exact time
  • From: Flash Gordon
• Re: Bytes to bits
  • From: Flash Gordon
• Re: ++ devils
  • From: Walter Roberson
• Re: General rules on interface (function) design
  • From: Malcolm
• Re: Pointer to an array
  • From: Flash Gordon
• Re: differance between binary file and ascii file
  • From: S.Tobias
• Re: fork call
  • From: Flash Gordon
• Re: GTK Libraries in WIndows
  • From: Flash Gordon
• Re: fork call
  • From: Julian V. Noble
• Re: fork call
  • From: Clever Monkey
• Re: NIS Service on Solaris
  • From: eoindeb
• Re: NIS Service on Solaris
  • From: Clever Monkey
• Pointer to an array
  • From: Sam
• Re: NIS Service on Solaris
  • From: Keith Thompson
• Re: exact time
  • From: CBFalconer
• NIS Service on Solaris
  • From: eoindeb
• Re: When/why to use size_t
  • From: CBFalconer
• Re: gcc and command line symbols
  • From: David Wade
• Re: Cannot call a C module from Fortran
  • From: CBFalconer
• Re: Find the size of a datatype
  • From: CBFalconer
• Re: Bytes to bits
  • From: CBFalconer
• Re: fork call
  • From: Keith Thompson
• Re: General rules on interface (function) design
  • From: santosh
• Re: fork call
  • From: Joe Smith
• Re: Cannot call a C module from Fortran
  • From: Malcolm
• Re: GTK Libraries in WIndows
  • From: Keith Thompson
• Re: GTK Libraries in WIndows
  • From: santosh
• Re: General rules on interface (function) design
  • From: Eric Sosman
• Re: When/why to use size_t
  • From: Malcolm
• Re: GTK Libraries in WIndows
  • From: richardcarranza
• Re: GTK Libraries in WIndows
  • From: Al Balmer
• Re: Curses for win32 with VT100/ANSI support
  • From: CBFalconer
• Re: GTK Libraries in WIndows
  • From: Malcolm
• Re: GTK Libraries in WIndows
  • From: santosh
• Re: GTK Libraries in WIndows
  • From: Clever Monkey
• Re: fork call
  • From: santosh
• Re: fork call
  • From: Keith Thompson
• Re: GTK Libraries in WIndows
  • From: santosh
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: General rules on interface (function) design
  • From: Malcolm
• Re: General rules on interface (function) design
  • From: Keith Thompson
• Re: Curses for win32 with VT100/ANSI support
  • From: Walter Roberson
• Re: GTK Libraries in WIndows
  • From: richardcarranza
• Re: ++ devils [OT: Goedel]
  • From: John F
• Re: mkdir problem
  • From: Keith Thompson
• Re: Bytes to bits
  • From: Keith Thompson
• Re: Curses for win32 with VT100/ANSI support
  • From: Walter Roberson
• Re: Cannot call a C module from Fortran
  • From: Keith Thompson
• Re: gcc and command line symbols
  • From: Keith Thompson
• Re: Find the size of a datatype
  • From: Keith Thompson
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: Curses for win32 with VT100/ANSI support
  • From: Al Balmer
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: GTK Libraries in WIndows
  • From: Flash Gordon
• Re: Find the size of a datatype
  • From: Keith Thompson
• Re: exact time
  • From: Keith Thompson
• Re: exact time
  • From: Keith Thompson
• Re: ++ devils
  • From: Keith Thompson
• Re: GTK Libraries in WIndows
  • From: santosh
• Re: WHERE can I get the `ANSI C89 specification' related?
  • From: Martin Ambuhl
• Re: Cannot call a C module from Fortran
  • From: Richard Heathfield
• GTK Libraries in WIndows
  • From: richardcarranza
• Re: Curses for win32 with VT100/ANSI support
  • From: Richard Heathfield
• Re: Cannot call a C module from Fortran
  • From: Jordan Abel
• Re: Curses for win32 with VT100/ANSI support
  • From: Skarmander
• Re: Curses for win32 with VT100/ANSI support
  • From: Richard Heathfield
• Re: fork call
  • From: Gordon Burditt
• Re: fork call
  • From: Robert Gamble
• Re: fork call
  • From: Eric Sosman
• fork call
  • From: anshul1806
• Re: Curses for win32 with VT100/ANSI support
  • From: Al Balmer
• Re: General rules on interface (function) design
  • From: Eric Sosman
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Re: General rules on interface (function) design
  • From: August Karlstrom
• Re: What's pointers like *** mean?
  • From: Kenneth Brody
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Re: General rules on interface (function) design
  • From: jacob navia
• Re: General rules on interface (function) design
  • From: Eric Sosman
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: allocate a multidimensional array dynamically
  • From: Vladimir Oka
• Re: General rules on interface (function) design
  • From: lovecreatesbeauty
• Re: Find the size of a datatype
  • From: Flash Gordon
• Re: gcc and command line symbols
  • From: Clever Monkey
• Re: Cannot call a C module from Fortran
  • From: Flash Gordon
• Re: Alogol-60 [Was: ++ devils]
  • From: SM Ryan
• Re: mkdir problem
  • From: SM Ryan
• Re: ++ devils
  • From: Al Balmer
• Re: Cannot call a C module from Fortran
  • From: Richard Heathfield
• Re: Curses for win32 with VT100/ANSI support
  • From: Al Balmer
• Re: Find the size of a datatype
  • From: Richard Bos
• Re: Cannot call a C module from Fortran
  • From: Chris Dollin
• Re: Find the size of a datatype
  • From: Chris Dollin
• Re: When/why to use size_t
  • From: Ben Pfaff
• Re: General rules on interface (function) design
  • From: Richard Heathfield
• Re: General rules on interface (function) design
  • From: Robert Latest
• Re: ++ devils
  • From: Richard Tobin
• Re: Find the size of a datatype
  • From: vire
• Re: Cannot call a C module from Fortran
  • From: Flash Gordon
• Re: Cannot call a C module from Fortran
  • From: Cottonwood
• Re: Find the size of a datatype
  • From: pete
• Re: Cannot call a C module from Fortran
  • From: Andrew Poelstra
• General rules on interface (function) design
  • From: lovecreatesbeauty
• Re: Cannot call a C module from Fortran
  • From: Cottonwood
• Re: Cannot call a C module from Fortran
  • From: Andrew Poelstra
• Re: Find the size of a datatype
  • From: Ico
• Re: Bytes to bits
  • From: vire
• Re: exact time
  • From: Flash Gordon
• Re: ++ devils
  • From: Dik T. Winter
• Re: ++ devils
  • From: Richard Heathfield
• Re: Find the size of a datatype
  • From: Chris Dollin
• Re: ++ devils
  • From: Chris Dollin
• Re: Curses for win32 with VT100/ANSI support
  • From: Richard Heathfield
• Re: Find the size of a datatype
  • From: Vladimir Oka
• Re: Find the size of a datatype
  • From: vire
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: When/why to use size_t
  • From: pete
• Re: Find the size of a datatype
  • From: pete
• Re: When/why to use size_t
  • From: Richard Heathfield
• Re: When/why to use size_t
  • From: pete
• Re: WHERE can I get the `ANSI C89 specification' related?
  • From: Vladimir Oka
• Re: ++ devils
  • From: pete
• WHERE can I get the `ANSI C89 specification' related?
  • From: alsor.zhou@xxxxxxxxx
• Re: Find the size of a datatype
  • From: Richard Heathfield
• Re: exact time
  • From: Henning Hasemann
• Re: When/why to use size_t
  • From: Richard Heathfield
• Re: allocate a multidimensional array dynamically
  • From: Richard Heathfield
• Re: allocate a multidimensional array dynamically
  • From: pete
• Re: ++ devils
  • From: Richard Heathfield
• Re: ++ devils
  • From: Richard Heathfield
• Re: Dynamic Array of Strings
  • From: CBFalconer
• Re: Cannot call a C module from Fortran
  • From: CBFalconer
• Re: About the binary tree
  • From: CBFalconer
• Re: When/why to use size_t
  • From: pete
• Re: allocate a multidimensional array dynamically
  • From: Vladimir Oka
• Re: allocate a multidimensional array dynamically
  • From: Robert Latest
• Re: Cannot call a C module from Fortran
  • From: Cottonwood
• Re: Dynamic Array of Strings
  • From: santosh
• Re: variable sized structures.
  • From: santosh
• Re: Alogol-60 [Was: ++ devils]
  • From: Dik T. Winter
• Re: Testing for EOF in file with binary data
  • From: santosh
• Re: When/why to use size_t
  • From: santosh
• Re: ++ devils
  • From: Vladimir Oka
• Re: allocate a multidimensional array dynamically
  • From: Vladimir Oka
• Re: gcc and command line symbols
  • From: Vladimir Oka
• gcc and command line symbols
  • From: AB
• Alogol-60 [Was: ++ devils]
  • From: Nick Keighley
• Re: ++ devils
  • From: Robert Latest
• Re: allocate a multidimensional array dynamically
  • From: Flash Gordon
• Re: ++ devils
  • From: pete
• Re: Find the size of a datatype
  • From: Flash Gordon
• allocate a multidimensional array dynamically
  • From: Yvad
• Re: type casting
  • From: pete
• Re: exact time
  • From: Chris McDonald
• Re: comma expression
  • From: Keith Thompson
• Re: exact time
  • From: Keith Thompson
• Re: ++ devils
  • From: aone1504
• Re: comma expression
  • From: Alexander Bartolich
• comma expression
  • From: JAY
• Re: exact time
  • From: Chris McDonald
• Re: ++ devils
  • From: Robert Latest
• Re: exact time
  • From: Flash Gordon
• Re: Find the size of a datatype
  • From: vire
• Re: ++ devils
  • From: Flash Gordon
• Re: exact time
  • From: Richard Bos
• Re: ++ devils
  • From: Gordon Burditt
• Re: exact time
  • From: Keith Thompson
• Re: Find the size of a datatype
  • From: Flash Gordon
• exact time
  • From: Henning Hasemann
• Re: ++ devils
  • From: v4vijayakumar
• Re: ++ devils
  • From: aone1504
• When/why to use size_t
  • From: Alex Vinokur
• Re: Find the size of a datatype
  • From: Ico
• Re: About the binary tree
  • From: Yuri CHUANG
• Re: free() multiple allocation error in C
  • From: a.zeevi@xxxxxxxxxxxxxx
• Re: free() multiple allocation error in C
  • From: a.zeevi@xxxxxxxxxxxxxx
• Re: Bytes to bits
  • From: Keith Thompson
• Re: What's pointers like *** mean?
  • From: Keith Thompson
• Re: Bytes to bits
  • From: Vladimir Oka
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: What's pointers like *** mean?
  • From: Yvad
• Re: Bytes to bits
  • From: vire
• Re: What's pointers like *** mean?
  • From: v4vijayakumar
• Re: one simple question
  • From: Jaspreet
• Re: What's pointers like *** mean?
  • From: Bill Pursell
• Re: problem with pointers in c. and dynamic memory allocation
  • From: Bill Pursell
• What's pointers like *** mean?
  • From: Yvad
• Re: Dynamic Array of Strings
  • From: Ian Collins
• Re: Cannot call a C module from Fortran
  • From: Ian Collins
• Dynamic Array of Strings
  • From: bstebroc
• Cannot call a C module from Fortran
  • From: Cottonwood
• Re: ++ devils
  • From: Ben Pfaff
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• problem with pointers in c. and dynamic memory allocation
  • From: manoharyes
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: ++ devils
  • From: Dik T. Winter
• Re: Find the size of a datatype
  • From: jjf
• Re: type casting
  • From: Roman Mashak
• Re: type casting
  • From: Roman Mashak
• Re: Find the size of a datatype
  • From: pete
• Re: Find the size of a datatype
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Walter Roberson
• Re: one simple question
  • From: Martin Jørgensen
• Re: ++ devils
  • From: Richard Tobin
• Re: C beginner: searching in structs (dynamically allocated)
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Andrew Poelstra
• Re: mkdir problem
  • From: CBFalconer
• Re: C beginner: searching in structs (dynamically allocated)
  • From: CBFalconer
• Re: ++ devils
  • From: CBFalconer
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: Raw socket three way handshake
  • From: CBFalconer
• Re: char [0-9] to int [0-9]
  • From: pete
• Re: Random Number Generation
  • From: CBFalconer
• Re: Curses for win32 with VT100/ANSI support
  • From: Walter Roberson
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Find the size of a datatype
  • From: Keith Thompson
• Re: Find the size of a datatype
  • From: Roberto Waltman
• Re: Find the size of a datatype
  • From: Roberto Waltman
• Re: Find the size of a datatype
  • From: Richard Heathfield
• Re: Translate from C/C++ to VB
  • From: Keith Thompson
• Re: Find the size of a datatype
  • From: Vladimir Oka
• Re: Translate from C/C++ to VB
  • From: Vladimir Oka
• Re: Find the size of a datatype
  • From: santosh
• Re: mkdir problem
  • From: eoindeb
• Re: Bytes to bits
  • From: Keith Thompson
• Re: Find the size of a datatype
  • From: Keith Thompson
• Re: Translate from C/C++ to VB
  • From: Keith Thompson
• Re: mkdir problem
  • From: Gordon Burditt
• mkdir problem
  • From: eoindeb
• Re: Raw socket three way handshake
  • From: Brand Bogard
• Re: char [0-9] to int [0-9]
  • From: Harald van Dijk
• Re: char [0-9] to int [0-9]
  • From: Harald van Dijk
• Re: A stylistic question.
  • From: Herbert Rosenau
• Re: C beginner: searching in structs (dynamically allocated)
  • From: David Resnick
• Re: Fatal Error in C
  • From: Vladimir Oka
• C beginner: searching in structs (dynamically allocated)
  • From: Yourko
• Re: ++ devils
  • From: Kenneth Brody
• Re: Curses for win32 with VT100/ANSI support
  • From: Andrew Poelstra
• Re: String move Macro.
  • From: Walter Roberson
• Re: char [0-9] to int [0-9]
  • From: Andrew Poelstra
• Re: String move Macro.
  • From: Al Balmer
• Re: SIGSEGV due to fscanf
  • From: Al Balmer
• Re: [OT] Re: Fatal Error in C
  • From: Joe Smith
• Re: ++ devils
  • From: Al Balmer
• Re: sizeof( int ) != sizeof( void * )
  • From: Joe Smith
• Re: ++ devils
  • From: John Bode
• [OT] Re: Fatal Error in C
  • From: Ico
• Re: Fatal Error in C
  • From: kennethlou
• Re: Find the size of a datatype
  • From: Sunil Varma
• Re: Bytes to bits
  • From: vire
• Re: Fatal Error in C
  • From: Richard Heathfield
• Re: Random Number Generation
  • From: Eric Sosman
• Re: Fatal Error in C
  • From: Roberto Waltman
• Re: one simple question
  • From: Richard Heathfield
• Fatal Error in C
  • From: kennethlou
• Re: Bytes to bits
  • From: vire
• Re: Find the size of a datatype
  • From: Ico
• Re: Bytes to bits
  • From: vire
• Re: Find the size of a datatype
  • From: pete
• Re: Find the size of a datatype
  • From: Vladimir Oka
• Re: Translate from C/C++ to VB
  • From: Roberto Waltman
• Re: Translate from C/C++ to VB
  • From: pete
• Re: Find the size of a datatype
  • From: Chris Dollin
• Re: Translate from C/C++ to VB
  • From: Vladimir Oka
• Find the size of a datatype
  • From: Rahul K
• Re: Translate from C/C++ to VB
  • From: pete
• Re: ++ devils
  • From: pete
• Re: file to array of strings(newbie question)
  • From: CBFalconer
• Re: ++ devils
  • From: v4vijayakumar
• Re: ++ devils
  • From: Vladimir Oka
• Re: Translate from C/C++ to VB
  • From: Vladimir Oka
• Re: ++ devils
  • From: aone1504
• Translate from C/C++ to VB
  • From: koobelek
• Re: one simple question
  • From: Eric Sosman
• Re: one simple question
  • From: ash
• Re: one simple question
  • From: Vladimir Oka
• Re: one simple question
  • From: ash
• Re: one simple question
  • From: Vladimir Oka
• Re: one simple question
  • From: Richard Heathfield
• Re: type casting
  • From: Richard Heathfield
• one simple question
  • From: ash
• Re: type casting
  • From: pete
• Re: type casting
  • From: Richard Heathfield
• Re: type casting
  • From: pete
• Re: type casting
  • From: Tomás
• Re: String move Macro.
  • From: pete
• Re: type casting
  • From: Tomás
• Re: speed of execution
  • From: Richard Harter
• Re: SIGSEGV due to fscanf
  • From: subirs
• Re: speed of execution
  • From: Richard Harter
• Re: speed of execution
  • From: Richard Harter
• Re: String move Macro.
  • From: Giannis Papadopoulos
• Re: Curses for win32 with VT100/ANSI support
  • From: Jordan Abel
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Tim Prince
• type casting
  • From: Roman Mashak
• Re: String move Macro.
  • From: Suman
• Re: varargs question: va_list in structure
  • From: Richard Bos
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: String move Macro.
  • From: Ian Collins
• Re: String move Macro.
  • From: Keith Thompson
• Re: String move Macro.
  • From: Keith Thompson
• Re: file to array of strings(newbie question)
  • From: Vladimir Oka
• Re: String move Macro.
  • From: Richard Heathfield
• Re: String move Macro.
  • From: Vladimir Oka
• Re: String move Macro.
  • From: Richard Heathfield
• Re: String move Macro.
  • From: Richard Heathfield
• Re: String move Macro.
  • From: Vladimir Oka
• Re: String move Macro.
  • From: vashwath
• Re: String move Macro.
  • From: Suman
• Re: String move Macro.
  • From: Vladimir Oka
• Re: A stylistic question.
  • From: Robert Latest
• Re: ++ devils
  • From: Keith Thompson
• Re: Bytes to bits
  • From: Vladimir Oka
• Re: A stylistic question.
  • From: Robert Latest
• String move Macro.
  • From: vashwath
• Re: ++ devils
  • From: Vladimir Oka
• Re: A stylistic question.
  • From: James Dow Allen
• Re: diff between sprintf() and fprintf()
  • From: Richard Bos
• Bytes to bits
  • From: Sync_net
• Re: differance between binary file and ascii file
  • From: Richard Bos
• Re: About the binary tree
  • From: Walter Roberson
• Re: SIGSEGV due to fscanf
  • From: Walter Roberson
• Re: ++ devils
  • From: v4vijayakumar
• Re: Array and Pointer Tutorial
  • From: Richard Bos
• About the binary tree
  • From: Yuri CHUANG
• Re: ++ devils
  • From: Vladimir Oka
• POPL 07 Call for Papers
  • From: sorin . lerner
• Re: ptr
  • From: Vladimir Oka
• Re: ++ devils
  • From: v4vijayakumar
• Re: sizeof( int ) != sizeof( void * )
  • From: Richard Heathfield
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Joe Smith
• sizeof( int ) != sizeof( void * )
  • From: blufox
• Re: [Off-topic] Doubt about doubt
  • From: Joe Smith
• Re: creating pattern using c
  • From: Minlar Ginger
• Re: creating pattern using c
  • From: Richard Heathfield
• Re: creating pattern using c
  • From: Minlar Ginger
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Keith Thompson
• Re: How to sscanf return integer only
  • From: Dave Thompson
• Re: learning name
  • From: Dave Thompson
• Re: simplifying c code with function pointers
  • From: Dave Thompson
• Re: Array and Pointer Tutorial
  • From: Dave Thompson
• Re: Listing the most dangerous parts of C
  • From: Dave Thompson
• Re: creating pattern using c
  • From: CBFalconer
• Re: ++ devils
  • From: CBFalconer
• Re: Incrementing a void pointer. Legal C99?
  • From: Harald van Dijk
• Re: char [0-9] to int [0-9]
  • From: Alex Buell
• Re: creating pattern using c
  • From: pete
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Incrementing a void pointer. Legal C99?
  • From: Keith Thompson
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Joe Smith
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: float.h and math.h
  • From: David Wade
• Re: [Off-topic] Doubt about doubt
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Default User
• Re: writing bits to file
  • From: Malcolm
• Re: checking double for Inf or NaN - how?
  • From: Malcolm
• Re: creating pattern using c
  • From: Martin Jørgensen
• Re: [Off-topic] Doubt about doubt
  • From: John F
• Re: [Off-topic] Doubt about doubt
  • From: Eric
• Re: Curses for win32 with VT100/ANSI support
  • From: Malcolm
• Re: A stylistic question.
  • From: Ian Collins
• Re: Incrementing a void pointer. Legal C99?
  • From: pete
• Re: Incrementing a void pointer. Legal C99?
  • From: Harald van Dijk
• Re: writing bits to file
  • From: Malcolm
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: A stylistic question.
  • From: Herbert Rosenau
• Re: creating pattern using c
  • From: Richard Heathfield
• Re: writing bits to file
  • From: Richard Heathfield
• Re: Incrementing a void pointer. Legal C99?
  • From: Richard Heathfield
• Re: C spot run: initializing variables
  • From: pete
• Re: [Off-topic] Doubt about doubt
  • From: Roberto Waltman
• Re: float.h and math.h
  • From: Robert Gamble
• Re: SIGSEGV due to fscanf
  • From: Ico
• SIGSEGV due to fscanf
  • From: subirs
• Re: creating pattern using c
  • From: Eric Sosman
• Re: [Off-topic] Doubt about doubt
  • From: Ben Pfaff
• Re: creating pattern using c
  • From: Joe Smith
• Re: ++ devils
  • From: David Wade
• Re: float.h and math.h
  • From: David Wade
• Re: ++ devils
  • From: Joe Smith
• Re: creating pattern using c
  • From: Robert Gamble
• Re: ++ devils
  • From: Ben Pfaff
• Re: creating pattern using c
  • From: Roberto Waltman
• Re: C spot run: initializing variables
  • From: lovecreatesbeauty
• [Off-topic] Doubt about doubt
  • From: Roberto Waltman
• Re: The value of variables
  • From: Andrew Poelstra
• creating pattern using c
  • From: anto_kamau
• Re: ++ devils
  • From: John F
• Re: The value of variables
  • From: John F
• Re: ++ devils
  • From: muttaa
• Re: ++ devils
  • From: Robert Gamble
• Re: ++ devils
  • From: Robert Gamble
• Re: ++ devils
  • From: ash
• ++ devils
  • From: muttaa
• Re: writing bits to file
  • From: Keith Thompson
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: float.h and math.h
  • From: Robert Gamble
• Re: Incrementing a void pointer. Legal C99?
  • From: S.Tobias
• Re: Incrementing a void pointer. Legal C99?
  • From: Harald van Dijk
• Re: Incrementing a void pointer. Legal C99?
  • From: pete
• Re: C spot run: initializing variables
  • From: pete
• Re: C spot run: initializing variables
  • From: Bill Pursell
• Re: Incrementing a void pointer. Legal C99?
  • From: pete
• Re: float.h and math.h
  • From: David Wade
• C spot run: initializing variables
  • From: Keith
• Re: writing bits to file
  • From: Richard Heathfield
• Re: The value of variables
  • From: Charles Richmond
• Re: why does this not work?
  • From: Ben Bacarisse
• Re: ptr
  • From: Barry Schwarz
• Re: Size of extern int x;
  • From: Barry Schwarz
• Re: Please Can Anny One Tell What This Declaration Says ?
  • From: Barry Schwarz
• Re: Incrementing a void pointer. Legal C99?
  • From: Harald van Dijk
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Curses for win32 with VT100/ANSI support
  • From: Skarmander
• Re: The value of variables
  • From: minlar
• Re: Curses for win32 with VT100/ANSI support
  • From: Chris Hills
• Re: Incrementing a void pointer. Legal C99?
  • From: Barry Schwarz
• Re: A stylistic question.
  • From: Bill Pursell
• Re: The value of variables
  • From: Martin Ambuhl
• Re: A stylistic question.
  • From: Ian Collins
• Re: A stylistic question.
  • From: Harald van Dijk
• Re: A stylistic question.
  • From: Ian Collins
• Re: A stylistic question.
  • From: Harald van Dijk
• Re: A stylistic question.
  • From: Ian Collins
• Re: A stylistic question.
  • From: Harald van Dijk
• Re: checking double for Inf or NaN - how?
  • From: Malcolm
• Re: A stylistic question.
  • From: Bill Pursell
• Re: Use of diff pointers
  • From: Old Wolf
• Re: why does this not work?
  • From: Default User
• Re: writing bits to file
  • From: Matt Kowalczyk
• Re: writing bits to file
  • From: Malcolm
• writing bits to file
  • From: Matt Kowalczyk
• Re: What's the meaning of this comma?
  • From: Iver.Leung@xxxxxxxxx
• Re: why does this not work?
  • From: Matt Kowalczyk
• What's the meaning of this comma?
  • From: Iver.Leung@xxxxxxxxx
• Re: The value of variables
  • From: Richard Heathfield
• Re: The value of variables
  • From: John F
• Re: why does this not work?
  • From: pete
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: why does this not work?
  • From: Gordon Burditt
• why does this not work?
  • From: Matt Kowalczyk
• Re: Use of diff pointers
  • From: pete
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Netocrat
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Keith Thompson
• FREE Work At Home Job Finder(3325)
  • From: tata20065
• Re: The value of variables
  • From: Keith Thompson
• Re: The value of variables
  • From: Robert Gamble
• Re: The value of variables
  • From: minlar
• Re: The value of variables
  • From: Ian Collins
• Re: The value of variables
  • From: minlar
• Re: The value of variables
  • From: Ian Collins
• Re: The value of variables
  • From: minlar
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Jack Klein
• Re: math.h trig functions questions (and some forgotten high school math)
  • From: Chris McDonald
• Re: Is "hello, world" a constant
  • From: Jack Klein
• Re: The value of variables
  • From: minlar
• Re: The value of variables
  • From: Gordon Burditt
• math.h trig functions questions (and some forgotten high school math)
  • From: Mark Healey
• Re: The value of variables
  • From: Robert Gamble
• The value of variables
  • From: minlar
• Re: A stylistic question.
  • From: Ben Pfaff
• Re: Use of diff pointers
  • From: Dik T. Winter
• Re: char [0-9] to int [0-9]
  • From: Tomás
• Re: Use of diff pointers
  • From: Keith Thompson
• Re: differance between binary file and ascii file
  • From: Ben Bacarisse
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Mike S
• Re: A stylistic question.
  • From: Ian Collins
• Re: Use of diff pointers
  • From: Tomás
• Re: A stylistic question.
  • From: Tomás
• Re: differance between binary file and ascii file
  • From: Dik T. Winter
• Re: A stylistic question.
  • From: Sjouke Burry
• Re: differance between binary file and ascii file
  • From: Keith Thompson
• Re: A stylistic question.
  • From: Ben Pfaff
• Re: differance between binary file and ascii file
  • From: S.Tobias
• Re: A stylistic question.
  • From: Bill Pursell
• Re: Curses for win32 with VT100/ANSI support
  • From: Keith Thompson
• Re: A stylistic question.
  • From: Keith Thompson
• Re: speed of execution
  • From: pete
• Re: speed of execution
  • From: Keith Thompson
• Re: A stylistic question.
  • From: pete
• Re: Use of diff pointers
  • From: Keith Thompson
• Re: Printing files every step
  • From: Richard Heathfield
• Curses for win32 with VT100/ANSI support
  • From: Daniele C.
• Re: Use of diff pointers
  • From: santosh
• Re: Use of diff pointers
  • From: Default User
• Re: float.h and math.h
  • From: Robert Gamble
• Re: Use of diff pointers
  • From: santosh
• Re: Use of diff pointers
  • From: santosh
• Re: Printing files every step
  • From: Mark McIntyre
• Re: A stylistic question.
  • From: Chris Hills
• Re: A stylistic question.
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Andrew Poelstra
• Re: A stylistic question.
  • From: Andrew Poelstra
• Re: float.h and math.h
  • From: David Wade
• Flexible array member and alignement
  • From: tobiasoed
• Re: speed of execution
  • From: Bill Pursell
• Re: Most recent C and C++ standards documents ?
  • From: Robert Gamble
• Re: A stylistic question.
  • From: Bill Pursell
• Re: single x double precision on 32bit arch
  • From: Tim Prince
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: endianness and 64-bit machines
  • From: Richard Heathfield
• Re: endianness and 64-bit machines
  • From: Martin Jørgensen
• Re: A stylistic question.
  • From: pete
• Re: Use of diff pointers
  • From: Roberto Waltman
• Re: Use of diff pointers
  • From: Roberto Waltman
• Re: Most recent C and C++ standards documents ?
  • From: pete
• Re: Raw socket three way handshake
  • From: pete
• Re: A stylistic question.
  • From: Bill Pursell
• Re: speed of execution
  • From: pete
• Raw socket three way handshake
  • From: Marco
• Re: Use of diff pointers
  • From: pete
• Re: A stylistic question.
  • From: James Dow Allen
• Re: endianness and 64-bit machines
  • From: Malcolm
• Re: Use of diff pointers
  • From: Richard Heathfield
• Re: Use of diff pointers
  • From: Comp.Lang.c
• Re: Use of diff pointers
  • From: Comp.Lang.c
• Re: Use of diff pointers
  • From: Typhonike
• Re: checking double for Inf or NaN - how?
  • From: Malcolm
• Re: checking double for Inf or NaN - how?
  • From: Malcolm
• Re: checking double for Inf or NaN - how?
  • From: Malcolm
• Re: Use of diff pointers
  • From: Keith Thompson
• Re: String Matching Problem (NUXI problem) ?
  • From: Malcolm
• Re: speed of execution
  • From: Malcolm
• Re: Use of diff pointers
  • From: Richard Heathfield
• Re: Use of diff pointers
  • From: Comp.Lang.c
• Re: Use of diff pointers
  • From: Richard Heathfield
• Use of diff pointers
  • From: Comp.Lang.c
• Re: Printing files every step
  • From: Jordan Abel
• Re: Printing files every step
  • From: Jordan Abel
• Re: Printing files every step
  • From: Jordan Abel
• Re: Printing files every step
  • From: Keith Thompson
• Re: Printing files every step
  • From: Richard Heathfield
• Re: Printing files every step
  • From: Jordan Abel
• Re: Printing files every step
  • From: Ben Pfaff
• Re: Printing files every step
  • From: Default User
• Re: Printing files every step
  • From: Keith Thompson
• Re: speed of execution
  • From: Thad Smith
• Re: float.h and math.h
  • From: Thad Smith
• Re: Printing files every step
  • From: Gordon Burditt
• Re: pointer
  • From: Thad Smith
• Re: Printing files every step
  • From: Default User
• Re: Printing files every step
  • From: CBFalconer
• Re: Random Number Generation
  • From: Eric
• Re: Printing files every step
  • From: CBFalconer
• Re: Printing files every step
  • From: Keith Thompson
• Re: Printing files every step
  • From: Ben Pfaff
• Re: Printing files every step
  • From: Andrew Poelstra
• Re: Printing files every step
  • From: Gordon Burditt
• Re: speed of execution
  • From: David Wade
• Re: Printing files every step
  • From: Keith Thompson
• Re: speed of execution
  • From: Kevin Handy
• Re: Printing files every step
  • From: Gordon Burditt
• Re: Printing files every step
  • From: Roberto Waltman
• Re: single x double precision on 32bit arch
  • From: Eric
• Re: Printing files every step
  • From: Keith Thompson
• Re: Printing files every step
  • From: Roberto Waltman
• Re: Thread Safe bug-hunt...
  • From: CBFalconer
• Re: File handling question
  • From: Joe Smith
• Re: Printing files every step
  • From: Roberto Waltman
• Re: Printing files every step
  • From: CBFalconer
• Re: Printing files every step
  • From: Clever Monkey
• Re: Printing files every step
  • From: Gordon Burditt
• Re: Good binary PRNG
  • From: CBFalconer
• Re: Printing files every step
  • From: Richard Heathfield
• Re: Printing files every step
  • From: Kenneth Brody
• Re: Is "hello, world" a constant
  • From: Keith Thompson
• Re: single x double precision on 32bit arch
  • From: lawrence . jones
• Re: Good binary PRNG
  • From: Keith Thompson
• Re: speed of execution
  • From: Richard Heathfield
• Re: Good binary PRNG
  • From: Richard Heathfield
• Re: Good binary PRNG
  • From: Eric Sosman
• Re: checking double for Inf or NaN - how?
  • From: P.J. Plauger
• Thread Safe bug-hunt...
  • From: Bill
• Re: Printing files every step
  • From: Keith Thompson
• Re: Is "hello, world" a constant
  • From: ed
• Re: checking double for Inf or NaN - how?
  • From: Keith Thompson
• Is "hello, world" a constant
  • From: lovecreatesbeauty
• Re: Good binary PRNG
  • From: pinkfloydhomer@xxxxxxxxx
• varargs question: va_list in structure
  • From: Rick Anderson
• Re: lower number
  • From: pete
• Re: speed of execution
  • From: Bill Pursell
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: String Matching Problem (NUXI problem) ?
  • From: Ed Prochak
• Re: single x double precision on 32bit arch
  • From: Martin Ambuhl
• Re: Good binary PRNG
  • From: Richard Heathfield
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: endianness and 64-bit machines
  • From: RSoIsCaIrLiIoA
• Re: Linked List
  • From: Rod Pemberton
• Re: Linked List
  • From: Rod Pemberton
• Re: single x double precision on 32bit arch
  • From: Julian V. Noble
• Re: lower number
  • From: Clever Monkey
• Re: lower number
  • From: bert
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Flash Gordon
• Re: speed of execution
  • From: Mike Wahler
• Re: speed of execution
  • From: Default User
• lower number
  • From: temper3243
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: speed of execution
  • From: Nelu
• Re: speed of execution
  • From: Walter Roberson
• Re: speed of execution
  • From: Walter Roberson
• Re: speed of execution
  • From: Andrew Poelstra
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Mike S
• Re: speed of execution
  • From: Clever Monkey
• Re: speed of execution
  • From: Chris Hills
• Re: speed of execution
  • From: Mike Wahler
• Re: single x double precision on 32bit arch
  • From: Mike Wahler
• Re: checking double for Inf or NaN - how?
  • From: Dik T. Winter
• Re: speed of execution
  • From: CBFalconer
• single x double precision on 32bit arch
  • From: R.Biloti
• Re: speed of execution
  • From: Nelu
• Re: speed of execution
  • From: Julian V. Noble
• Re: speed of execution
  • From: Julian V. Noble
• Re: speed of execution
  • From: pete
• Re: Printing files every step
  • From: Roberto Waltman
• Re: speed of execution
  • From: Richard Harter
• Re: speed of execution
  • From: Nelu
• Re: 2/4 bytes boundary problem
  • From: Nelu
• Re: checking double for Inf or NaN - how?
  • From: Richard Tobin
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: checking double for Inf or NaN - how?
  • From: Dave Vandervies
• Re: speed of execution
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: pete
• Re: ptr
  • From: Harald van Dijk
• Re: speed of execution
  • From: pete
• Re: speed of execution
  • From: David Wade
• Re: checking double for Inf or NaN - how?
  • From: pete
• Re: File handling question
  • From: Eric Sosman
• Re: checking double for Inf or NaN - how?
  • From: pete
• Re: checking double for Inf or NaN - how?
  • From: pete
• Re: A stylistic question.
  • From: pete
• Re: ptr
  • From: pete
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: speed of execution
  • From: Chris Hills
• Re: checking double for Inf or NaN - how?
  • From: Chris Hills
• Re: checking double for Inf or NaN - how?
  • From: Richard Tobin
• Re: speed of execution
  • From: David Wade
• Re: A stylistic question.
  • From: Robert Latest
• Re: checking double for Inf or NaN - how?
  • From: Chris Hills
• Re: Forward Reference for Typedef'd Type?
  • From: SM Ryan
• Re: checking double for Inf or NaN - how?
  • From: Chris Hills
• Re: checking double for Inf or NaN - how?
  • From: Chris Hills
• Re: speed of execution
  • From: kwikius
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: speed of execution
  • From: kavi
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: speed of execution
  • From: Richard Heathfield
• Re: speed of execution
  • From: Ian Collins
• speed of execution
  • From: kavi
• Re: A stylistic question.
  • From: ais523
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: 2/4 bytes boundary problem
  • From: Keith Thompson
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: checking double for Inf or NaN - how?
  • From: Keith Thompson
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: ptr
  • From: Harald van Dijk
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Netocrat
• Re: How this code works n
  • From: Herbert Rosenau
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Netocrat
• Re: Linked List
  • From: Jack Klein
• Re: (OT) Dll and Lib (Do Correct Me)
  • From: Christopher Benson-Manica
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Old Wolf
• Re: File handling question
  • From: Old Wolf
• Re: Random Number Generation
  • From: Julian V. Noble
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Mike S
• Re: va_list
  • From: pete
• Re: File handling question
  • From: Eric Sosman
• Re: ptr
  • From: pete
• Re: Linked List
  • From: Al Balmer
• Re: Forward Reference for Typedef'd Type?
  • From: Michael B Allen
• Re: Forward Reference for Typedef'd Type?
  • From: Nelu
• Re: Forward Reference for Typedef'd Type?
  • From: swengineer001@xxxxxxxxx
• Re: Random Number Generation
  • From: Keith Thompson
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: CBFalconer
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: ptr
  • From: CBFalconer
• Re: Random Number Generation
  • From: Richard Heathfield
• Re: Random Number Generation
  • From: Gordon Burditt
• Re: type casting
  • From: CBFalconer
• Re: Random Number Generation
  • From: Richard Heathfield
• Random Number Generation
  • From: muttaa
• Re: Printing files every step
  • From: Mokkapati
• Re: checking double for Inf or NaN - how?
  • From: Richard Heathfield
• Re: Printing files every step
  • From: Gordon Burditt
• Re: Printing files every step
  • From: Eric Sosman
• Re: Forward Reference for Typedef'd Type?
  • From: Keith Thompson
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: Forward Reference for Typedef'd Type?
  • From: Eric Sosman
• Re: Good binary PRNG
  • From: Keith Thompson
• Re: Forward Reference for Typedef'd Type?
  • From: Michael B Allen
• Re: Forward Reference for Typedef'd Type?
  • From: Marc Thrun
• Re: Good binary PRNG
  • From: Eric Sosman
• Printing files every step
  • From: Mokkapati
• Forward Reference for Typedef'd Type?
  • From: Michael B Allen
• float.h and math.h
  • From: David Wade
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: A stylistic question.
  • From: Andrew Poelstra
• Re: Linked List
  • From: Rod Pemberton
• Re: Good binary PRNG
  • From: Richard Heathfield
• Re: File handling question
  • From: Joe Smith
• Re: Good binary PRNG
  • From: Ben Pfaff
• Re: Good binary PRNG
  • From: pinkfloydhomer@xxxxxxxxx
• Re: A stylistic question.
  • From: Andrew Poelstra
• Re: Good binary PRNG
  • From: Richard Heathfield
• Re: String Matching Problem (NUXI problem) ?
  • From: Ben Bacarisse
• Re: Good binary PRNG
  • From: Keith Thompson
• Re: Linked List
  • From: Al Balmer
• Re: va_list
  • From: Keith Thompson
• Re: va_list
  • From: Keith Thompson
• Re: how to find out the address of a variable after I compile the C file
  • From: Keith Thompson
• Re: File handling question
  • From: Richard Heathfield
• Re: Linked List
  • From: Rod Pemberton
• Re: How this code works n
  • From: Steven Tarence Dalton
• Re: ptr
  • From: pete
• Re: va_list
  • From: Rod Pemberton
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: checking double for Inf or NaN - how?
  • From: jacob navia
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: String Matching Problem (NUXI problem) ?
  • From: Jordan Abel
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: File handling question
  • From: Joe Smith
• Re: Good binary PRNG
  • From: Richard Heathfield
• Re: String Matching Problem (NUXI problem) ?
  • From: timmu
• Re: ptr
  • From: Harald van Dijk
• Re: how to find out the address of a variable after I compile the C file
  • From: Walter Roberson
• Re: va_list
  • From: Jordan Abel
• Re: Error using '__attribute__'
  • From: Jordan Abel
• Re: String Matching Problem (NUXI problem) ?
  • From: Bill Pursell
• Re: how to find out the address of a variable after I compile the C file
  • From: Jordan Abel
• Re: Good binary PRNG
  • From: Jordan Abel
• Re: ptr
  • From: Charles Richmond
• Re: Good binary PRNG
  • From: Jordan Abel
• Re: A stylistic question.
  • From: Bill Pursell
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Jordan Abel
• String Matching Problem (NUXI problem) ?
  • From: timmu
• Small Correction to K&R Exercise 1-22 Solution on CLC-Wiki
  • From: Mike S
• Re: how to find out the address of a variable after I compile the C file
  • From: Ben Pfaff
• Re: how to find out the address of a variable after I compile the C file
  • From: Walter Roberson
• Re: checking double for Inf or NaN - how?
  • From: pete
• Re: type casting
  • From: Charles Richmond
• Re: -1>>4 and -1<<4
  • From: Al Balmer
• Re: checking double for Inf or NaN - how?
  • From: bert
• Re: computing t = pow(-11.5, .333)
  • From: Charles Richmond
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: checking double for Inf or NaN - how?
  • From: Joe Smith
• Re: checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: ptr
  • From: pete
• Re: What is wrong with this. (files)
  • From: Richard Heathfield
• checking double for Inf or NaN - how?
  • From: Martin Jørgensen
• Re: Good binary PRNG
  • From: Richard Heathfield
• [ot]Re: What is wrong with this. (files)
  • From: pete
• Re: ptr
  • From: Harald van Dijk
• Re: What is wrong with this. (files)
  • From: jab3
• Re: pointer
  • From: Vladimir Oka
• Re: computing t = pow(-11.5, .333)
  • From: Julian V. Noble
• Re: pointer
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: Julian V. Noble
• Re: pointer
  • From: Andrew Poelstra
• Re: pointer
  • From: pete
• Re: pointer
  • From: Vladimir Oka
• Re: pointer
  • From: Fred Kleinschmidt
• Re: A stylistic question.
  • From: Andrew Poelstra
• Re: How this code works n
  • From: Clever Monkey
• Re: pointer
  • From: Vladimir Oka
• Re: pointer
  • From: Vladimir Oka
• Re: sizeof([ALLOCATED MEMORY])
  • From: Ben Pfaff
• Re: Linked List
  • From: Ben Pfaff
• Re: -1>>4 and -1<<4
  • From: CBFalconer
• Re: pointer
  • From: vim
• pointer
  • From: vim
• Re: overloading, template, exception handling and c
  • From: CBFalconer
• Re: Good binary PRNG
  • From: CBFalconer
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• If you were given a mall would you take?
  • From: Chuck
• Re: how to find out the address of a variable after I compile the C file
  • From: Stephen Sprunk
• Re: -1>>4 and -1<<4
  • From: Robert Latest
• Re: ptr
  • From: pete
• Re: Good binary PRNG
  • From: pete
• Re: ptr
  • From: CoL
• Re: Initializer element Error
  • From: pete
• Re: overloading, template, exception handling and c
  • From: pete
• Re: va_list
  • From: pete
• Re: how to find out the address of a variable after I compile the C file
  • From: Nelu
• Re: Enumerations
  • From: Eric Sosman
• Re: Error using '__attribute__'
  • From: Flash Gordon
• Re: Error using '__attribute__'
  • From: ritesh
• Re: How this code works n
  • From: Vladimir Oka
• Re: Initializer element Error
  • From: vib
• How this code works n
  • From: sgurminder
• Re: overloading, template, exception handling and c
  • From: santosh
• Re: (OT) Dll and Lib (Do Correct Me)
  • From: santosh
• Re: sizeof([ALLOCATED MEMORY])
  • From: ais523
• Re: (OT) Dll and Lib (Do Correct Me)
  • From: pemo
• (OT) Dll and Lib (Do Correct Me)
  • From: ranjeet . gupta
• Re: Binary to ASCII
  • From: jdorrington
• Re: -1>>4 and -1<<4
  • From: Flash Gordon
• Re: -1>>4 and -1<<4
  • From: Eric
• Re: Enumerations
  • From: Vladimir Oka
• Re: Linked List
  • From: jacob navia
• Re: Enumerations
  • From: Christian Christmann
• Re: Binary to ASCII
  • From: Vladimir Oka
• Re: What is wrong with this. (files)
  • From: Richard Heathfield
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: What is wrong with this. (files)
  • From: jab3
• Re: A stylistic question.
  • From: James Dow Allen
• Re: Error using '__attribute__'
  • From: Marc Thrun
• Re: va_list
  • From: Keith Thompson
• Re: Linked List
  • From: Jack Klein
• Re: Error using '__attribute__'
  • From: Bill Pursell
• Linked List
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Richard Heathfield
• Re: va_list
  • From: Richard Heathfield
• Error using '__attribute__'
  • From: ritesh
• Re: how to find out the address of a variable after I compile the C file
  • From: Keith Thompson
• Re: Good binary PRNG
  • From: Keith Thompson
• Re: how to find out the address of a variable after I compile the C file
  • From: Nelu
• Re: Initializer element Error
  • From: Jack Klein
• Re: Good binary PRNG
  • From: Eric Sosman
• Re: computing t = pow(-11.5, .333)
  • From: Jordan Abel
• Re: computing t = pow(-11.5, .333)
  • From: Jordan Abel
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Andrew Poelstra
• Re: Good binary PRNG
  • From: Ben Pfaff
• Initializer element Error
  • From: vib
• Re: Good binary PRNG
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: P.J. Plauger
• Re: how to find out the address of a variable after I compile the C file
  • From: pete
• Re: Good binary PRNG
  • From: Keith Thompson
• Re: how to find out the address of a variable after I compile the C file
  • From: Ian Collins
• how to find out the address of a variable after I compile the C file
  • From: bijayadipti
• Re: Good binary PRNG
  • From: Rod Pemberton
• Re: computing t = pow(-11.5, .333)
  • From: Keith Thompson
• Re: va_list
  • From: Keith Thompson
• Re: computing t = pow(-11.5, .333)
  • From: Ben Pfaff
• Re: New document
  • From: Malcolm
• Re: computing t = pow(-11.5, .333)
  • From: Jordan Abel
• Re: computing t = pow(-11.5, .333)
  • From: Jordan Abel
• Homepages.
  • From: Malcolm
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Malcolm
• Re: program output
  • From: Malcolm
• Re: va_list
  • From: Malcolm
• Re: va_list
  • From: Eric Sosman
• Re: endianness and 64-bit machines
  • From: CBFalconer
• Re: diff between sprintf() and fprintf()
  • From: CBFalconer
• Re: computing t = pow(-11.5, .333)
  • From: CBFalconer
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: va_list
  • From: Keith Thompson
• Re: va_list
  • From: Ben Pfaff
• Re: Binary to ASCII
  • From: Barry
• Re: diff between sprintf() and fprintf()
  • From: Barry
• Re: problem with initiallisation
  • From: Keith Thompson
• Re: computing t = pow(-11.5, .333)
  • From: Keith Thompson
• Re: endianness and 64-bit machines
  • From: Gordon Burditt
• Re: computing t = pow(-11.5, .333)
  • From: Keith Thompson
• endianness and 64-bit machines
  • From: bob_jenkins
• va_list
  • From: mito19651996
• Re: Enumerations
  • From: Default User
• Re: New document
  • From: Keith Thompson
• Re: [ot]Re: Introduce urself
  • From: pete
• Re: Problem with small piece of C code
  • From: Keith Thompson
• Re: Introduce urself
  • From: John F
• Re: New document
  • From: Andrew Poelstra
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: New document
  • From: Herbert Rosenau
• Re: New document
  • From: Herbert Rosenau
• Re: sizeof([ALLOCATED MEMORY])
  • From: Default User
• Re: Introduce urself
  • From: Default User
• Re: Converting Float to unsigned short and Back
  • From: Vladimir Oka
• Re: Converting Float to unsigned short and Back
  • From: Joe Smith
• Re: any floating point library with more exponent bits?
  • From: hrbigelow
• Re: any floating point library with more exponent bits?
  • From: hrbigelow
• Re: computing t = pow(-11.5, .333)
  • From: P.J. Plauger
• Re: computing t = pow(-11.5, .333)
  • From: P.J. Plauger
• Re: Enumerations
  • From: Vladimir Oka
• Re: Enumerations
  • From: Vladimir Oka
• Re: Enumerations
  • From: Eric Sosman
• Re: Enumerations
  • From: jarod.tang@xxxxxxxxx
• Re: ptr
  • From: Vladimir Oka
• Re: ptr
  • From: vim
• Re: ptr
  • From: Vladimir Oka
• Re: ptr
  • From: Vladimir Oka
• Re: [ot]Re: Introduce urself
  • From: Dik T. Winter
• Re: ptr
  • From: HandledException
• Enumerations
  • From: Christian Christmann
• ptr
  • From: vim
• Re: program output
  • From: Richard Heathfield
• Re: diff between sprintf() and fprintf()
  • From: The Grue - James T. Sprinkle
• Re: New document
  • From: jacob navia
• Re: type casting
  • From: CBFalconer
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: New document
  • From: Andrew Poelstra
• Re: program output
  • From: Vladimir Oka
• Re: computing t = pow(-11.5, .333)
  • From: CBFalconer
• Re: File handling question
  • From: Robert Latest
• Re: computing t = pow(-11.5, .333)
  • From: Julian V. Noble
• Re: program output
  • From: Andrew Poelstra
• Re: What is wrong with this. (files)
  • From: Richard Heathfield
• Re: What is wrong with this. (files)
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: What is wrong with this. (files)
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: File handling question
  • From: Bill Pursell
• Re: File handling question
  • From: Jordan Abel
• Re: File handling question
  • From: Eric Sosman
• Re: Binary to ASCII
  • From: Ben Bacarisse
• Re: type casting
  • From: Flash Gordon
• Re: Binary to ASCII
  • From: Vladimir Oka
• Re: stuck with file organisation and global a global array of strings
  • From: ben
• Re: computing t = pow(-11.5, .333)
  • From: P.J. Plauger
• Re: Binary to ASCII
  • From: Vladimir Oka
• Re: File handling question
  • From: Flash Gordon
• Re: type casting
  • From: Vladimir Oka
• Re: Converting Float to unsigned short and Back
  • From: Vladimir Oka
• Re: Binary to ASCII
  • From: Jordan Abel
• Re: CALL to label without another reference crashes
  • From: pemo
• Re: File handling question
  • From: CBFalconer
• Re: CALL to label without another reference crashes
  • From: Flash Gordon
• Re: File handling question
  • From: Richard Heathfield
• Re: File handling question
  • From: Anunay
• Re: Size of extern int x;
  • From: jaysome
• Re: File handling question
  • From: CBFalconer
• Re: File handling question
  • From: Richard Heathfield
• Re: File handling question
  • From: Richard Heathfield
• type casting
  • From: sonu
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: New document
  • From: jacob navia
• Re: File handling question
  • From: Anunay
• Re: CALL to label without another reference crashes
  • From: pemo
• Re: File handling question
  • From: Robert Latest
• Re: Problem with small piece of C code
  • From: CBFalconer
• Re: C code analisys tool
  • From: kazak
• Re: converting inline functions to C functions
  • From: pemo
• Re: File handling question
  • From: Ico
• Re: File handling question
  • From: Friedrich Dominicus
• Re: A trick with if-else
  • From: Chris Dollin
• Re: Binary to ASCII
  • From: Ico
• Re: What is wrong with this. (files)
  • From: Richard Heathfield
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Luca Benini
• Re: Binary to ASCII
  • From: Wrecked
• Re: program output
  • From: santosh
• Re: What is wrong with this. (files)
  • From: Luca Benini
• Re: overloading, template, exception handling and c
  • From: santosh
• Re: Binary to ASCII
  • From: Richard Heathfield
• Binary to ASCII
  • From: Wrecked
• Re: File handling question
  • From: Richard Heathfield
• Re: program output
  • From: sonu
• File handling question
  • From: Anunay
• Re: program output
  • From: jjf
• Re: CALL to label without another reference crashes
  • From: Richard Heathfield
• Re: CALL to label without another reference crashes
  • From: jjf
• CALL to label without another reference crashes
  • From: ReavenK
• Re: type specifiers
  • From: Joe Smith
• Re: differance between binary file and ascii file
  • From: Herbert Rosenau
• Re: register
  • From: Herbert Rosenau
• program output
  • From: sonu
• Re: Problem with small piece of C code
  • From: Peter "Shaggy" Haywood
• Re: type specifiers
  • From: Robert Gamble
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: Listing the most dangerous parts of C
  • From: CBFalconer
• Re: Parsing a simple string
  • From: mathieu
• Re: type specifiers
  • From: CBFalconer
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: P.J. Plauger
• Re: Listing the most dangerous parts of C
  • From: Rod Pemberton
• Re: Converting Float to unsigned short and Back
  • From: Joe Smith
• Re: type specifiers
  • From: Joe Smith
• Re: Introduce urself
  • From: John F
• Re: converting inline functions to C functions
  • From: CBFalconer
• Re: pointer q
  • From: Joe Smith
• Re: New document
  • From: Bill Pursell
• Re: pointer q
  • From: pete
• Re: Introduce urself
  • From: Jordan Abel
• Re: pointer q
  • From: Joe Smith
• Re: converting inline functions to C functions
  • From: pete
• Re: A trick with if-else
  • From: pete
• Re: sizeof([ALLOCATED MEMORY])
  • From: Stephen Sprunk
• Re: stuck with file organisation and global a global array of strings
  • From: SM Ryan
• Re: Introduce urself
  • From: John F
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: converting inline functions to C functions
  • From: jamihuq
• Re: overloading, template, exception handling and c
  • From: John Bode
• Re: pointer q
  • From: Joe Smith
• Re: invalid conversion from void* to int**
  • From: Martin Jørgensen
• Re: Converting Float to unsigned short and Back
  • From: CBFalconer
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: Introduce urself
  • From: Richard Heathfield
• Re: Introduce urself
  • From: Jordan Abel
• Re: overloading, template, exception handling and c
  • From: Andrew Poelstra
• Re: stuck with file organisation and global a global array of strings
  • From: CBFalconer
• Re: using select to read STDIN?
  • From: CBFalconer
• Re: pointer q
  • From: Flash Gordon
• Re: computing t = pow(-11.5, .333)
  • From: Julian V. Noble
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: Converting Float to unsigned short and Back
  • From: Flash Gordon
• Re: Converting Float to unsigned short and Back
  • From: Vladimir Oka
• Re: computing t = pow(-11.5, .333)
  • From: CBFalconer
• Re: A trick with if-else
  • From: Kenneth Brody
• Re: Introduce urself
  • From: CBFalconer
• Re: A trick with if-else
  • From: Kenneth Brody
• Re: overloading, template, exception handling and c
  • From: CBFalconer
• Re: pointer q
  • From: Joe Smith
• Re: Converting Float to unsigned short and Back
  • From: John Devereux
• Re: pointer q
  • From: CBFalconer
• Converting Float to unsigned short and Back
  • From: avsrk
• Re: converting inline functions to C functions
  • From: Flash Gordon
• Re: pointer q
  • From: Flash Gordon
• Re: sizeof([ALLOCATED MEMORY])
  • From: Ion Gaztañaga
• Re: diff between sprintf() and fprintf()
  • From: Fred Kleinschmidt
• Re: stuck with file organisation and global a global array of strings
  • From: pete
• Re: overloading, template, exception handling and c
  • From: Richard Heathfield
• Re: stuck with file organisation and global a global array of strings
  • From: ben
• Re: overloading, template, exception handling and c
  • From: jacob navia
• Re: diff between sprintf() and fprintf()
  • From: Robert Gamble
• Re: diff between sprintf() and fprintf()
  • From: Richard Heathfield
• Re: stuck with file organisation and global a global array of strings
  • From: pete
• Re: A trick with if-else
  • From: Richard Heathfield
• Re: A trick with if-else
  • From: Martin Ambuhl
• Re: diff between sprintf() and fprintf()
  • From: Ben Pfaff
• Re: using select to read STDIN?
  • From: ifmusic
• Re: What is wrong with this. (files)
  • From: pete
• diff between sprintf() and fprintf()
  • From: mknarang.nsit
• Re: A trick with if-else
  • From: Keith Thompson
• Re: stuck with file organisation and global a global array of strings
  • From: Roberto Waltman
• Re: New document
  • From: jacob navia
• Re: stuck with file organisation and global a global array of strings
  • From: Walter Roberson
• Re: computing t = pow(-11.5, .333)
  • From: John Smith
• Re: overloading, template, exception handling and c
  • From: Andrew Poelstra
• stuck with file organisation and global a global array of strings
  • From: ben
• Re: Introduce urself
  • From: Ben Pfaff
• Re: Introduce urself
  • From: Clever Monkey
• Re: Introduce urself
  • From: Clever Monkey
• Re: Introduce urself
  • From: Clever Monkey
• Re: using select to read STDIN?
  • From: Robert Gamble
• using select to read STDIN?
  • From: ifmusic
• Re: int fact( int n )
  • From: Clever Monkey
• Re: pointer q
  • From: Joe Smith
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Felix Kater
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Eric Sosman
• Re: What is wrong with this. (files)
  • From: Richard Heathfield
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: John Devereux
• Re: converting inline functions to C functions
  • From: Eric Sosman
• Re: New document
  • From: Giannis Papadopoulos
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Eric Sosman
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Andrew Poelstra
• converting inline functions to C functions
  • From: jamihuq
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Eric Sosman
• Re: Introduce urself
  • From: Martin Jørgensen
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Flash Gordon
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Vladimir Oka
• Re: What is wrong with this. (files)
  • From: Vladimir Oka
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Felix Kater
• Re: What is wrong with this. (files)
  • From: Ben C
• Re: What is wrong with this. (files)
  • From: Flash Gordon
• Re: What is wrong with this. (files)
  • From: Bill Pursell
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: A trick with if-else
  • From: Chris Dollin
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Felix Kater
• Re: What is wrong with this. (files)
  • From: Eric Sosman
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Eric Sosman
• Re: A trick with if-else
  • From: Chris Dollin
• Re: A trick with if-else
  • From: Chris Dollin
• Re: va_list: how to produce warnings at compile time if called incorrectly?
  • From: Flash Gordon
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: What is wrong with this. (files)
  • From: noridotjabi@xxxxxxxxx
• Re: A trick with if-else
  • From: Suman
• Re: A trick with if-else
  • From: John Devereux
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: differance between binary file and ascii file
  • From: Ben Pfaff
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: A trick with if-else
  • From: Suman
• Re: A trick with if-else
  • From: John Devereux
• Re: What is wrong with this. (files)
  • From: jacob navia
• Re: A trick with if-else
  • From: Kenneth Brody
• Re: overloading, template, exception handling and c
  • From: jacob navia
• Re: 2/4 bytes boundary problem
  • From: Eric Sosman
• Re: 2/4 bytes boundary problem
  • From: Thomas.Chang
• Re: Random Seeding
  • From: Eric Sosman
• Re: computing t = pow(-11.5, .333)
  • From: Kenneth Brody
• [ot]Re: Introduce urself
  • From: pete
• Re: A trick with if-else
  • From: Richard Heathfield
• Re: What is wrong with this. (files)
  • From: CBFalconer
• Re: A trick with if-else
  • From: Chris Dollin
• Re: A trick with if-else
  • From: Vladimir Oka
• Re: int fact( int n )
  • From: CBFalconer
• A trick with if-else
  • From: Piyush Agarwal
• Re: Introduce urself
  • From: Richard Heathfield
• va_list: how to produce warnings at compile time if called incorrectly?
  • From: Felix Kater
• Re: overloading, template, exception handling and c
  • From: CBFalconer
• Re: Introduce urself
  • From: Richard Tobin
• Re: sprintf: anomalous behavior
  • From: Marc Thrun
• Re: Extern functions inside library
  • From: Ico
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Extern functions inside library
  • From: karthy
• Re: What is wrong with this. (files)
  • From: Roberto Waltman
• Re: What is wrong with this. (files)
  • From: pete
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: 2/4 bytes boundary problem
  • From: Thomas.Chang
• Re: help with types needed
  • From: Ben
• What is wrong with this. (files)
  • From: noridotjabi@xxxxxxxxx
• Re: problem with initiallisation
  • From: vim
• Re: Random Seeding
  • From: websnarf
• Re: Random Seeding
  • From: websnarf
• Re: computing t = pow(-11.5, .333)
  • From: Julian V. Noble
• Re: Introduce urself
  • From: Dik T. Winter
• Re: void struct
  • From: Richard Heathfield
• void struct
  • From: v4vijayakumar
• Re: int fact( int n )
  • From: Richard Heathfield
• Re: Size of extern int x;
  • From: Richard Heathfield
• Re: int fact( int n )
  • From: Giannis Papadopoulos
• Re: int fact( int n )
  • From: Vladimir Oka
• Re: Size of extern int x;
  • From: Vladimir Oka
• Re: int fact( int n )
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: int fact( int n )
  • From: Vladimir Oka
• Re: int fact( int n )
  • From: jacob navia
• Re: Size of extern int x;
  • From: skishorev
• int fact( int n )
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: Size of extern int x;
  • From: Chris McDonald
• Size of extern int x;
  • From: skishorev
• Re: sizeof([ALLOCATED MEMORY])
  • From: Flash Gordon
• Re: FREE Work At Home Job Finder
  • From: santosh
• Re: overloading, template, exception handling and c
  • From: jacob navia
• Re: Introduce urself
  • From: CBFalconer
• Re: sprintf: anomalous behavior
  • From: Vladimir Oka
• Re: register
  • From: Flash Gordon
• Re: sprintf: anomalous behavior
  • From: Flash Gordon
• Re: register
  • From: Zara
• Re: overloading, template, exception handling and c
  • From: CBFalconer
• Re: pointer q
  • From: Flash Gordon
• Re: string parametres becoming empty
  • From: Flash Gordon
• Re: differance between binary file and ascii file
  • From: Flash Gordon
• Re: Introduce urself
  • From: Ben C
• Re: sprintf: anomalous behavior
  • From: Ivan78
• Re: Introduce urself
  • From: ais523
• Re: Random Seeding
  • From: porterboy76
• Re: FREE Work At Home Job Finder
  • From: CBFalconer
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: Introduce urself
  • From: Richard Heathfield
• Re: Introduce urself
  • From: v4vijayakumar
• Re: arrays
  • From: Keith Thompson
• Re: register
  • From: Zara
• Re: Random Seeding
  • From: porterboy76
• Re: 2/4 bytes boundary problem
  • From: Richard Heathfield
• Re: Introduce urself
  • From: santosh
• Re: Introduce urself
  • From: santosh
• Re: A stylistic question.
  • From: Ian Collins
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: Dynamic tracing of C code execution
  • From: Frank Pittel
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: switch why?
  • From: Neil
• Re: register
  • From: Al Balmer
• Re: Introduce urself
  • From: pete
• Re: Introduce urself
  • From: Jaspreet
• Re: Introduce urself
  • From: Keith Thompson
• Re: a struct parser
  • From: Herbert Rosenau
• Re: A stylistic question.
  • From: Herbert Rosenau
• Re: arrays
  • From: Herbert Rosenau
• Re: differance between binary file and ascii file
  • From: Herbert Rosenau
• Re: differance between binary file and ascii file
  • From: Herbert Rosenau
• Re: Introduce urself
  • From: Martin Jørgensen
• Re: computing t = pow(-11.5, .333)
  • From: Jordan Abel
• Re: help with types needed
  • From: Jack Klein
• Re: string parametres becoming empty
  • From: Jordan Abel
• Re: FREE Work At Home Job Finder
  • From: wangqiongyue888
• Re: help with types needed
  • From: Eric
• Re: overloading, template, exception handling and c
  • From: Jack Klein
• Re: differance between binary file and ascii file
  • From: pete
• Re: differance between binary file and ascii file
  • From: Mike S
• Re: sizeof([ALLOCATED MEMORY])
  • From: pete
• Re: 2/4 bytes boundary problem
  • From: Nelu
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: sizeof([ALLOCATED MEMORY])
  • From: pete
• Re: Introduce urself
  • From: pete
• help with types needed
  • From: Ben
• Re: computing t = pow(-11.5, .333)
  • From: Dik T. Winter
• Re: computing t = pow(-11.5, .333)
  • From: Howard Hinnant
• Re: computing t = pow(-11.5, .333)
  • From: Eric Sosman
• Re: sprintf: anomalous behavior
  • From: lovecreatesbeauty
• Re: computing t = pow(-11.5, .333)
  • From: CBFalconer
• Re: computing t = pow(-11.5, .333)
  • From: Robert Gamble
• Re: differance between binary file and ascii file
  • From: CBFalconer
• Re: Introduce urself
  • From: Dik T. Winter
• Re: computing t = pow(-11.5, .333)
  • From: Robert Gamble
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: computing t = pow(-11.5, .333)
  • From: pete
• Re: Random Seeding
  • From: Dik T. Winter
• computing t = pow(-11.5, .333)
  • From: John Smith
• Re: Introduce urself
  • From: CBFalconer
• Re: differance between binary file and ascii file
  • From: P.J. Plauger
• Re: Introduce urself
  • From: mensanator@xxxxxxx
• Re: Introduce urself
  • From: Ian Collins
• Re: sizeof([ALLOCATED MEMORY])
  • From: Howard Hinnant
• Re: Introduce urself
  • From: Default User
• Re: Parsers for C
  • From: Ira Baxter
• Re: Dynamic tracing of C code execution
  • From: Ira Baxter
• Re: Introduce urself
  • From: Nikesh
• type specifiers
  • From: Joe Smith
• Re: short or int
  • From: Ian Collins
• Re: Rounding Float in C and Remove those Zeros
  • From: Dik T. Winter
• Re: short or int
  • From: pete
• Re: short or int
  • From: Keith Thompson
• Re: Random Seeding
  • From: Eric Sosman
• Re: Random Seeding
  • From: porterboy76
• Re: overloading, template, exception handling and c
  • From: CBFalconer
• Re: eratosthenos
  • From: Joe Smith
• Re: Pragma
  • From: Ian Collins
• Re: pointer q
  • From: CBFalconer
• Re: Rounding Float in C and Remove those Zeros
  • From: John Bode
• Re: Rounding Float in C and Remove those Zeros
  • From: Skarmander
• Re: switch why?
  • From: Keith Thompson
• Re: Random Seeding
  • From: Keith Thompson
• Re: PLEASE HELP - How do I include OpenSSL in my code?
  • From: Martin Ambuhl
• Re: 2/4 bytes boundary problem
  • From: Default User
• Re: Question c faq
  • From: CBFalconer
• Re: Rounding Float in C and Remove those Zeros
  • From: Keith Thompson
• Re: overloading, template, exception handling and c
  • From: Default User
• Re: problem including perl header files
  • From: Keith Thompson
• Re: Question c faq
  • From: CBFalconer
• Re: pointer q
  • From: Joe Smith
• Re: switch why?
  • From: Martin Ambuhl
• Re: switch why?
  • From: cbmanica
• Re: A stylistic question.
  • From: CBFalconer
• Re: C code analisys tool
  • From: Keith Thompson
• Re: Pragma
  • From: CBFalconer
• Re: switch why?
  • From: Clever Monkey
• Re: differance between binary file and ascii file
  • From: CBFalconer
• Re: 2/4 bytes boundary problem
  • From: Andrew Poelstra
• Re: 2/4 bytes boundary problem
  • From: Vladimir Oka
• Re: differance between binary file and ascii file
  • From: CBFalconer
• Re: 2/4 bytes boundary problem
  • From: Rafael Almeida
• Re: switch why?
  • From: Keith Thompson
• Re: C code analisys tool
  • From: CBFalconer
• Re: overloading, template, exception handling and c
  • From: Flash Gordon
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: pointer q
  • From: RSoIsCaIrLiIoA
• Re: pointer q
  • From: RSoIsCaIrLiIoA
• Re: overloading, template, exception handling and c
  • From: JesusWaffle@xxxxxxxxx
• Re: Introduce urself
  • From: Martin Jørgensen
• Re: sprintf: anomalous behavior
  • From: Marc Thrun
• Re: Array and Pointer Tutorial
  • From: Default User
• Re: sprintf: anomalous behavior
  • From: lovecreatesbeauty
• Re: sprintf: anomalous behavior
  • From: Kenneth Brody
• Re: switch why?
  • From: Kenneth Brody
• Re: 2/4 bytes boundary problem
  • From: Robert Gamble
• Re: sprintf: anomalous behavior
  • From: pemo
• Re: sprintf: anomalous behavior
  • From: pemo
• Re: sprintf: anomalous behavior
  • From: lovecreatesbeauty
• Re: Help needed in a simple UDP socket program
  • From: Vitali Gontsharuk
• Re: Help needed in a simple UDP socket program
  • From: santosh
• Help needed in a simple UDP socket program
  • From: Vitali Gontsharuk
• Re: Introduce urself
  • From: santosh
• Re: switch why?
  • From: Clever Monkey
• Re: Introduce urself
  • From: Richard Tobin
• Re: PLEASE HELP - How do I include OpenSSL in my code?
  • From: Clever Monkey
• Re: short or int
  • From: Richard Heathfield
• Re: Extracting output from system(3) call
  • From: Kevin Bagust
• Re: problem with initiallisation
  • From: KOFKS
• Re: sprintf: anomalous behavior
  • From: Marc Thrun
• Re: C code analisys tool
  • From: Al Balmer
• Re: sprintf: anomalous behavior
  • From: Flash Gordon
• Re: overloading, template, exception handling and c
  • From: Bill Pursell
• Re: Array and Pointer Tutorial
  • From: Al Balmer
• Re: sprintf: anomalous behavior
  • From: pemo
• Re: problem with initiallisation
  • From: Flash Gordon
• Re: switch why?
  • From: Eric Sosman
• Re: problem with initiallisation
  • From: Flash Gordon
• Re: sprintf: anomalous behavior
  • From: Gordon Burditt
• Re: arrays
  • From: Andrew Poelstra
• Re: problem with initiallisation
  • From: Bill Pursell
• Re: Array and Pointer Tutorial
  • From: Al Balmer
• Re: problem with initiallisation
  • From: Eric Sosman
• Re: 2/4 bytes boundary problem
  • From: Flash Gordon
• Re: problem with initiallisation
  • From: KOFKS
• Re: pointer q
  • From: Flash Gordon
• Re: switch why?
  • From: pemo
• sprintf: anomalous behavior
  • From: Ivan78
• Re: short or int
  • From: Simon Biber
• Re: Extracting output from system(3) call
  • From: Flash Gordon
• Re: arrays
  • From: Flash Gordon
• Re: switch why?
  • From: Roberto Waltman
• Re: switch why?
  • From: Roberto Waltman
• Re: switch why?
  • From: vim
• Re: switch why?
  • From: pemo
• Re: switch why?
  • From: Vladimir Oka
• Re: 2/4 bytes boundary problem
  • From: Duncan Muirhead
• switch why?
  • From: vim
• problem with initiallisation
  • From: vim
• Re: Introduce urself
  • From: Joe Smith
• Re: 2/4 bytes boundary problem
  • From: Andrew Poelstra
• Re: Where is the printf body defined?
  • From: Joe Smith
• Re: 2/4 bytes boundary problem
  • From: Andrew Poelstra
• Re: pointer q
  • From: Joe Smith
• Re: Introduce urself
  • From: zhongjiechao@xxxxxxxxx
• Re: vsprintf(char *str, const char *format, va_list ap, ...)?
  • From: rory . brandybuck
• Re: Pragma
  • From: Clever Monkey
• Re: Random Seeding
  • From: Dik T. Winter
• Re: 2/4 bytes boundary problem
  • From: zhongjiechao@xxxxxxxxx
• Re: string parametres becoming empty
  • From: Fred Kleinschmidt
• Introduce urself
  • From: Nikesh
• Re: For loops help
  • From: Andrew Poelstra
• Re: 2/4 bytes boundary problem
  • From: Robert Gamble
• Re: short or int
  • From: Kenneth Brody
• Re: Pragma
  • From: Kenneth Brody
• Re: Random Seeding
  • From: Gordon Burditt
• Re: arrays
  • From: Andrew Poelstra
• Re: 2/4 bytes boundary problem
  • From: Andrew Poelstra
• Re: differance between binary file and ascii file
  • From: Kenneth Brody
• Re: 2/4 bytes boundary problem
  • From: Flash Gordon
• Re: Extracting output from system(3) call
  • From: Kenneth Brody
• Re: Please Can Anny One Tell What This Declaration Says ?
  • From: S.Tobias
• Re: differance between binary file and ascii file
  • From: Flash Gordon
• 2/4 bytes boundary problem
  • From: Thomas.Chang
• Re: Please Can Anny One Tell What This Declaration Says ?
  • From: Haroon Shafiq
• Re: differance between binary file and ascii file
  • From: P.J. Plauger
• Re: Random Seeding
  • From: porterboy76
• Re: Please Can Anny One Tell What This Declaration Says ?
  • From: rory . brandybuck
• Re: differance between binary file and ascii file
  • From: Joe Wright
• Re: Random Seeding
  • From: rory . brandybuck
• Random Seeding
  • From: porterboy76
• Re: a struct parser
  • From: Eric Sosman
• Re: differance between binary file and ascii file
  • From: S.Tobias
• Please Can Anny One Tell What This Declaration Says ?
  • From: code break
• Re: Extracting output from system(3) call
  • From: Flash Gordon
• Re: Pragma
  • From: Eric Sosman
• Re: Rounding Float in C and Remove those Zeros
  • From: Joe Wright
• Re: Extracting output from system(3) call
  • From: Flash Gordon
• Re: problem including header files in TC
  • From: Flash Gordon
• Re: Windows equivalent of fstatfs() or fstatvfs()?
  • From: Mike
• Re: Extracting output from system(3) call
  • From: v4vijayakumar
• Re: overloading, template, exception handling and c
  • From: Ian Collins
• Re: overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: problem including perl header files
  • From: Flash Gordon
• Re: Extracting output from system(3) call
  • From: Jordan Abel
• Re: Good binary PRNG
  • From: Flash Gordon
• Re: string parametres becoming empty
  • From: Flash Gordon
• Re: Extracting output from system(3) call
  • From: v4vijayakumar
• Re: overloading, template, exception handling and c
  • From: Ian Collins
• Re: overloading, template, exception handling and c
  • From: jacob navia
• overloading, template, exception handling and c
  • From: v4vijayakumar
• Re: Array and Pointer Tutorial
  • From: pete
• Re: Extracting output from system(3) call
  • From: SM Ryan
• Re: Array and Pointer Tutorial
  • From: pete
• Re: differance between binary file and ascii file
  • From: Robert Latest
• Re: C code analisys tool
  • From: jacob navia
• Re: variable - modifiable lvalue
  • From: websnarf
• problem including header files in TC
  • From: shruti
• Re: string parametres becoming empty
  • From: "Nils O. Selåsdal"
• Re: string parametres becoming empty
  • From: Erik
• Re: Extracting output from system(3) call
  • From: Flash Gordon
• problem including perl header files
  • From: shruti
• Good binary PRNG
  • From: pinkfloydhomer@xxxxxxxxx
• Re: string parametres becoming empty
  • From: "Nils O. Selåsdal"
• Re: string parametres becoming empty
  • From: Erik
• Re: string parametres becoming empty
  • From: Ivan78
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: C code analisys tool
  • From: Richard Heathfield
• Re: C code analisys tool
  • From: kazak
• Re: Extracting output from system(3) call
  • From: v4vijayakumar
• Re: string parametres becoming empty
  • From: Ian Collins
• Re: short or int
  • From: Chris Hills
• Re: short or int
  • From: SM Ryan
• Re: pointer q
  • From: RSoIsCaIrLiIoA
• Re: Listing the most dangerous parts of C
  • From: RSoIsCaIrLiIoA
• Re: How to sscanf return integer only
  • From: RSoIsCaIrLiIoA
• Re: The void** pointer breaking symmetry?
  • From: RSoIsCaIrLiIoA
• Re: string parametres becoming empty
  • From: Erik
• Re: string parametres becoming empty
  • From: "Nils O. Selåsdal"
• Re: A stylistic question.
  • From: James Dow Allen
• Re: string parametres becoming empty
  • From: Erik
• Re: any floating point library with more exponent bits?
  • From: jacob navia
• Re: string parametres becoming empty
  • From: Ian Collins
• Re: Portable integer type which can hold int, wchar_t, and void *
  • From: Keith Thompson
• string parametres becoming empty
  • From: Erik
• variable - modifiable lvalue
  • From: v4vijayakumar
• Re: sizeof([ALLOCATED MEMORY])
  • From: S.Tobias
• Re: any floating point library with more exponent bits?
  • From: azi . stdout
• Re: strtok problem
  • From: Charles Richmond
• Re: strtok problem
  • From: Vladimir Oka
• Re: A stylistic question.
  • From: Ian Collins
• Re: short or int
  • From: Ian Collins
• Re: strtok problem
  • From: Victor Eijkhout
• Re: Does this make sense?
  • From: Mark Healey
• Re: any floating point library with more exponent bits?
  • From: hrbigelow
• Re: learning name
  • From: Neil
• Re: Windows equivalent of fstatfs() or fstatvfs()?
  • From: Dave
• Re: short or int
  • From: Herbert Rosenau
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Herbert Rosenau
• Re: a struct parser
  • From: Herbert Rosenau
• Re: A stylistic question.
  • From: Herbert Rosenau
• Re: differance between binary file and ascii file
  • From: Herbert Rosenau
• Re: any floating point library with more exponent bits?
  • From: Gordon Burditt
• any floating point library with more exponent bits?
  • From: hrbigelow
• Re: Where is the printf body defined?
  • From: Mike Wahler
• Where is the printf body defined?
  • From: jeniffer
• Re: Windows equivalent of fstatfs() or fstatvfs()?
  • From: Keith Thompson
• Re: vsprintf(char *str, const char *format, va_list ap, ...)?
  • From: kyle.tk
• Re: Portable integer type which can hold int, wchar_t, and void *
  • From: Ben Pfaff
• Windows equivalent of fstatfs() or fstatvfs()?
  • From: Dave
• Re: short or int
  • From: Dave Vandervies
• Re: 3n+1 problem revised
  • From: Keith Thompson
• Portable integer type which can hold int, wchar_t, and void *
  • From: JesusWaffle@xxxxxxxxx
• Re: vsprintf(char *str, const char *format, va_list ap, ...)?
  • From: goldfita
• Re: vsprintf(char *str, const char *format, va_list ap, ...)?
  • From: JesusWaffle
• Re: How to sscanf return integer only
  • From: Robert Gamble
• Re: strtok problem
  • From: pete
• Re: Question c faq
  • From: Christopher Benson-Manica
• Re: What are Threads?
  • From: pete
• Re: strtok problem
  • From: Christopher Benson-Manica
• Re: For loops help
  • From: Chris F.A. Johnson
• Re: How to convert from a struct tm to a time_t ?
  • From: Ben Hetland
• Re: arrays
  • From: pete
• Re: short or int
  • From: pete
• Re: Pragma
  • From: swengineer001@xxxxxxxxx
• strtok problem
  • From: Victor Eijkhout
• Re: Pragma
  • From: swengineer001@xxxxxxxxx
• Re: 3n+1 problem revised
  • From: Joe Wright
• vsprintf(char *str, const char *format, va_list ap, ...)?
  • From: goldfita
• Re: Pragma
  • From: Ian Collins
• Re: differance between binary file and ascii file
  • From: Dik T. Winter
• Re: differance between binary file and ascii file
  • From: Malcolm
• Re: Question c faq
  • From: Ben C
• Re: Question c faq
  • From: Eric Sosman
• Re: Does this make sense?
  • From: Richard Heathfield
• Re: Question c faq
  • From: Malcolm
• Re: sizeof([ALLOCATED MEMORY])
  • From: Howard Hinnant
• Re: Question c faq
  • From: Ben C
• Re: sizeof([ALLOCATED MEMORY])
  • From: Joe Wright
• Re: differance between binary file and ascii file
  • From: Mike S
• Re: How to sscanf return integer only
  • From: Dave Thompson
• Re: Incrementing a void pointer. Legal C99?
  • From: Dave Thompson
• Re: Boost process and C
  • From: Dave Thompson
• Re: Question c faq
  • From: Eric Sosman
• Re: Does this make sense?
  • From: Neil
• Re: pointer q
  • From: Joe Smith
• Re: A stylistic question.
  • From: Keith Thompson
• Re: Question c faq
  • From: Keith Thompson
• Re: For loops help
  • From: Keith Thompson
• Re: pointer q
  • From: Keith Thompson
• Re: short or int
  • From: Chris Hills
• Re: Question c faq
  • From: Keith Thompson
• Re: differance between binary file and ascii file
  • From: P.J. Plauger
• Re: Question c faq
  • From: Keith Thompson
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: What are Threads?
  • From: CBFalconer
• Re: For loops help
  • From: Andrew Poelstra
• Re: Question c faq
  • From: CBFalconer
• Re: Question c faq
  • From: Emilio
• Re: A stylistic question.
  • From: CBFalconer
• Re: pointer q
  • From: Coos Haak
• Re: Question c faq
  • From: Emilio
• Re: differance between binary file and ascii file
  • From: CBFalconer
• Re: pointer q
  • From: Joe Smith
• Re: What are Threads?
  • From: Flash Gordon
• Re: Question c faq
  • From: Emilio
• Re: Problem with small piece of C code
  • From: Keith Thompson
• Re: For loops help
  • From: Vladimir Oka
• Re: Question c faq
  • From: Eric Sosman
• Re: short or int
  • From: Keith Thompson
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: What are Threads?
  • From: Alexander Bartolich
• Re: A stylistic question.
  • From: Keith Thompson
• What are Threads?
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: differance between binary file and ascii file
  • From: Keith Thompson
• Question c faq
  • From: Emilio
• Re: differance between binary file and ascii file
  • From: Keith Thompson
• Re: differance between binary file and ascii file
  • From: Keith Thompson
• Re: sizeof([ALLOCATED MEMORY])
  • From: Keith Thompson
• Re: pointer q
  • From: Eric Sosman
• Re: pointer q
  • From: Flash Gordon
• Re: differance between binary file and ascii file
  • From: Martin Ambuhl
• Re: For loops help
  • From: CBFalconer
• Re: For loops help
  • From: Andrew Poelstra
• Re: arrays
  • From: CBFalconer
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: arrays
  • From: Richard Heathfield
• Re: arrays
  • From: mdh
• Re: arrays
  • From: Richard Heathfield
• Re: arrays
  • From: mdh
• Re: arrays
  • From: Andrew Poelstra
• Re: short or int
  • From: Chris Hills
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Richard Heathfield
• Re: Overloaded vendor library routine: is this C++? Or very clever C?
  • From: "Nils O. Selåsdal"
• Re: arrays
  • From: Alexander Bartolich
• Re: short or int
  • From: Jordan Abel
• Re: pointer q
  • From: Joe Smith
• arrays
  • From: mdh
• Re: differance between binary file and ascii file
  • From: P.J. Plauger
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Andrew Poelstra
• Re: short or int
  • From: SM Ryan
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Andrew Poelstra
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: short or int
  • From: Chris Hills
• Re: learning name
  • From: CBFalconer
• Re: sizeof([ALLOCATED MEMORY])
  • From: Gordon Burditt
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: noridotjabi@xxxxxxxxx
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Ben C
• Re: short or int
  • From: Flash Gordon
• Re: Overloaded vendor library routine: is this C++? Or very clever C?
  • From: Jack Daly
• Re: Does this make sense?
  • From: Simon Biber
• Re: Array and Pointer Tutorial
  • From: CBFalconer
• Re: Problem with small piece of C code
  • From: CBFalconer
• Re: Problem with small piece of C code
  • From: Ulrich Eckhardt
• Re: short or int
  • From: Simon Biber
• Re: sizeof([ALLOCATED MEMORY])
  • From: Joe Wright
• Re: short or int
  • From: john
• Re: short or int
  • From: CBFalconer
• Re: Pragma
  • From: pete
• Re: short or int
  • From: pete
• Re: pointer q
  • From: Eric Sosman
• Re: JPEG and C language..
  • From: Martin Jørgensen
• Re: Pragma
  • From: Eric Sosman
• Re: short or int
  • From: Chris Hills
• Problem with small piece of C code
  • From: kalyan . listsubs
• Re: short or int
  • From: john
• Re: short or int
  • From: Richard Heathfield
• Re: JPEG and C language..
  • From: Richard Heathfield
• short or int
  • From: john
• Re: JPEG and C language..
  • From: pete
• Re: differance between binary file and ascii file
  • From: pete
• Re: JPEG and C language..
  • From: Simon Biber
• Re: differance between binary file and ascii file
  • From: Flash Gordon
• Re: JPEG and C language..
  • From: Simon Biber
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: differance between binary file and ascii file
  • From: Chris Hills
• Re: For loops help
  • From: CBFalconer
• Re: A stylistic question.
  • From: pete
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: Array and Pointer Tutorial
  • From: pete
• Re: Array and Pointer Tutorial
  • From: pete
• Re: differance between binary file and ascii file
  • From: pete
• Re: differance between binary file and ascii file
  • From: Flash Gordon
• Re: A stylistic question.
  • From: Chris Hills
• Re: sizeof([ALLOCATED MEMORY])
  • From: CBFalconer
• Re: For loops help
  • From: zwjzhangwenjin
• Re: Does this make sense?
  • From: Malcolm
• Re: For loops help
  • From: Keith Thompson
• Re: sizeof([ALLOCATED MEMORY])
  • From: Keith Thompson
• Re: a struct parser
  • From: Keith Thompson
• Re: For loops help
  • From: Toni
• Re: differance between binary file and ascii file
  • From: Keith Thompson
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: SM Ryan
• Re: learning name
  • From: SM Ryan
• Re: A stylistic question.
  • From: Ian Collins
• Re: A stylistic question.
  • From: Toni
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: a struct parser
  • From: Friedrich Dominicus
• Re: A stylistic question.
  • From: Bill Pursell
• Re: A stylistic question.
  • From: Richard Heathfield
• Re: Does this make sense?
  • From: Richard Heathfield
• A stylistic question.
  • From: Mark Healey
• Re: differance between binary file and ascii file
  • From: jjf
• Does this make sense?
  • From: Mark Healey
• Re: differance between binary file and ascii file
  • From: jjf
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: differance between binary file and ascii file
  • From: Alan
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: differance between binary file and ascii file
  • From: Alan
• Re: Array and Pointer Tutorial
  • From: Keith Thompson
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: differance between binary file and ascii file
  • From: Mike S
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: Array and Pointer Tutorial
  • From: Keith Thompson
• Re: Array and Pointer Tutorial
  • From: Keith Thompson
• Re: pointer q
  • From: Keith Thompson
• Re: Bitwise AND etc
  • From: Peter "Shaggy" Haywood
• Re: invalid conversion from void* to int**
  • From: Keith Thompson
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: noridotjabi@xxxxxxxxx
• Re: invalid conversion from void* to int**
  • From: Martin Jørgensen
• Re: pointer q
  • From: Joe Smith
• Re: Pragma
  • From: Ian Collins
• Re: Pragma
  • From: Gordon Burditt
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Gordon Burditt
• Re: How to increase stack space/heap space
  • From: pete
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: noridotjabi@xxxxxxxxx
• LOADEXE or LOADO: For those of you that have been following my posts
  • From: noridotjabi@xxxxxxxxx
• Re: getchar() problem
  • From: Peter "Shaggy" Haywood
• Re: libclc - from Boost thread
  • From: Peter "Shaggy" Haywood
• Re: learning name
  • From: Walter Roberson
• Re: Writting Pluggins
  • From: noridotjabi@xxxxxxxxx
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Walter Roberson
• Re: Pragma
  • From: swengineer001@xxxxxxxxx
• Re: invalid conversion from void* to int**
  • From: Flash Gordon
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Ben C
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Gordon Burditt
• Re: invalid conversion from void* to int**
  • From: Marc Thrun
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Richard Tobin
• invalid conversion from void* to int**
  • From: Martin Jørgensen
• Re: How to increase stack space/heap space
  • From: Ian Collins
• Re: Compiler error for "wrong" sized type
  • From: David White
• Re: puttextxy( int x, int y, char far *const );
  • From: Malcolm
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Flash Gordon
• Re: Writting Pluggins
  • From: Malcolm
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: noridotjabi@xxxxxxxxx
• Re: Rounding Float in C and Remove those Zeros
  • From: Malcolm
• Re: How to increase stack space/heap space
  • From: Malcolm
• Re: Quick way to zero array
  • From: Malcolm
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Ben C
• Re: Pragma
  • From: Eric Sosman
• Re: getchar() problem
  • From: Keith Thompson
• Re: learning name
  • From: Keith Thompson
• Re: learning name
  • From: Keith Thompson
• Re: pointer q
  • From: Keith Thompson
• Re: Address in int
  • From: Keith Thompson
• Re: Parsing a simple string
  • From: Default User
• Re: Address in int
  • From: Keith Thompson
• Pragma
  • From: muttaa
• Re: 1)Executing by reading from executable 2)Compileing in a program
  • From: Flash Gordon
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Richard Heathfield
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Martin Ambuhl
• Re: continue with switch
  • From: Herbert Rosenau
• Re: Dynamic tracing of C code execution
  • From: Walter Bright
• NovelSpace Media, LLC announces the launch of their new online bookstore and web portal devoted to developers and programmers.
  • From: paquejd
• Re: pointer q
  • From: Ben Pfaff
• Re: PLEASE HELP - How do I include OpenSSL in my code? <OT: Cryptographic laws>
  • From: Andrew Poelstra
• 1)Executing by reading from executable 2)Compileing in a program
  • From: noridotjabi@xxxxxxxxx
• Re: Writting Pluggins
  • From: noridotjabi@xxxxxxxxx
• Re: Writting Pluggins
  • From: Andrew Poelstra
• pointer q
  • From: Joe Smith
• Re: learning name
  • From: Thad Smith
• Re: Address in int
  • From: Alexander Bartolich
• Re: Address in int
  • From: Richard Heathfield
• Address in int
  • From: john
• Re: differance between binary file and ascii file
  • From: santosh
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• Re: learning name
  • From: Ico
• Re: Writting Pluggins
  • From: Mike Wahler
• Re: [OT]Re: Extracting output from system(3) call
  • From: Mike Wahler
• Re: differance between binary file and ascii file
  • From: Parahat Melayev
• Re: differance between binary file and ascii file
  • From: vim
• Re: Bitwise AND etc
  • From: John Devereux
• Re: learning name
  • From: Parahat Melayev
• Re: differance between binary file and ascii file
  • From: Richard Heathfield
• differance between binary file and ascii file
  • From: vim
• Re: Extracting output from system(3) call
  • From: SM Ryan
• Re: JPEG and C language..
  • From: Richard Heathfield
• Re: JPEG and C language..
  • From: Parahat Melayev
• Re: learning name
  • From: CBFalconer
• Re: JPEG and C language..
  • From: Parahat Melayev
• Re: puttextxy( int x, int y, char far *const );
  • From: CBFalconer
• Re: JPEG and C language..
  • From: CBFalconer
• Re: learning name
  • From: Parahat Melayev
• Re: JPEG and C language..
  • From: Parahat Melayev
• Re: [OT]Re: Extracting output from system(3) call
  • From: Martin Jørgensen
• Re: JPEG and C language..
  • From: Martin Jørgensen
• learning name
  • From: Parahat Melayev
• Re: JPEG and C language..
  • From: Richard Heathfield
• Re: JPEG and C language..
  • From: Ico
• Re: JPEG and C language..
  • From: Ramesh
• Re: puttextxy( int x, int y, char far *const );
  • From: pemo
• Re: puttextxy( int x, int y, char far *const );
  • From: Michael Brennan
• Re: puttextxy( int x, int y, char far *const );
  • From: Vladimir Oka
• Re: Extracting output from system(3) call
  • From: Keith Thompson
• Re: puttextxy( int x, int y, char far *const );
  • From: venkatesh.k.desai5@xxxxxxxxx
• Re: puttextxy( int x, int y, char far *const );
  • From: Richard Heathfield
• puttextxy( int x, int y, char far *const );
  • From: venkatesh.k.desai5@xxxxxxxxx
• [OT]Re: Extracting output from system(3) call
  • From: Robert Harris
• Re: Writting Pluggins
  • From: Malcolm
• An Amazing offer
  • From: im4u143@xxxxxxxxx
• Re: function prototypes and declarations
  • From: goldfita
• Re: function prototypes and declarations
  • From: goldfita
• Re: function prototypes and declarations
  • From: Harald van Dijk
• Re: Extracting output from system(3) call
  • From: v4vijayakumar
• Re: function prototypes and declarations
  • From: Michael Mair
• Re: Extracting output from system(3) call
  • From: v4vijayakumar
• Re: Compiler error for "wrong" sized type
  • From: Harald van Dijk
• Re: getchar() problem
  • From: Alan
• Re: function prototypes and declarations
  • From: jacob navia
• Extracting output from system(3) call
  • From: v4vijayakumar
• function prototypes and declarations
  • From: goldfita
• Re: Off topic Re: Iteration vs. Recursion
  • From: Ben Pfaff
• Re: Parsing a simple string
  • From: Keith Thompson
• Re: Parsing a simple string
  • From: SM Ryan
• Re: continue with switch
  • From: CBFalconer
• Re: simplifying c code with function pointers
  • From: Thad Smith
• Writting A Psudo Filesystem
  • From: noridotjabi@xxxxxxxxx
• Re: Bitwise AND etc
  • From: Lew Pitcher
• Writting Pluggins
  • From: noridotjabi@xxxxxxxxx
• Re: Bitwise AND etc
  • From: Keith Thompson
• Re: swapping bytes in an integer
  • From: pete
• Re: Array and Pointer Tutorial
  • From: Richard Heathfield
• Re: Array and Pointer Tutorial
  • From: Rod Pemberton
• Re: swapping bytes in an integer
  • From: pete
• Re: Bitwise AND etc
  • From: jjf
• Re: Bitwise AND etc
  • From: Richard Heathfield
• Re: Quick way to zero array
  • From: Himanshu Chauhan
• Re: Bitwise AND etc
  • From: Lew Pitcher
• Re: Array and Pointer Tutorial
  • From: Richard Heathfield
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: Help regarding Josepheus problem.
  • From: Rod Pemberton
• Re: Rounding Float in C and Remove those Zeros
  • From: Dik T. Winter
• Re: Array and Pointer Tutorial
  • From: Flash Gordon
• Re: Array and Pointer Tutorial
  • From: Rod Pemberton
• Re: continue with switch
  • From: Rod Pemberton
• Re: Quick way to zero array
  • From: Rod Pemberton
• Re: continue with switch
  • From: Flash Gordon
• Re: Array and Pointer Tutorial
  • From: Richard Heathfield
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: Compiler error for "wrong" sized type
  • From: S.Tobias
• Re: Array and Pointer Tutorial
  • From: Rod Pemberton
• Re: PLEASE HELP - How do I include OpenSSL in my code?
  • From: Ben C
• Re: PLEASE HELP - How do I include OpenSSL in my code?
  • From: Martin Ambuhl
• Re: 64 bit Endianness issue
  • From: Ian Collins
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: PLEASE HELP - How do I include OpenSSL in my code?
  • From: Richard Heathfield
• Re: Bitwise AND etc
  • From: Rod Pemberton
• PLEASE HELP - How do I include OpenSSL in my code?
  • From: cpptutor2000@xxxxxxxxx
• Re: 64 bit Endianness issue
  • From: Gordon Burditt
• Re: Quick way to zero array
  • From: rocketman768
• Re: Compiler error for "wrong" sized type
  • From: tedu
• Re: continue with switch
  • From: Keith Thompson
• Re: continue with switch
  • From: Keith Thompson
• Re: 64 bit Endianness issue
  • From: Flash Gordon
• Re: How to convert from a struct tm to a time_t ?
  • From: Eric Sosman
• Re: 64 bit Endianness issue
  • From: Ian Collins
• Re: How to convert from a struct tm to a time_t ?
  • From: jjf
• Re: Quick way to zero array
  • From: Flash Gordon
• Re: How to convert from a struct tm to a time_t ?
  • From: Gordon Burditt
• Re: continue with switch
  • From: tedu
• Re: dynamic mem alloc q
  • From: Keith Thompson
• Re: 64 bit Endianness issue
  • From: Gordon Burditt
• Re: Quick way to zero array
  • From: Keith Thompson
• Re: Rounding Float in C and Remove those Zeros
  • From: Skarmander
• Re: continue with switch
  • From: Flash Gordon
• Re: continue with switch
  • From: Andrew Poelstra
• Re: How to simulate a key press?
  • From: doina
• Re: Avoiding malloc
  • From: Ben Hetland
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: Avoiding malloc
  • From: John Devereux
• Re: Quick way to zero array
  • From: Julian V. Noble
• Re: Avoiding malloc
  • From: Stephen Sprunk
• Re: Dynamic tracing of C code execution
  • From: Michael Mair
• Re: Dynamic tracing of C code execution
  • From: Vladimir Oka
• Re: Rounding Float in C and Remove those Zeros
  • From: Vladimir Oka
• Dynamic tracing of C code execution
  • From: Nikhil
• Re: request for a program
  • From: Default User
• Re: continue with switch
  • From: Default User
• Re: Help regarding Josepheus problem.
  • From: vcp
• Re: Compiler error for "wrong" sized type
  • From: Kenneth Brody
• Re: <OT> Re: continue with switch
  • From: CBFalconer
• Re: Quick way to zero array
  • From: Michael Mair
• Re: Quick way to zero array
  • From: Vladimir Oka
• Re: Rounding Float in C and Remove those Zeros
  • From: Vladimir Oka
• Re: Quick way to zero array
  • From: Ben C
• Re: request for a program
  • From: Ben C
• Re: Avoiding malloc
  • From: Joe Smith
• Re: request for a program
  • From: Duncan Muirhead
• <OT> Re: continue with switch
  • From: Andrew Poelstra
• Re: strtok causes Segmentation fault
  • From: void * clvrmnky()
• Re: Listing the most dangerous parts of C
  • From: Walter Banks
• Re: Quick way to zero array
  • From: prax
• Re: continue with switch
  • From: void * clvrmnky()
• Quick way to zero array
  • From: rocketman768
• Re: continue with switch
  • From: CBFalconer
• Re: request for a program
  • From: rocketman768
• Re: 64 bit Endianness issue
  • From: CBFalconer
• Re: Array and Pointer Tutorial
  • From: CBFalconer
• Re: continue with switch
  • From: Bart Rider
• Re: JPEG and C language..
  • From: Vladimir Oka
• Re: Rounding Float in C and Remove those Zeros
  • From: Vladimir Oka
• Re: strtok causes Segmentation fault
  • From: Nelu
• Re: How to simulate a key press?
  • From: Vladimir Oka
• Rounding Float in C and Remove those Zeros
  • From: kennethlou
• JPEG and C language..
  • From: Ramesh
• Re: Avoiding malloc
  • From: John Devereux
• Re: Avoiding malloc
  • From: those who know me have no need of my name
• Re: continue with switch
  • From: Flash Gordon
• Re: continue with switch
  • From: Richard Heathfield
• Re: Compiler error for "wrong" sized type
  • From: Eric Sosman
• Re: 3n+1 problem revised
  • From: pete
• Re: continue with switch
  • From: pete
• Re: continue with switch
  • From: v4vijayakumar
• Re: Sizes of integers
  • From: those who know me have no need of my name
• Re: Avoiding malloc
  • From: Ben Hetland
• Re: request for a program
  • From: Richard Heathfield
• request for a program
  • From: kumar
• request for a program
  • From: kumar
• Re: How to convert from a struct tm to a time_t ?
  • From: Ben Hetland
• Re: returning address of stack variable
  • From: pete
• Re: Array and Pointer Tutorial
  • From: Chad
• Re: Array and Pointer Tutorial
  • From: Chad
• Re: returning address of stack variable
  • From: CoL
• Re: continue with switch
  • From: Flash Gordon
• Re: continue with switch
  • From: pete
• Re: returning address of stack variable
  • From: Richard Heathfield
• Re: Compiler error for "wrong" sized type
  • From: David White
• Re: returning address of stack variable
  • From: pete
• Re: Avoiding malloc
  • From: John Devereux
• Re: Help regarding Josepheus problem.
  • From: Rohini Ramamurthy
• Re: Avoiding malloc
  • From: John Devereux
• Re: Array and Pointer Tutorial
  • From: pete
• Re: continue with switch
  • From: Richard Heathfield
• Re: continue with switch
  • From: Bart Rider
• Re: Avoiding malloc
  • From: John Devereux
• Re: continue with switch
  • From: Bart Rider
• Re: How to convert from a struct tm to a time_t ?
  • From: pete
• Re: continue with switch
  • From: Richard Bos
• Re: How to convert from a struct tm to a time_t ?
  • From: Richard Bos
• continue with switch
  • From: v4vijayakumar
• How to convert from a struct tm to a time_t ?
  • From: Angus Comber
• Re: 64 bit Endianness issue
  • From: Flash Gordon
• Re: Compiler error for "wrong" sized type
  • From: Richard Heathfield
• Re: Avoiding malloc
  • From: Flash Gordon
• Help regarding Josepheus problem.
  • From: Rohini Ramamurthy
• Re: C code analisys tool
  • From: kazak
• Re: Array and Pointer Tutorial
  • From: Richard Heathfield
• Re: Visual Studio 2005 compatiblity with VC6
  • From: Flash Gordon
• Re: Avoiding malloc
  • From: Ivan Vecerina
• Re: sizeof([ALLOCATED MEMORY])
  • From: Ion Gaztañaga
• Re: Array and Pointer Tutorial
  • From: Flash Gordon
• Re: 64 bit Endianness issue
  • From: sureshjayaram
• Re: Avoiding malloc
  • From: Ian Collins
• Re: Array and Pointer Tutorial
  • From: pemo
• Re: Compiler error for "wrong" sized type
  • From: Nick Keighley
• Avoiding malloc
  • From: John Devereux
• Re: 64 bit Endianness issue
  • From: Ian Collins
• Re: A little quiz on macros
  • From: Old Wolf
• Re: C code analisys tool
  • From: Ben C
• Re: const int in header: linker error
  • From: Old Wolf
• Re: How to increase stack space/heap space
  • From: Old Wolf
• Re: 64 bit Endianness issue
  • From: Gordon Burditt
• Re: 64 bit Endianness issue
  • From: sureshjayaram
• Re: 64 bit Endianness issue
  • From: Ian Collins
• Re: How to simulate a key press?
  • From: Ian Collins
• How to simulate a key press?
  • From: Joel
• Re: 64 bit Endianness issue
  • From: sureshjayaram
• Re: returning address of stack variable
  • From: Suman
• Re: Compiler error for "wrong" sized type
  • From: David White
• Re: Compiler error for "wrong" sized type
  • From: David White
• Re: 64 bit Endianness issue
  • From: Ian Collins
• Re: Array and Pointer Tutorial
  • From: Ian Collins
• Re: 64 bit Endianness issue
  • From: sureshjayaram
• Re: Visual Studio 2005 compatiblity with VC6
  • From: websnarf
• Re: strtok causes Segmentation fault
  • From: Jack Klein
• Re: C code analisys tool
  • From: Mark Laczynski
• Re: Array and Pointer Tutorial
  • From: Chad
• Re: Array and Pointer Tutorial
  • From: Jack Klein
• Re: Compiler error for "wrong" sized type
  • From: Bill Pursell
• Re: returning address of stack variable
  • From: websnarf
• Re: How to increase stack space/heap space
  • From: Jack Klein
• Re: Array and Pointer Tutorial
  • From: Richard Heathfield
• Re: Array and Pointer Tutorial
  • From: Chad
• Re: returning address of stack variable
  • From: websnarf
• Re: Compiler error for "wrong" sized type
  • From: Keith Thompson
• Re: Visual Studio 2005 compatiblity with VC6
  • From: Espen Myrland
• Re: Array and Pointer Tutorial
  • From: pete
• Re: Array and Pointer Tutorial
  • From: pete
• Re: Compiler error for "wrong" sized type
  • From: Richard Heathfield
• Compiler error for "wrong" sized type
  • From: David White
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: Array and Pointer Tutorial
  • From: pete
• Re: Array and Pointer Tutorial
  • From: Nelu
• Re: Sizes of integers
  • From: Richard Heathfield
• Re: dynamic mem alloc q
  • From: Nelu
• Re: const int in header: linker error
  • From: pete
• Visual Studio 2005 compatiblity with VC6
  • From: carl
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: strtok causes Segmentation fault
  • From: Default User
• Re: strtok causes Segmentation fault
  • From: pete
• Re: strtok causes Segmentation fault
  • From: bofh1234
• Re: strtok causes Segmentation fault
  • From: Default User
• Re: dynamic mem alloc q
  • From: Keith Thompson
• Re: Array and Pointer Tutorial
  • From: pete
• Re: strtok causes Segmentation fault
  • From: bofh1234
• Re: returning address of stack variable
  • From: Stephen Sprunk
• Re: How to increase stack space/heap space
  • From: Stephen Sprunk
• Re: storing delimited string in an array
  • From: CBFalconer
• Re: strtok causes Segmentation fault
  • From: CBFalconer
• Re: Sizes of integers
  • From: Stephen Sprunk
• Re: strtok causes Segmentation fault
  • From: Default User
• Re: Array and Pointer Tutorial
  • From: CBFalconer
• Re: strtok causes Segmentation fault
  • From: bofh1234
• Re: sizeof([ALLOCATED MEMORY])
  • From: Stephen Sprunk
• Re: Iteration vs. Recursion
  • From: Andrew Poelstra
• Re: C code analisys tool
  • From: jacob navia
• Re: C code analisys tool
  • From: Ian Collins
• Re: returning address of stack variable
  • From: Keith Thompson
• Re: C code analisys tool
  • From: pibru@xxxxxx
• Re: C code analisys tool
  • From: jacob navia
• Re: Parsing a simple string
  • From: Keith Thompson
• Re: C code analisys tool
  • From: Ian Collins
• Re: Sizes of integers
  • From: Malcolm
• Re: How to increase stack space/heap space
  • From: Ian Collins
• Re: C code analisys tool
  • From: jacob navia
• C code analisys tool
  • From: kazak
• Re: sizeof([ALLOCATED MEMORY])
  • From: Howard Hinnant
• Re: Sizes of integers
  • From: Malcolm
• Re: How to increase stack space/heap space
  • From: Malcolm
• Re: strtok causes Segmentation fault
  • From: void * clvrmnky()
• Re: sizeof([ALLOCATED MEMORY])
  • From: Ion Gaztañaga
• Re: strtok causes Segmentation fault
  • From: Nelu
• Re: sizeof([ALLOCATED MEMORY])
  • From: Ion Gaztañaga
• Re: Inserting Assembally into C source
  • From: Keith Thompson
• Re: strtok causes Segmentation fault
  • From: bofh1234
• Re: Bitwise AND etc
  • From: Keith Thompson
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: strtok causes Segmentation fault
  • From: bofh1234
• Re: 64 bit Endianness issue
  • From: Charles Mills
• Re: strtok causes Segmentation fault
  • From: Joe Smith
• Re: libclc - from Boost thread
  • From: William Ahern
• Re: strtok causes Segmentation fault
  • From: void * clvrmnky()
• Re: storing delimited string in an array
  • From: void * clvrmnky()
• Re: Parsing a simple string
  • From: mathieu
• storing delimited string in an array
  • From: gh
• Re: Array and Pointer Tutorial
  • From: Charles Richmond
• Re: 64 bit Endianness issue
  • From: Walter Roberson
• strtok causes Segmentation fault
  • From: bofh1234
• Re: swapping bytes in an integer
  • From: Jordan Abel
• 64 bit Endianness issue
  • From: sureshjayaram
• Re: Parsing a simple string
  • From: Flash Gordon
• Re: returning address of stack variable
  • From: Walter Roberson
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: libclc - from Boost thread
  • From: boa
• Re: Array and Pointer Tutorial
  • From: Flash Gordon
• Re: a struct parser
  • From: Rod Pemberton
• Re: const int in header: linker error
  • From: Ulrich Eckhardt
• Re: For loops help
  • From: Richard Heathfield
• Re: Const variables
  • From: CBFalconer
• Re: Parsing a simple string
  • From: mathieu
• Re: Listing the most dangerous parts of C
  • From: Rod Pemberton
• Re: Listing the most dangerous parts of C
  • From: Chris Hills
• Re: Array and Pointer Tutorial
  • From: CBFalconer
• Re: simplifying c code with function pointers
  • From: goldfita
• const int in header: linker error
  • From: Felix Kater
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: Bitwise AND etc
  • From: Rod Pemberton
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: Boost process and C
  • From: John F
• Re: swapping bytes in an integer
  • From: David Resnick
• Re: Listing the most dangerous parts of C
  • From: Rod Pemberton
• Re: Listing the most dangerous parts of C
  • From: Rod Pemberton
• Re: getchar() problem
  • From: CBFalconer
• Re: Array and Pointer Tutorial
  • From: Chad
• Re: Boost process and C
  • From: Richard Heathfield
• Re: Listing the most dangerous parts of C
  • From: CBFalconer
• Re: a struct parser
  • From: Ben Pfaff
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: Inserting Assembally into C source
  • From: Tim Prince
• Re: Listing the most dangerous parts of C
  • From: Flash Gordon
• Re: returning address of stack variable
  • From: Suman
• Re: Boost process and C
  • From: Robert Latest
• Re: Inserting Assembally into C source
  • From: Flash Gordon
• Re: Boost process and C
  • From: Robert Latest
• Re: The void** pointer breaking symmetry?
  • From: CBFalconer
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: Inserting Assembally into C source
  • From: Jordan Abel
• Re: Boost process and C
  • From: Robert Latest
• Re: Inserting Assembally into C source
  • From: noridotjabi@xxxxxxxxx
• Re: Inserting Assembally into C source
  • From: noridotjabi@xxxxxxxxx
• Re: Listing the most dangerous parts of C
  • From: Richard Bos
• Re: returning address of stack variable
  • From: pete
• Re: accessing static variables from outside their function
  • From: Steve Blinkhorn
• Re: For loops help
  • From: pete
• Re: Const variables
  • From: Richard Bos
• Re: Const variables
  • From: Vladimir Oka
• Re: Boost process and C
  • From: Ian Collins
• Const variables
  • From: Christian Christmann
• Re: Listing the most dangerous parts of C
  • From: Christopher Benson-Manica
• Re: avoid structure padding
  • From: Flash Gordon
• Re: For loops help
  • From: Christopher Benson-Manica
• Re: For loops help
  • From: Richard Bos
• Re: returning address of stack variable
  • From: Flash Gordon
• Re: returning address of stack variable
  • From: Richard Bos
• Re: For loops help
  • From: Vladimir Oka
• Re: A little quiz on macros
  • From: Richard Bos
• Re: A little quiz on macros
  • From: Jordan Abel
• Re: A little quiz on macros
  • From: Kiuhnm
• Re: returning address of stack variable
  • From: Suman
• Re: Boost process and C
  • From: Robert Latest
• For loops help
  • From: paolo . arimado
• Re: returning address of stack variable
  • From: pete
• Re: Boost process and C
  • From: Richard Tobin
• Re: Inserting Assembally into C source
  • From: Flash Gordon
• Re: Listing the most dangerous parts of C
  • From: Jordan Abel
• Re: Boost process and C
  • From: websnarf
• Re: Boost process and C
  • From: websnarf
• Re: returning address of stack variable
  • From: Manish Tomar
• Re: Boost process and C
  • From: Ian Collins
• avoid structure padding
  • From: pmm
• Re: Boost process and C
  • From: John F
• Re: simplifying c code with function pointers
  • From: pemo
• Re: Boost process and C
  • From: Robert Latest
• Re: simplifying c code with function pointers
  • From: Richard Heathfield
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: sizeof([ALLOCATED MEMORY])
  • From: Robert Latest
• Re: The void** pointer breaking symmetry?
  • From: Richard Bos
• Re: Boost process and C
  • From: Ian Collins
• Re: Boost process and C
  • From: Robert Latest
• Re: Boost process and C
  • From: Robert Latest
• Re: Boost process and C
  • From: Robert Latest
• Re: Listing the most dangerous parts of C
  • From: Flash Gordon
• Re: Boost process and C
  • From: Robert Latest
• Re: Inserting Assembally into C source
  • From: Dheroyan2006
• Re: a struct parser
  • From: Haude Daniel
• Re: simplifying c code with function pointers
  • From: pemo
• Re: simplifying c code with function pointers
  • From: Richard Heathfield
• Re: a struct parser
  • From: Haude Daniel
• Re: Boost process and C
  • From: Richard Heathfield
• Re: simplifying c code with function pointers
  • From: pemo
• Re: accessing static variables from outside their function
  • From: Robert Latest
• Re: The void** pointer breaking symmetry?
  • From: Flash Gordon
• Re: Boost process and C
  • From: Robert Latest
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: getchar() problem
  • From: Flash Gordon
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: Listing the most dangerous parts of C
  • From: Richard Heathfield
• Re: Listing the most dangerous parts of C
  • From: Robert Latest
• Re: a struct parser
  • From: Flash Gordon
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: Sizes of integers
  • From: Flash Gordon
• Re: Parsing a simple string
  • From: Richard Bos
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: mirror image of tree
  • From: Richard Bos
• Re: Array and Pointer Tutorial
  • From: Richard Bos
• Re: dynamic mem alloc q
  • From: Richard Heathfield
• Re: libclc - from Boost thread
  • From: boa
• Re: Listing the most dangerous parts of C
  • From: Richard Bos
• Re: Sizes of integers
  • From: Chris McDonald
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: libclc - from Boost thread
  • From: boa
• Re: Sizes of integers
  • From: Marc Thrun
• Re: dynamic mem alloc q
  • From: Richard Bos
• Re: Sizes of integers
  • From: Richard Heathfield
• Re: mirror image of tree
  • From: Ian Collins
• simplifying c code with function pointers
  • From: goldfita
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: Sizes of integers
  • From: Chris McDonald
• Re: Listing the most dangerous parts of C
  • From: Richard Heathfield
• Re: returning address of stack variable
  • From: Richard Heathfield
• Re: Sizes of integers
  • From: Richard Heathfield
• mirror image of tree
  • From: vim
• Re: dynamic mem alloc q
  • From: Michael Mair
• Re: accessing static variables from outside their function
  • From: Richard Heathfield
• Re: getchar() problem
  • From: Eric
• Re: returning address of stack variable
  • From: Ian Collins
• returning address of stack variable
  • From: Manish Tomar
• Re: Listing the most dangerous parts of C
  • From: qed
• Re: How to increase stack space/heap space
  • From: Artie Gold
• How to increase stack space/heap space
  • From: Ajay
• Re: Help on callback function
  • From: Ian Collins
• getchar() problem
  • From: Alan
• Re: How do I print this?
  • From: Dave Thompson
• Re: const struct members
  • From: Dave Thompson
• Re: discussing C evolution
  • From: Dave Thompson
• Re: First program in C - what is going on with function returns?
  • From: Dave Thompson
• Re: enumeration variables
  • From: Dave Thompson
• Re: Structure
  • From: Dave Thompson
• Re: eratosthenos
  • From: Dave Thompson
• Re: Listing the most dangerous parts of C
  • From: Jordan Abel
• Re: Listing the most dangerous parts of C
  • From: Jordan Abel
• Help on callback function
  • From: Ajay
• Re: Listing the most dangerous parts of C
  • From: qed
• Re: Listing the most dangerous parts of C
  • From: Ben Hinkle
• Re: A little quiz on macros
  • From: Christopher Benson-Manica
• Re: Listing the most dangerous parts of C
  • From: Christopher Benson-Manica
• Re: Listing the most dangerous parts of C
  • From: Christopher Benson-Manica
• Re: Listing the most dangerous parts of C
  • From: CBFalconer
• Re: The void** pointer breaking symmetry?
  • From: Keith Thompson
• Re: Listing the most dangerous parts of C
  • From: qed
• Re: a struct parser
  • From: qed
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: Listing the most dangerous parts of C
  • From: CBFalconer
• Re: Listing the most dangerous parts of C
  • From: CBFalconer
• Re: Listing the most dangerous parts of C
  • From: Dave Vandervies
• Re: a struct parser
  • From: Keith Thompson
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: Inserting Assembally into C source
  • From: Keith Thompson
• Re: segementation fault
  • From: Keith Thompson
• Re: Listing the most dangerous parts of C
  • From: Skarmander
• Re: Listing the most dangerous parts of C
  • From: Ben Pfaff
• Re: Listing the most dangerous parts of C
  • From: Skarmander
• Re: Listing the most dangerous parts of C
  • From: qed
• Re: segementation fault
  • From: Jordan Abel
• Re: E-Mail parse library?
  • From: CBFalconer
• Re: accessing static variables from outside their function
  • From: CBFalconer
• Re: libclc - from Boost thread
  • From: Skarmander
• Re: a struct parser
  • From: Ben Pfaff
• Re: dynamic mem alloc q
  • From: CBFalconer
• Re: a struct parser
  • From: CBFalconer
• Re: E-Mail parse library?
  • From: Chris McDonald
• Re: Sizes of integers
  • From: Walter Roberson
• Re: Listing the most dangerous parts of C
  • From: Andrew Poelstra
• Re: Inserting Assembally into C source
  • From: David Wade
• Re: The void** pointer breaking symmetry?
  • From: CBFalconer
• Re: OT - Name Mangling software
  • From: David Wade
• Re: segementation fault
  • From: Ian Collins
• Re: Sizes of integers
  • From: Ian Collins
• Re: E-Mail parse library?
  • From: Andrew Poelstra
• Re: segementation fault
  • From: didier2309
• Re: Sizes of integers
  • From: Chris McDonald
• Re: segementation fault
  • From: didier2309
• Sizes of integers
  • From: Michael Brennan
• Re: A little quiz on macros
  • From: Kiuhnm
• Re: A little quiz on macros
  • From: Kiuhnm
• Re: Inserting Assembally into C source
  • From: Al Balmer
• Re: Inserting Assembally into C source
  • From: Default User
• Re: libclc - from Boost thread
  • From: Ian Collins
• Inserting Assembally into C source
  • From: noridotjabi@xxxxxxxxx
• Re: libclc - from Boost thread
  • From: pete
• E-Mail parse library?
  • From: cgiatras
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: libclc - from Boost thread
  • From: boa
• Re: segementation fault
  • From: Keith Thompson
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: Concept of Statements and Expressions
  • From: pete
• Re: segementation fault
  • From: Jordan Abel
• Re: Listing the most dangerous parts of C
  • From: pete
• Re: Listing the most dangerous parts of C
  • From: jacob navia
• Re: libclc - from Boost thread
  • From: Jordan Abel
• Re: Concept of Statements and Expressions
  • From: Jordan Abel
• Re: Concept of Statements and Expressions
  • From: Jordan Abel
• Re: Parsing a simple string
  • From: pete
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: A little quiz on macros
  • From: Jordan Abel
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: Concept of Statements and Expressions
  • From: pete
• Re: Parsing a simple string
  • From: Keith Thompson
• Re: segementation fault
  • From: Keith Thompson
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: dynamic mem alloc q
  • From: Michael Mair
• Re: Concept of Statements and Expressions
  • From: Keith Thompson
• Re: Ansi standard with #defines and \ character
  • From: Keith Thompson
• Re: Concept of Statements and Expressions
  • From: pete
• Re: A little quiz on macros
  • From: Al Balmer
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: definition of u_int32
  • From: Flash Gordon
• Re: Listing the most dangerous parts of C
  • From: Kenneth Brody
• Re: swapping bytes in an integer
  • From: Ian Collins
• Re: Source Code to Plauger's "Standard C Library"
  • From: The Grue - James T. Sprinkle
• Re: accessing static variables from outside their function
  • From: Michael Mair
• Re: Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: Listing the most dangerous parts of C
  • From: Keith Thompson
• Re: Parsing a simple string
  • From: mathieu
• Re: Concept of Statements and Expressions
  • From: Robert Gamble
• Re: Concept of Statements and Expressions
  • From: Keith Thompson
• Re: Concept of Statements and Expressions
  • From: void * clvrmnky()
• Re: accessing static variables from outside their function
  • From: pete
• Re: a struct parser
  • From: Martin Ambuhl
• Re: The void** pointer breaking symmetry?
  • From: Keith Thompson
• Re: Source Code to Plauger's "Standard C Library"
  • From: P.J. Plauger
• Re: The void** pointer breaking symmetry?
  • From: Keith Thompson
• Re: The void** pointer breaking symmetry?
  • From: Keith Thompson
• Re: libclc - from Boost thread
  • From: pete
• Re: A little quiz on macros
  • From: Kiuhnm
• Re: Ansi standard with #defines and \ character
  • From: Brand Bogard
• Re: definition of u_int32
  • From: pete
• Re: Concept of Statements and Expressions
  • From: Ben C
• Re: Concept of Statements and Expressions
  • From: pete
• Re: libclc - from Boost thread
  • From: William Ahern
• Re: accessing static variables from outside their function
  • From: Walter Roberson
• Re: Source Code to Plauger's "Standard C Library"
  • From: A. Sinan Unur
• Re: Concept of Statements and Expressions
  • From: Robert Gamble
• Re: Concept of Statements and Expressions
  • From: pete
• Re: Source Code to Plauger's "Standard C Library"
  • From: Lew Pitcher
• Re: Converting int of unknown length to a string
  • From: William Ahern
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: Concept of Statements and Expressions
  • From: Rod Pemberton
• Re: Concept of Statements and Expressions
  • From: pete
• Re: Concept of Statements and Expressions
  • From: void * clvrmnky()
• Re: a struct parser
  • From: Walter Roberson
• Re: accessing static variables from outside their function
  • From: dick
• Source Code to Plauger's "Standard C Library"
  • From: The Grue - James T. Sprinkle
• Re: a struct parser
  • From: Flash Gordon
• Re: accessing static variables from outside their function
  • From: Steve Blinkhorn
• Re: accessing static variables from outside their function
  • From: Walter Roberson
• Re: accessing static variables from outside their function
  • From: Roberto Waltman
• Re: A little quiz on macros
  • From: Jordan Abel
• Re: Listing the most dangerous parts of C
  • From: jacob navia
• Re: libclc - from Boost thread
  • From: Rod Pemberton
• Re: The void** pointer breaking symmetry?
  • From: Jordan Abel
• Re: Listing the most dangerous parts of C
  • From: Rod Pemberton
• Re: a struct parser
  • From: jacob navia
• Re: accessing static variables from outside their function
  • From: Richard Heathfield
• accessing static variables from outside their function
  • From: Steve Blinkhorn
• Re: Boost process and C
  • From: Richard Heathfield
• Re: a struct parser
  • From: Weiguang Shi
• Re: a struct parser
  • From: Weiguang Shi
• Re: sizeof vs. sizeof() - Was: pls answer
  • From: Richard Heathfield
• Re: Boost process and C
  • From: Rod Pemberton
• Re: Concept of Statements and Expressions
  • From: Ben C
• sizeof vs. sizeof() - Was: pls answer
  • From: Roberto Waltman
• Re: a struct parser
  • From: Weiguang Shi
• Re: Listing the most dangerous parts of C
  • From: Richard Heathfield
• Re: Steady State ?
  • From: Walter Roberson
• Re: Boost process and C
  • From: Juuso Hukkanen
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: Listing the most dangerous parts of C
  • From: P.J. Plauger
• Re: Strange va_list problem
  • From: Flash Gordon
• Re: A little quiz on macros
  • From: Kiuhnm
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: Listing the most dangerous parts of C
  • From: Arthur J. O'Dwyer
• Re: definition of u_int32
  • From: Flash Gordon
• Re: Parsing a simple string
  • From: void * clvrmnky()
• Re: libclc - from Boost thread
  • From: jacob navia
• Re: Listing the most dangerous parts of C
  • From: jacob navia
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: Need help understanding program control/flow.
  • From: void * clvrmnky()
• Re: Concept of Statements and Expressions
  • From: Keith Thompson
• Re: segementation fault
  • From: void * clvrmnky()
• Re: Strange va_list problem
  • From: Flash Gordon
• Listing the most dangerous parts of C
  • From: Juuso Hukkanen
• Re: Parsing a simple string
  • From: mathieu
• Re: Concept of Statements and Expressions
  • From: pete
• Re: Strange va_list problem
  • From: Robert Gamble
• Re: libclc - from Boost thread
  • From: Richard Heathfield
• Re: Concept of Statements and Expressions
  • From: Vladimir Oka
• libclc - from Boost thread
  • From: Marco
• Re: definition of u_int32
  • From: Vladimir Oka
• Re: Strange va_list problem
  • From: Dik T. Winter
• Concept of Statements and Expressions
  • From: Neroku
• Re: Strange va_list problem
  • From: Richard Bos
• definition of u_int32
  • From: raghu
• Re: Strange va_list problem
  • From: Richard Bos
• Steady State ?
  • From: Amogh
• Re: Strange va_list problem
  • From: carol8421
• Re: A little quiz on macros
  • From: Richard Bos
• A little quiz on macros
  • From: Kiuhnm
• Re: The void** pointer breaking symmetry?
  • From: Richard Bos
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: Boost process and C
  • From: Robert Latest
• Re: a struct parser
  • From: Richard Tobin
• Re: The void** pointer breaking symmetry?
  • From: Robert Latest
• Re: a struct parser
  • From: Haude Daniel
• Re: Boost process and C
  • From: Robert Latest
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: swapping bytes in an integer
  • From: Robert Latest
• Strange va_list problem
  • From: Flash Gordon
• Re: Converting int of unknown length to a string
  • From: Robert Latest
• Re: biggest of 3 numbers
  • From: vim
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: Need help understanding program control/flow.
  • From: pete
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: OT - Name Mangling software
  • From: CBFalconer
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: Need help understanding program control/flow.
  • From: Vladimir Oka
• Re: Need help understanding program control/flow.
  • From: Buck Rogers
• Re: Need help understanding program control/flow.
  • From: Richard Heathfield
• Re: Need help understanding program control/flow.
  • From: Vladimir Oka
• Re: Need help understanding program control/flow.
  • From: Richard Heathfield
• Need help understanding program control/flow.
  • From: Buck Rogers
• Re: OT - Name Mangling software
  • From: David Wade
• Re: Bitwise AND etc
  • From: Rudolf
• Re: Bitwise AND etc
  • From: Keith Thompson
• Re: segementation fault
  • From: Keith Thompson
• Re: meaning of outport(LPT1,00)
  • From: Neil
• Re: meaning of outport(LPT1,00)
  • From: Martin Ambuhl
• Re: meaning of outport(LPT1,00)
  • From: Richard Bos
• Re: Bitwise AND etc
  • From: Martin Ambuhl
• Re: about UDP packet capture error
  • From: pmm
• meaning of outport(LPT1,00)
  • From: nimmiejoey@xxxxxxxxx
• Re: dynamic mem alloc q
  • From: Michael Mair
• Re: segementation fault
  • From: Jack Klein
• Re: Ansi standard with #defines and \ character
  • From: Thad Smith
• Re: a struct parser
  • From: websnarf
• Re: Problem: Thread in C
  • From: Ian Collins
• Problem: Thread in C
  • From: ranjeet . gupta
• Re: Converting int of unknown length to a string
  • From: Ben Pfaff
• Re: Converting int of unknown length to a string
  • From: William Ahern
• Re: Bitwise AND etc
  • From: mdh
• Re: Bitwise AND etc
  • From: mdh
• Re: Bitwise AND etc
  • From: Ian Collins
• Re: Converting int of unknown length to a string
  • From: Ben Pfaff
• Bitwise AND etc
  • From: mdh
• Re: Converting int of unknown length to a string
  • From: Robert Gamble
• Re: Converting int of unknown length to a string
  • From: Robert Gamble
• Re: what is wrong with the 'strcpy'
  • From: jim
• Re: OT - Name Mangling software
  • From: CBFalconer
• Re: Converting int of unknown length to a string
  • From: TomServo
• Re: Converting int of unknown length to a string
  • From: jefong
• Re: Converting int of unknown length to a string
  • From: Robert Gamble
• Re: Converting int of unknown length to a string
  • From: Ian Collins
• Converting int of unknown length to a string
  • From: TomServo
• Re: dynamic mem alloc q
  • From: Robert Gamble
• Re: printf headache
  • From: Joe Smith
• Re: lgamma function: ANSI C or not?
  • From: Ian Collins
• Re: dynamic mem alloc q
  • From: Joe Smith
• Re: iostream error.
  • From: Keith Thompson
• Re: lgamma function: ANSI C or not?
  • From: P.J. Plauger
• Re: lgamma function: ANSI C or not?
  • From: P.J. Plauger
• Re: problem with advisory file locks
  • From: Joe Wright
• Re: Parsing a simple string
  • From: attn.steven.kuo@xxxxxxxxx
• Re: Substitute for floatint point
  • From: Joe Wright
• Re: Looking for a C++ compiler
  • From: John F
• Re: Ansi standard with #defines and \ character
  • From: Mike Wahler
• Re: The void** pointer breaking symmetry?
  • From: Old Wolf
• Re: Globally unique enums or macro values?
  • From: userblue
• Re: a struct parser
  • From: Richard Tobin
• Ansi standard with #defines and \ character
  • From: Brand Bogard
• Re: Looking for a C++ compiler
  • From: Chris Hills
• Re: a struct parser
  • From: Eric Sosman
• Re: segementation fault
  • From: Keith Thompson
• Re: a struct parser
  • From: jacob navia
• Re: OT - Name Mangling software
  • From: Eric Sosman
• Re: pls answer
  • From: Jordan Abel
• Re: a struct parser
  • From: Robert Gamble
• Re: segementation fault
  • From: Robert Gamble
• Re: Parsing a simple string
  • From: Eric Sosman
• Re: pls answer
  • From: Ian Collins
• Re: GCC Preprocessor
  • From: Keith Thompson
• Re: pls answer
  • From: Keith Thompson
• Re: a struct parser
  • From: Ian Collins
• Re: lgamma function: ANSI C or not?
  • From: Ian Collins
• Re: a struct parser
  • From: void * clvrmnky()
• Re: GCC Preprocessor
  • From: Taylor K.
• Re: segementation fault
  • From: Flash Gordon
• Re: OT - Name Mangling software
  • From: Kenneth Brody
• Re: segementation fault
  • From: Keith Thompson
• Re: segementation fault
  • From: Martin Ambuhl
• Re: pls answer
  • From: Ian Collins
• Re: Parsing a simple string
  • From: mathieu
• Re: preprocessor: checking for clashing #define
  • From: iler . ml
• Re: segementation fault
  • From: Ahmed
• Re: lgamma function: ANSI C or not?
  • From: Stephen Sprunk
• Re: discussing C evolution
  • From: Ian Collins
• Re: segementation fault
  • From: cbmanica
• Re: dynamic mem alloc q
  • From: Michael Mair
• Re: a struct parser
  • From: Weiguang Shi
• Re: Looking for a C++ compiler
  • From: John F
• Re: Parsing a simple string
  • From: mathieu
• Re: preprocessor: checking for clashing #define
  • From: Eric Sosman
• OT - Name Mangling software
  • From: David Wade
• Re: pls answer
  • From: CBFalconer
• Re: segementation fault
  • From: Robert Gamble
• Re: Parsing a simple string
  • From: Robert Gamble
• Re: pls answer
  • From: Flash Gordon
• Re: pls answer
  • From: pete
• Re: Looking for a C++ compiler
  • From: David Wade
• Parsing a simple string
  • From: mathieu
• Re: segementation fault
  • From: didier2309
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: Determine if a character string is palindromic
  • From: Keith Thompson
• Re: preprocessor: checking for clashing #define
  • From: Joe Smith
• Re: pls answer
  • From: Roberto Waltman
• dynamic mem alloc q
  • From: Joe Smith
• Re: a struct parser
  • From: Bill Pursell
• preprocessor: checking for clashing #define
  • From: iler . ml
• Re: segementation fault
  • From: Kenneth Brody
• Re: pls answer
  • From: Kenneth Brody
• Re: segementation fault
  • From: cbmanica
• Re: segementation fault
  • From: Flash Gordon
• a struct parser
  • From: Weiguang Shi
• Re: pls answer
  • From: Jordan Abel
• Re: Determine if a character string is palindromic
  • From: Chris F.A. Johnson
• Re: pls answer
  • From: pemo
• segementation fault
  • From: didier2309
• Re: Finding errors in this code...
  • From: Martin Ambuhl
• Re: pls answer
  • From: Martin Ambuhl
• Re: Determine if a character string is palindromic
  • From: Simon Biber
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: swapping bytes in an integer
  • From: john
• Re: lgamma function: ANSI C or not?
  • From: Flash Gordon
• Re: lgamma function: ANSI C or not?
  • From: P.J. Plauger
• Re: about UDP packet capture error
  • From: Nick Keighley
• Re: call function with function pointer array as argument
  • From: Bill Pursell
• Re: Boost process and C
  • From: Juuso Hukkanen
• call function with function pointer array as argument
  • From: Felix Kater
• Re: lgamma function: ANSI C or not?
  • From: Flash Gordon
• Re: printf headache
  • From: Michael Wojcik
• Re: what is wrong with the 'strcpy'
  • From: Andrew Poelstra
• Re: Finding errors in this code...
  • From: Andrew Poelstra
• Re: lgamma function: ANSI C or not?
  • From: Ico
• Re: swapping bytes in an integer
  • From: Eric Sosman
• Re: lgamma function: ANSI C or not?
  • From: Flash Gordon
• Re: lgamma function: ANSI C or not?
  • From: Tim Prince
• Re: Finding errors in this code...
  • From: Robert Latest
• Re: lgamma function: ANSI C or not?
  • From: Flash Gordon
• Re: lgamma function: ANSI C or not?
  • From: Bart Vandewoestyne
• Re: Determine if a character string is palindromic
  • From: Richard Heathfield
• Re: biggest of 3 numbers
  • From: Peter "Shaggy" Haywood
• Re: Finding errors in this code...
  • From: Richard Heathfield
• Re: discussing C evolution
  • From: Richard Bos
• Re: Efficiency and the proposed changes
  • From: Richard Bos
• Re: Determine if a character string is palindromic
  • From: Simon Biber
• Re: raeding disk block in linux
  • From: Ico
• Re: Globally unique enums or macro values?
  • From: userblue
• Re: lgamma function: ANSI C or not?
  • From: P.J. Plauger
• Re: lgamma function: ANSI C or not?
  • From: Vladimir Oka
• lgamma function: ANSI C or not?
  • From: Bart Vandewoestyne
• Re: pls answer
  • From: Flash Gordon
• Re: pls answer
  • From: Vladimir Oka
• Re: raeding disk block in linux
  • From: Vladimir Oka
• Re: pls answer
  • From: "Nils O. Selåsdal"
• Re: about UDP packet capture error
  • From: Flash Gordon
• raeding disk block in linux
  • From: kg
• Re: pls answer
  • From: Ian Malone
• Re: Implementing this constructor...
  • From: sophie
• Re: Implementing this constructor...
  • From: Ian Collins
• Implementing this constructor...
  • From: sophie
• Re: Finding errors in this code...
  • From: Ian Collins
• Re: Finding errors in this code...
  • From: Vladimir Oka
• Finding errors in this code...
  • From: sophie
• Re: about UDP packet capture error
  • From: pmm
• Re: pls answer
  • From: pemo
• pls answer
  • From: rammy
• Re: about UDP packet capture error
  • From: Nick Keighley
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: what is wrong with the 'strcpy'
  • From: Richard Heathfield
• about UDP packet capture error
  • From: pmm
• Re: The void** pointer breaking symmetry?
  • From: Old Wolf
• Re: what is wrong with the 'strcpy'
  • From: jim
• Re: what is wrong with the 'strcpy'
  • From: jim
• Re: Rock Program
  • From: pemo
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: GCC Preprocessor
  • From: Chris McDonald
• Re: (const char *cp) and (char *p) are consistent type, (const char **cpp) and (char **pp) are not consistent
  • From: Ian Collins
• Re: The void** pointer breaking symmetry?
  • From: lovecreatesbeauty
• (const char *cp) and (char *p) are consistent type, (const char **cpp) and (char **pp) are not consistent
  • From: lovecreatesbeauty
• Re: GCC Preprocessor
  • From: S.Tobias
• Re: GCC Preprocessor
  • From: Richard Heathfield
• Re: GCC Preprocessor
  • From: Chris McDonald
• Re: Boost process and C
  • From: Richard Heathfield
• Re: GCC Preprocessor
  • From: Richard Heathfield
• Re: Utility Warrior announces Image to PDF Dynamic Link Library (DLL)
  • From: Jack Klein
• Re: Determine if a character string is palindromic
  • From: Richard Heathfield
• Re: The void** pointer breaking symmetry?
  • From: Richard Heathfield
• Re: Utility Warrior announces Image to PDF Dynamic Link Library (DLL)
  • From: Richard Heathfield
• Re: casting question
  • From: Giorgos Keramidas
• Re: Determine if a character string is palindromic
  • From: Simon Biber
• Re: How to sscanf return integer only
  • From: Joe Smith
• Re: Globally unique enums or macro values?
  • From: Thad Smith
• Re: swapping bytes in an integer
  • From: Rod Pemberton
• Re: swapping bytes in an integer
  • From: john
• Re: Globally unique enums or macro values?
  • From: Rod Pemberton
• Re: GCC Preprocessor
  • From: SM Ryan
• Re: Changing file permission in windows
  • From: SM Ryan
• Re: swapping bytes in an integer
  • From: EventHelix.com
• Re: Determine if a character string is palindromic
  • From: qed
• Re: Globally unique enums or macro values?
  • From: Ian Collins
• GCC Preprocessor
  • From: s7master
• Re: iostream error.
  • From: Rod Pemberton
• Re: Globally unique enums or macro values?
  • From: userblue
• Re: Efficiency and the proposed changes
  • From: Rod Pemberton
• Re: Globally unique enums or macro values?
  • From: Keith Thompson
• Re: Globally unique enums or macro values?
  • From: userblue
• Re: Globally unique enums or macro values?
  • From: Ian Collins
• Globally unique enums or macro values?
  • From: userblue
• Re: Determine if a character string is palindromic
  • From: CBFalconer
• Re: How to sscanf return integer only
  • From: Robert Gamble
• Re: Rock Program
  • From: Keith Thompson
• Re: Determine if a character string is palindromic
  • From: Flash Gordon
• Re: casting question
  • From: Old Wolf
• Re: urgent
  • From: Charles Richmond
• Re: what is wrong with the 'strcpy'
  • From: Charles Richmond
• Re: Rock Program
  • From: Old Wolf
• Re: Rock Program
  • From: Old Wolf
• Re: The void** pointer breaking symmetry?
  • From: Old Wolf
• Re: Determine if a character string is palindromic
  • From: Chris F.A. Johnson
• Re: Determine if a character string is palindromic
  • From: CBFalconer
• Re: Looking for a C++ compiler
  • From: John F
• Re: swapping bytes in an integer
  • From: W Marsh
• Re: Looking for a C++ compiler
  • From: David Wade
• Re: swapping bytes in an integer
  • From: Andrew Poelstra
• Re: swapping bytes in an integer
  • From: W Marsh
• Re: swapping bytes in an integer
  • From: john
• Re: Determine if a character string is palindromic
  • From: Keith Thompson
• Re: How to sscanf return integer only
  • From: Joe Smith
• Re: swapping bytes in an integer
  • From: Ian Collins
• Re: swapping bytes in an integer
  • From: W Marsh
• Re: Determine if a character string is palindromic
  • From: Chris F.A. Johnson
• Re: Determine if a character string is palindromic
  • From: Richard Tobin
• Re: swapping bytes in an integer
  • From: Harald van Dijk
• Re: swapping bytes in an integer
  • From: Keith Thompson
• Re: problem with advisory file locks
  • From: Keith Thompson
• Re: Efficiency and the proposed changes
  • From: REH
• problem with advisory file locks
  • From: fabio
• Re: swapping bytes in an integer
  • From: W Marsh
• Re: iostream error.
  • From: Mark McIntyre
• Re: The void** pointer breaking symmetry?
  • From: Ben C
• Re: swapping bytes in an integer
  • From: Ian Collins
• Re: swapping bytes in an integer
  • From: Flash Gordon
• Re: swapping bytes in an integer
  • From: W Marsh
• swapping bytes in an integer
  • From: john
• Re: code for implementing buddy allocator
  • From: Rod Pemberton
• Utility Warrior announces Image to PDF Dynamic Link Library (DLL)
  • From: UtilityWarrior
• Re: Determine if a character string is palindromic
  • From: Ben C
• Re: Determine if a character string is palindromic
  • From: Keith Thompson
• Re: Determine if a character string is palindromic
  • From: Vladimir Oka
• Re: The void** pointer breaking symmetry?
  • From: Keith Thompson
• Re: Efficiency and the proposed changes
  • From: Keith Thompson
• Re: Determine if a character string is palindromic
  • From: john
• Re: what is wrong with the 'strcpy'
  • From: Michael Mair
• Re: Determine if a character string is palindromic
  • From: Robert Gamble
• Re: The void** pointer breaking symmetry?
  • From: Michael Mair
• Re: Rock Program
  • From: Ed Prochak
• Re: Determine if a character string is palindromic
  • From: Robert Gamble
• Re: casting question
  • From: Rod Pemberton
• Re: Determine if a character string is palindromic
  • From: CBFalconer
• Re: The void** pointer breaking symmetry?
  • From: CBFalconer
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: Determine if a character string is palindromic
  • From: Vladimir Oka
• Re: Determine if a character string is palindromic
  • From: Richard Heathfield
• Determine if a character string is palindromic
  • From: lovecreatesbeauty
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: Substitute for floatint point
  • From: Vladimir Oka
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Martin Jørgensen
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Martin Jørgensen
• Re: Substitute for floatint point
  • From: /*24age*/
• Re: Is it because of diffrence between bcc32 and gcc?
  • From: Gimmmo
• Re: The void** pointer breaking symmetry?
  • From: Eric Sosman
• Meta-UB (was Re: getchar)
  • From: Kenneth Brody
• Re: The void** pointer breaking symmetry?
  • From: CBFalconer
• Re: biggest of 3 numbers
  • From: Flash Gordon
• Re: Rock Program
  • From: pemo
• Re: biggest of 3 numbers
  • From: Richard Bos
• casting question
  • From: Giorgos Keramidas
• Re: Rock Program
  • From: gc
• Re: Efficiency and the proposed changes
  • From: Rod Pemberton
• Re: biggest of 3 numbers
  • From: Dik T. Winter
• Re: Substitute for floatint point
  • From: Dik T. Winter
• Re: Substitute for floatint point
  • From: Keith Thompson
• Re: Substitute for floatint point
  • From: Keith Thompson
• Re: KeyB typeahead buffer in BIOS
  • From: Rod Pemberton
• Re: Substitute for floatint point
  • From: Vladimir Oka
• Re: what is wrong with the 'strcpy'
  • From: jim
• Re: biggest of 3 numbers
  • From: Flash Gordon
• Re: biggest of 3 numbers
  • From: Richard Bos
• Substitute for floatint point
  • From: Sathyaish
• Re: Changing file permission in windows
  • From: Rafael Almeida
• Re: Efficiency and the proposed changes
  • From: Richard Bos
• Re: The void** pointer breaking symmetry?
  • From: elmar
• Re: Rock Program
  • From: gc
• Re: Looking for a C++ compiler
  • From: Alan
• Re: Changing file permission in windows
  • From: santosh
• Re: Changing file permission in windows
  • From: Vladimir Oka
• Changing file permission in windows
  • From: santosh
• Re: KeyB typeahead buffer in BIOS
  • From: Vladimir Oka
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Vladimir Oka
• KeyB typeahead buffer in BIOS
  • From: Sree
• Re: discussing C evolution
  • From: Keith Thompson
• Re: help me learn C
  • From: Richard Heathfield
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Martin Jørgensen
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Old Wolf
• Re: biggest of 3 numbers
  • From: Dik T. Winter
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: Keith Thompson
• Re: declaration meaning
  • From: Keith Thompson
• Re: help me learn C
  • From: Keith Thompson
• Re: printf headache
  • From: Al Balmer
• Re: printf headache
  • From: Old Wolf
• Re: printf headache
  • From: Old Wolf
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: P.J. Plauger
• Re: sizeof([ALLOCATED MEMORY])
  • From: Howard Hinnant
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Vladimir Oka
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Vladimir Oka
• Re: urgent
  • From: Skarmander
• Re: main() called inside main()
  • From: Richard Heathfield
• Re: printf headache
  • From: Richard Heathfield
• Re: Boost process and C
  • From: John F
• Re: Boost process and C
  • From: John F
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Martin Jørgensen
• Re: discussing C evolution
  • From: Ian Collins
• Re: urgent
  • From: Robert Latest
• Re: unsigned variables
  • From: Michael Mair
• Re: help me learn C
  • From: Malcolm
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Robert Gamble
• Re: help me learn C
  • From: Malcolm
• Re: perhaps a stack problem? Long calculations - strange error?
  • From: Vladimir Oka
• Re: urgent
  • From: Martin Ambuhl
• Re: strtok behavior with multiple consecutive delimiters
  • From: Malcolm
• Re: How to sscanf return integer only
  • From: Robert Gamble
• Re: declaration meaning
  • From: michi
• Re: printf headache
  • From: Joe Smith
• Re: biggest of 3 numbers
  • From: Jordan Abel
• Re: unsigned variables
  • From: Walter Roberson
• Re: How to sscanf return integer only
  • From: Joe Smith
• Re: A Little help with Bits...
  • From: Walter Roberson
• unsigned variables
  • From: Christian Christmann
• Re: partial/selective Macro expansion scpp
  • From: michi
• Re: Looking for a C++ compiler
  • From: Burton Samograd
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: Chris Hills
• Re: partial/selective Macro expansion scpp
  • From: michi
• Re: help me learn C
  • From: Chris Hills
• Re: partial/selective Macro expansion scpp
  • From: Ben Pfaff
• perhaps a stack problem? Long calculations - strange error?
  • From: Martin Joergensen
• Re: help me learn C
  • From: Chris Hills
• Re: partial/selective Macro expansion scpp
  • From: Robert Gamble
• Re: Looking for a C++ compiler
  • From: Damir
• Re: help me learn C
  • From: Christopher Benson-Manica
• Re: Looking for a C++ compiler
  • From: Tim Prince
• Looking for a C++ compiler
  • From: flank
• Re: partial/selective Macro expansion scpp
  • From: michi
• Re: urgent
  • From: Christopher Benson-Manica
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: Chris Hills
• Re: urgent
  • From: Julian V. Noble
• Re: parallel port programming using C
  • From: Julian V. Noble
• Re: urgent
  • From: noridotjabi@xxxxxxxxx
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: Chris Hills
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: Michael Mair
• Re: urgent
  • From: Gohar
• Re: urgent
  • From: W Marsh
• urgent
  • From: Gohar
• Re: Is it because of diffrence between bcc32 and gcc?
  • From: jigsaw
• urgent
  • From: Gohar
• Re: Free Microsoft Visual C++ Toolkit 2003
  • From: P.J. Plauger
• Re: Is it because of diffrence between bcc32 and gcc?
  • From: Michael Mair
• Re: Is it because of diffrence between bcc32 and gcc?
  • From: Ian Coll