comp.lang.c

• Date Index

---

• How to make binary data portable?, PengYu.UT@xxxxxxxxx
  • Re: How to make binary data portable?, Martin Ambuhl
    • Re: How to make binary data portable?, Walter Roberson
      • Re: How to make binary data portable?, PengYu.UT@xxxxxxxxx
    • Re: How to make binary data portable?, PengYu.UT@xxxxxxxxx
      • Re: How to make binary data portable?, Randy Howard
  • Re: How to make binary data portable?, Charles Mills
    • Re: How to make binary data portable?, Sensei
• why use -> (not .) with pointers?, Felix Kater
  • Re: why use -> (not .) with pointers?, Suman
    • Re: why use -> (not .) with pointers?, jacob navia
    • Re: why use -> (not .) with pointers?, Richard Tobin
      • Re: why use -> (not .) with pointers?, Suman
      • Re: why use -> (not .) with pointers?, Suman
      • Re: why use -> (not .) with pointers?, Lawrence Kirby
  • Re: why use -> (not .) with pointers?, jacob navia
    • Re: why use -> (not .) with pointers?, Lawrence Kirby
    • Re: why use -> (not .) with pointers?, CBFalconer
      • Re: why use -> (not .) with pointers?, Alan Balmer
      • Re: why use -> (not .) with pointers?, Clint Olsen
  • Re: why use -> (not .) with pointers?, Chris Dollin
  • Re: why use -> (not .) with pointers?, lawrence . jones
    • Re: why use -> (not .) with pointers?, Guillaume
      • Re: why use -> (not .) with pointers?, Richard Tobin
      • Re: why use -> (not .) with pointers?, Guillaume
      • Re: why use -> (not .) with pointers?, Walter Roberson
      • Re: why use -> (not .) with pointers?, Eric Sosman
      • Re: why use -> (not .) with pointers?, Clark S . Cox III
      • Re: why use -> (not .) with pointers?, Alan Balmer
      • Re: why use -> (not .) with pointers?, Anonymous 7843
    • Re: why use -> (not .) with pointers?, Lew Pitcher
      • Re: why use -> (not .) with pointers?, Tydr Schnubbis
      • Re: why use -> (not .) with pointers?, Tydr Schnubbis
    • Re: why use -> (not .) with pointers?, Chris Torek
      • Re: why use -> (not .) with pointers?, P.J. Plauger
  • Re: why use -> (not .) with pointers?, Anonymous 7843
• #defines and strings, GMM50
  • Re: #defines and strings, Walter Roberson
  • Re: #defines and strings, Eric Sosman
    • Re: #defines and strings, GMM50
• reading a line through scanf, gyan
  • Re: reading a line through scanf, Suman
  • Re: reading a line through scanf, pete
    • Re: reading a line through scanf, Suman
      • Re: reading a line through scanf, pete
      • Re: reading a line through scanf, pete
  • Re: reading a line through scanf, Lawrence Kirby
  • Re: reading a line through scanf, CBFalconer
• Re: K&R3?, Chris Croughton
• Re: Object persistence in C, Bilgehan . Balban
• casting to unsigned char for is*() and to*() functions, mr_semantics
  • Re: casting to unsigned char for is*() and to*() functions, Lew Pitcher
    • Re: casting to unsigned char for is*() and to*() functions, Eric Sosman
  • Re: casting to unsigned char for is*() and to*() functions, Eric Sosman
    • Re: casting to unsigned char for is*() and to*() functions, Kenneth Brody
      • Re: casting to unsigned char for is*() and to*() functions, Eric Sosman
    • Re: casting to unsigned char for is*() and to*() functions, CBFalconer
    • Re: casting to unsigned char for is*() and to*() functions, James Daughtry
      • Re: casting to unsigned char for is*() and to*() functions, Eric Sosman
      • Re: casting to unsigned char for is*() and to*() functions, James Daughtry
      • Re: casting to unsigned char for is*() and to*() functions, Lawrence Kirby
  • Re: casting to unsigned char for is*() and to*() functions, pete
  • Re: casting to unsigned char for is*() and to*() functions, Jack Klein
• Reading Lines with Fgets and a bit of C++ {Novice Programmer}, AMT2K5
  • Re: Reading Lines with Fgets and a bit of C++ {Novice Programmer}, Eric Sosman
  • Re: Reading Lines with Fgets and a bit of C++ {Novice Programmer}, AMT2K5
  • Re: Reading Lines with Fgets and a bit of C++ {Novice Programmer}, Richard Bos
  • Re: Reading Lines with Fgets and a bit of C++ {Novice Programmer}, Default User
    • Re: Reading Lines with Fgets and a bit of C++ {Novice Programmer}, AMT2K5
• C directives, vib
  • Re: C directives, Richard Bos
  • Re: C directives, Jonathan Bartlett
    • Re: C directives, Christian Kandeler
• Floatin point issues, sandeep
  • Re: Floatin point issues, Richard Bos
    • Re: Floatin point issues, sandeep
      • Re: Floatin point issues, CBFalconer
  • Re: Floatin point issues, Suman
  • Re: Floatin point issues, Martin Ambuhl
    • Re: Floatin point issues, sandeep
      • Re: Floatin point issues, Neil Kurzman
      • Re: Floatin point issues, sandeep
      • Re: Floatin point issues, Default User
      • Re: Floatin point issues, sandeep
      • Re: Floatin point issues, Suman
      • Re: Floatin point issues, Lefty Bigfoot
      • Re: Floatin point issues, CBFalconer
• conditional statements, prasad
  • Re: conditional statements, Suman
  • Re: conditional statements, Ben Pfaff
• what's wrong with atof() and casting?, XZ
  • Re: what's wrong with atof() and casting?, Jack Klein
    • Re: what's wrong with atof() and casting?, Roman Mashak
      • Re: what's wrong with atof() and casting?, Jack Klein
      • Re: what's wrong with atof() and casting?, Roman Mashak
      • Re: what's wrong with atof() and casting?, Flash Gordon
      • Re: what's wrong with atof() and casting?, Roman Mashak
      • Re: what's wrong with atof() and casting?, Peter Nilsson
      • Re: what's wrong with atof() and casting?, XZ
      • Re: what's wrong with atof() and casting?, Adam Warner
      • Re: what's wrong with atof() and casting?, CBFalconer
      • Re: what's wrong with atof() and casting?, Peter Nilsson
  • Re: what's wrong with atof() and casting?, Rajan
    • Re: what's wrong with atof() and casting?, Clark S . Cox III
    • Re: what's wrong with atof() and casting?, Flash Gordon
• lint, Roman Mashak
  • Re: lint, Artie Gold
    • Re: lint, Roman Mashak
      • Re: lint, Jonathan Bartlett
      • Re: lint, Chris Croughton
• Aliasing/Torek's strtod() experience, Adam Warner
  • Re: Aliasing/Torek's strtod() experience, Grumble
    • Re: Aliasing/Torek's strtod() experience, Adam Warner
      • Re: Aliasing/Torek's strtod() experience, Michael Mair
      • Re: Aliasing/Torek's strtod() experience, Adam Warner
      • Re: Aliasing/Torek's strtod() experience, Walter Roberson
  • Re: Aliasing/Torek's strtod() experience, Lawrence Kirby
    • Re: Aliasing/Torek's strtod() experience, Adam Warner
• fast multiple file access, Cable
  • Re: fast multiple file access, Walter Roberson
    • Re: fast multiple file access, Chris Torek
    • Re: fast multiple file access, CBFalconer
      • Re: fast multiple file access, Michael Mair
      • Re: fast multiple file access, Lawrence Kirby
      • Re: fast multiple file access, CBFalconer
• openssl and DES, nrivera . eng
  • Re: openssl and DES, Jack Klein
  • Re: openssl and DES, CBFalconer
• bizarre malloc problem, Snis Pilbor
  • Re: bizarre malloc problem, Gordon Burditt
  • Re: bizarre malloc problem, Default User
  • Re: bizarre malloc problem, Flash Gordon
    • Re: bizarre malloc problem, Snis Pilbor
      • Re: bizarre malloc problem, Clark S . Cox III
      • Re: bizarre malloc problem, Lawrence Kirby
      • Re: bizarre malloc problem, CBFalconer
  • Re: bizarre malloc problem, CBFalconer
• Array subscripting overflow behaviour, Netocrat
  • Re: Array subscripting overflow behaviour, Walter Roberson
    • Re: Array subscripting overflow behaviour, Netocrat
    • Re: Array subscripting overflow behaviour, Lawrence Kirby
  • Re: Array subscripting overflow behaviour, pete
    • Re: Array subscripting overflow behaviour, Netocrat
  • Re: Array subscripting overflow behaviour, Eric Sosman
    • Re: Array subscripting overflow behaviour, Netocrat
• Libraries, function names and link, joseluismarchetti
  • Re: Libraries, function names and link, Walter Roberson
    • Re: Libraries, function names and link, joseluismarchetti
  • Re: Libraries, function names and link, joseluismarchetti
• gcc iso90 and long long, Olivier
  • Re: gcc iso90 and long long, Olivier
• Array name and address of the first element, ehames@xxxxxxxxx
  • Re: Array name and address of the first element, akarl
  • Re: Array name and address of the first element, Eric Sosman
    • Re: Array name and address of the first element, Michael Wojcik
  • Re: Array name and address of the first element, Default User
    • Re: Array name and address of the first element, ehames@xxxxxxxxx
      • Re: Array name and address of the first element, Clark S . Cox III
      • Re: Array name and address of the first element, Default User
      • Re: Array name and address of the first element, ehames@xxxxxxxxx
• graphics in Linux..., sudip
  • Re: graphics in Linux..., Penguin_X
    • Re: graphics in Linux..., akarl
    • Re: graphics in Linux..., CBFalconer
  • Re: graphics in Linux..., john_bode
  • Re: graphics in Linux..., Malcolm
    • Re: graphics in Linux..., sudip
• ANSI C Compilation linking problem, Ben
  • Re: ANSI C Compilation linking problem, Richard Bos
  • Re: ANSI C Compilation linking problem, john_bode
    • Re: ANSI C Compilation linking problem, Ben
• Is an empty translation unit valid?, Chris Croughton
  • Re: Is an empty translation unit valid?, Lawrence Kirby
    • Re: Is an empty translation unit valid?, Chris Croughton
      • Re: Is an empty translation unit valid?, Lawrence Kirby
• reading from a file, some times values in file may not be filled, srikanth
  • Re: reading from a file, some times values in file may not be filled, Mike Wahler
• memory delete problem, MJ
  • Re: memory delete problem, akarl
  • Re: memory delete problem, Lawrence Kirby
    • Re: memory delete problem, MJ
• test, Slim
  • Re: test, Christopher Benson-Manica
• sharing data from DLL, phil
  • Re: sharing data from DLL, Jack Klein
• bits comparison, vib
  • Re: bits comparison, vib
  • Re: bits comparison, pete
    • Re: bits comparison, vib
      • Re: bits comparison, pete
      • Re: bits comparison, vib
  • Re: bits comparison, Jason Curl
    • Re: bits comparison, pete
    • Re: bits comparison, vib
• Interface, sandeep
  • Re: Interface, Dave Vandervies
• parameters or stdin, David Warner
  • Re: parameters or stdin, ade ishs
  • Re: parameters or stdin, Richard Tobin
    • Re: parameters or stdin, Michael Wojcik
  • Re: parameters or stdin, #2pencil
• C and Tk, Penguin_X
  • Re: C and Tk, Jack Klein
    • Re: C and Tk, Chris McDonald
      • Re: C and Tk, Peter Nilsson
      • Re: C and Tk, Gordon Burditt
      • Re: C and Tk, Martin Ambuhl
      • Re: C and Tk, Keith Thompson
      • Re: C and Tk, Chris McDonald
      • Re: C and Tk, Michael Mair
      • Re: C and Tk, Peter Nilsson
      • Re: C and Tk, SM Ryan
      • Re: C and Tk, Jack Klein
      • Re: C and Tk, CBFalconer
      • Re: C and Tk, Lawrence Kirby
      • Re: C and Tk, Flash Gordon
      • Re: C and Tk, CBFalconer
      • Re: C and Tk, Alan Balmer
      • Re: C and Tk, Walter Roberson
      • Re: C and Tk, Keith Thompson
      • Re: C and Tk, Lawrence Kirby
    • Re: C and Tk, Keith Thompson
  • Re: C and Tk, Dave Marquardt
• why do I have "file size exceed" problem?, guru . slt
  • Re: why do I have "file size exceed" problem?, Sorav Bansal
    • Re: why do I have "file size exceed" problem?, bird
• fscanf problem, learner
  • Re: fscanf problem, Michael Mair
    • Re: fscanf problem, learner
      • Re: fscanf problem, Michael Mair
      • Re: fscanf problem, learner
      • Re: fscanf problem, Michael Mair
• Tool to trace function calls, Thomas Glanzmann
  • Re: Tool to trace function calls, Artie Gold
  • Re: Tool to trace function calls, Grumble
  • Re: Tool to trace function calls, Morris Dovey
• Differences between Functio & Macro in C, uma676
  • Re: Differences between Functio & Macro in C, Rouben Rostamian
    • Re: Differences between Functio & Macro in C, Kenny McCormack
      • Re: Differences between Functio & Macro in C, CBFalconer
      • Re: Differences between Functio & Macro in C, Lefty Bigfoot
      • Re: Differences between Functio & Macro in C, jdallen2000
  • <Possible follow-ups>
  • Re: Differences between Functio & Macro in C, Suman
    • Re: Differences between Functio & Macro in C, Flash Gordon
  • Re: Differences between Functio & Macro in C, Robert Maas, see http://tinyurl.com/uh3t
    • Re: Differences between Functio & Macro in C, CBFalconer
• About c++, sandeep
  • Re: About c++, Lew Pitcher
    • Re: About c++, sandeep
  • Re: About c++, pete
    • Re: About c++, Paul Mesken
      • Re: About c++, Kenny McCormack
      • Re: About c++, Alan Balmer
• "basic" pointer question, steve
  • Re: "basic" pointer question, Jonathan Bartlett
    • Re: "basic" pointer question, steve
      • Re: "basic" pointer question, Jonathan Bartlett
  • Re: "basic" pointer question, Richard Bos
    • Re: "basic" pointer question, steve
    • Re: "basic" pointer question, Netocrat
      • Re: "basic" pointer question, steve
  • Re: "basic" pointer question, CBFalconer
  • Re: "basic" pointer question, Rajan
    • Re: "basic" pointer question, pete
      • Re: "basic" pointer question, Rajan
      • Re: "basic" pointer question, Richard Bos
      • Re: "basic" pointer question, Martin Ambuhl
      • Re: "basic" pointer question, CBFalconer
      • Re: "basic" pointer question, Flash Gordon
      • Re: "basic" pointer question, pete
      • Re: "basic" pointer question, Rajan
      • Re: "basic" pointer question, john_bode
• XML serialization of structures, jacob navia
  • Re: XML serialization of structures, Suman
  • Re: XML serialization of structures, Paul Mesken
• Standard way of dealing with directories, josegomez
  • Re: Standard way of dealing with directories, David Resnick
• Re: read 32 bit value into 64 bit variable?, Grumble
• hiding structure members, Madhav
  • Re: hiding structure members, Bilgehan . Balban
  • Re: hiding structure members, Tydr Schnubbis
• endof, Michael B Allen
  • Re: endof, Suman
  • Re: endof, Michael Mair
    • Re: endof, Lawrence Kirby
      • Re: endof, Michael Mair
  • Re: endof, Christian Kandeler
    • Re: endof, Michael B Allen
      • Re: endof, Christian Kandeler
      • Re: endof, Michael Mair
      • Re: endof, Michael B Allen
• padding granularity, ranjeet . gupta
  • Re: padding granularity, Lawrence Kirby
• Finding Repeated and Missing Numbers, Harsha Srinath
  • Re: Finding Repeated and Missing Numbers, Richard Harter
    • Re: Finding Repeated and Missing Numbers, Harsha Srinath
      • Re: Finding Repeated and Missing Numbers, Chris Torek
      • Re: Finding Repeated and Missing Numbers, Lawrence Kirby
      • Re: Finding Repeated and Missing Numbers, pete
    • Re: Finding Repeated and Missing Numbers, CBFalconer
  • Re: Finding Repeated and Missing Numbers, Peter Nilsson
  • Re: Finding Repeated and Missing Numbers, John L
    • Re: Finding Repeated and Missing Numbers, Harsha Srinath
• Internal representation of char == unsigned small int?, Sathyaish
  • Re: Internal representation of char == unsigned small int?, Lew Pitcher
    • Re: Internal representation of char == unsigned small int?, Lew Pitcher
  • Re: Internal representation of char == unsigned small int?, Keith Thompson
  • Re: Internal representation of char == unsigned small int?, Malcolm
    • Re: Internal representation of char == unsigned small int?, Keith Thompson
• Default arguments, Sathyaish
  • Re: Default arguments, CBFalconer
  • Re: Default arguments, Jaspreet
    • Re: Default arguments, Michael Mair
      • Re: Default arguments, Jaspreet
      • Re: Default arguments, Michael Mair
      • Re: Default arguments, Jaspreet
    • Re: Default arguments, Alan Balmer
• Functions with variable arguments, Sathyaish
  • Re: Functions with variable arguments, CBFalconer
  • Re: Functions with variable arguments, SM Ryan
  • Re: Functions with variable arguments, Jaspreet
    • Re: Functions with variable arguments, Suman
      • Re: Functions with variable arguments, Jaspreet
• Re: convert int to char, Kenny McCormack
  • <Possible follow-ups>
  • Re: convert int to char, Robert Maas, see http://tinyurl.com/uh3t
    • Re: convert int to char, Anonymous 7843
    • Re: convert int to char, SM Ryan
    • Re: convert int to char, Walter Roberson
    • Re: convert int to char, Chris Croughton
• Microsoft Visual C++ 6.0, mikee188
  • Re: Microsoft Visual C++ 6.0, Erik de Castro Lopo
  • Re: Microsoft Visual C++ 6.0, Lefty Bigfoot
  • Re: Microsoft Visual C++ 6.0, Malcolm
  • Re: Microsoft Visual C++ 6.0, Emmanuel Delahaye
    • Re: Microsoft Visual C++ 6.0, Michael Wojcik
      • Re: Microsoft Visual C++ 6.0, Kenny McCormack
  • Re: Microsoft Visual C++ 6.0, hlwu
  • Re: Microsoft Visual C++ 6.0, onlywin_kr
    • Re: Microsoft Visual C++ 6.0, CBFalconer
      • Re: Microsoft Visual C++ 6.0, Guillaume
  • Re: Microsoft Visual C++ 6.0, onlywin_kr
• New File, EngineerGeek
  • Re: New File, SM Ryan
  • Re: New File, Martin Ambuhl
    • Re: New File, Martin Ambuhl
  • Re: New File, Gordon Burditt
    • Re: New File, SM Ryan
      • Re: New File, Kenny McCormack
      • Re: New File, SM Ryan
      • Re: New File, Kenny McCormack
      • Re: New File, EngineerGeek
  • Re: New File, Penguin_X
  • Re: New File, Penguin_X
• how to ask gcc to link with older library ?, KC
  • Re: how to ask gcc to link with older library ?, Walter Roberson
• constructing own error functions vs something like fprinf(), grocery_stocker
  • Re: constructing own error functions vs something like fprinf(), Eric Sosman
  • Re: constructing own error functions vs something like fprinf(), Lawrence Kirby
  • Re: constructing own error functions vs something like fprinf(), Anonymous 7843
    • Re: constructing own error functions vs something like fprinf(), Richard Tobin
      • Re: constructing own error functions vs something like fprinf(), Anonymous 7843
• What about a C compiler with structured data management INSIDE ?, HALLES
  • Re: What about a C compiler with structured data management INSIDE ?, CBFalconer
    • Re: What about a C compiler with structured data management INSIDE ?, HALLES
      • Re: What about a C compiler with structured data management INSIDE ?, Keith Thompson
• Implementing my own memcpy, Rajan
  • Re: Implementing my own memcpy, Netocrat
    • Re: Implementing my own memcpy, Rajan
      • Re: Implementing my own memcpy, Ben Pfaff
      • Re: Implementing my own memcpy, Lawrence Kirby
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Clark S . Cox III
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, pete
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Lefty Bigfoot
      • Re: Implementing my own memcpy, Chris Torek
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, pete
      • Re: Implementing my own memcpy, CBFalconer
    • Re: Implementing my own memcpy, Robert W Hand
      • Re: Implementing my own memcpy, Netocrat
    • Re: Implementing my own memcpy, Chris Torek
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Chris Torek
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Stan Milam
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Mark F. Haigh
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Richard Harter
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, Richard Harter
      • Re: Implementing my own memcpy, Netocrat
      • Re: Implementing my own memcpy, pete
      • Re: Implementing my own memcpy, Richard Harter
      • Re: Implementing my own memcpy, Michael Mair
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Richard Harter
      • Re: Implementing my own memcpy, pete
      • Re: Implementing my own memcpy, Richard Harter
      • Re: Implementing my own memcpy, pete
      • Message not available
      • Re: Implementing my own memcpy, pete
      • Re: Implementing my own memcpy, Richard Harter
    • Re: Implementing my own memcpy, Kevin Bagust
      • Re: Implementing my own memcpy, Netocrat
  • Re: Implementing my own memcpy, Ben Pfaff
  • Re: Implementing my own memcpy, Stan Milam
    • Re: Implementing my own memcpy, Nils Weller
      • Re: Implementing my own memcpy, Stan Milam
      • Re: Implementing my own memcpy, Michael Wojcik
      • Re: Implementing my own memcpy, CBFalconer
      • Re: Implementing my own memcpy, Nils Weller
• Data Structure, ranjeet . gupta
  • Re: Data Structure, Roger Leigh
    • Re: Data Structure, Malcolm
      • Re: Data Structure, Roger Leigh
    • Re: Data Structure, Chris Torek
  • Re: Data Structure, He Shiming
  • Re: Data Structure, Barry Schwarz
• nested while - how to go to the beginning of the first while?, invni
  • Re: nested while - how to go to the beginning of the first while?, Suman
  • Re: nested while - how to go to the beginning of the first while?, Robert W Hand
    • Re: nested while - how to go to the beginning of the first while?, invni
  • Re: nested while - how to go to the beginning of the first while?, CBFalconer
    • Re: nested while - how to go to the beginning of the first while?, Netocrat
    • Re: nested while - how to go to the beginning of the first while?, Malcolm
    • Re: nested while - how to go to the beginning of the first while?, Lawrence Kirby
      • Re: nested while - how to go to the beginning of the first while?, Robert Maas, see http://tinyurl.com/uh3t
      • Re: nested while - how to go to the beginning of the first while?, Michael Mair
      • Re: nested while - how to go to the beginning of the first while?, CBFalconer
      • Re: nested while - how to go to the beginning of the first while?, Michael Mair
      • Re: nested while - how to go to the beginning of the first while?, CBFalconer
      • Re: nested while - how to go to the beginning of the first while?, Lawrence Kirby
  • Re: nested while - how to go to the beginning of the first while?, akarl
    • Re: nested while - how to go to the beginning of the first while?, Kenny McCormack
      • Message not available
      • Re: nested while - how to go to the beginning of the first while?, Kenny McCormack
      • Message not available
      • Re: nested while - how to go to the beginning of the first while?, Kenny McCormack
  • Re: nested while - how to go to the beginning of the first while?, Richard Harter
• function arguments question (newbie), Yoni Rabkin Katzenell
  • Re: function arguments question (newbie), Suman
    • Re: function arguments question (newbie), Yoni Rabkin Katzenell
      • Re: function arguments question (newbie), Suman
  • Re: function arguments question (newbie), Lawrence Kirby
• A biiiig break ?, Olivier
  • Re: A biiiig break ?, Keith Thompson
    • Re: A biiiig break ?, Olivier
      • Re: A biiiig break ?, Malcolm
      • Re: A biiiig break ?, Olivier
      • Re: A biiiig break ?, Chris Torek
      • Re: A biiiig break ?, Robert Gamble
      • Re: A biiiig break ?, Olivier
• realloc, copy and VM, Jean-Claude Arbaut
  • Re: realloc, copy and VM, Gordon Burditt
    • Re: realloc, copy and VM, Jean-Claude Arbaut
  • Re: realloc, copy and VM, Anonymous 7843
    • Re: realloc, copy and VM, Anonymous 7843
  • Re: realloc, copy and VM, Keith Thompson
    • Re: realloc, copy and VM, Jean-Claude Arbaut
  • Re: realloc, copy and VM, Michael Wojcik
    • Re: realloc, copy and VM, CBFalconer
• compiler unable to find defn. of sin(), sudip
  • Re: compiler unable to find defn. of sin(), Artie Gold
  • Re: compiler unable to find defn. of sin(), Martin Ambuhl
• printf() with too many args -- legal?, Kenneth Brody
  • Re: printf() with too many args -- legal?, Mark
    • Re: printf() with too many args -- legal?, Robert Gamble
  • Re: printf() with too many args -- legal?, Eric Sosman
    • Re: printf() with too many args -- legal?, Kenneth Brody
      • Re: printf() with too many args -- legal?, Simon Biber
      • Re: printf() with too many args -- legal?, Keith Thompson
    • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, Rouben Rostamian
      • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, Lawrence Kirby
      • Re: printf() with too many args -- legal?, Christian Kandeler
      • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, pete
      • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, pete
      • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, CBFalconer
      • Re: printf() with too many args -- legal?, Kenny McCormack
      • Re: printf() with too many args -- legal?, Chris Torek
      • Re: printf() with too many args -- legal?, Robert Gamble
      • Re: printf() with too many args -- legal?, Peter Nilsson
      • Re: printf() with too many args -- legal?, Robert Gamble
  • Re: printf() with too many args -- legal?, Robert Gamble
    • Re: printf() with too many args -- legal?, Stan R.
    • Re: printf() with too many args -- legal?, Stan R.
  • Re: printf() with too many args -- legal?, Lawrence Kirby
  • Re: printf() with too many args -- legal?, CBFalconer
  • <Possible follow-ups>
  • Re: printf() with too many args -- legal?, Stan R.
• static function declaration in header file, Ravi
  • Re: static function declaration in header file, Eric Sosman
    • Re: static function declaration in header file, Ravi
      • Re: static function declaration in header file, Clark S . Cox III
      • Re: static function declaration in header file, Peter "Shaggy" Haywood
  • Re: static function declaration in header file, Alan Balmer
  • Re: static function declaration in header file, CBFalconer
• Convert hex string to struct, Ross
  • Re: Convert hex string to struct, Suman
  • Re: Convert hex string to struct, Martin Ambuhl
  • Re: Convert hex string to struct, Suman
  • Re: Convert hex string to struct, Al Bowers
• URL+JPEG+MPEG+P2P blocking, Shobhit
  • Re: URL+JPEG+MPEG+P2P blocking, Kenny McCormack
  • Re: URL+JPEG+MPEG+P2P blocking, #2pencil
• Memset Optimizing, prcpani
  • Re: Memset Optimizing, Eric Sosman
    • Re: Memset Optimizing, prcpani
      • Re: Memset Optimizing, Michael Mair
    • Re: Memset Optimizing, prcpani
• C preprocessor, selvesteen
  • Re: C preprocessor, Chris Dollin
    • Re: C preprocessor, CBFalconer
  • Re: C preprocessor, pete
  • Re: C preprocessor, snnn
    • Re: C preprocessor, pete
• Using macros as function_names (for compiling different function_names with one C-Code via a compile flag), Andreas Morgenstern
  • Re: Using macros as function_names (for compiling different function_names with one C-Code via a compile flag), Grumble
  • Re: Using macros as function_names (for compiling different function_names with one C-Code via a compile flag), SM Ryan
• Hmmm, It's Curious, Stan Milam
  • Re: Hmmm, It's Curious, pete
    • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, Chris Torek
      • Re: Hmmm, It's Curious, CBFalconer
  • Re: Hmmm, It's Curious, CBFalconer
    • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, pete
  • Re: Hmmm, It's Curious, pete
  • Re: Hmmm, It's Curious, pete
    • Re: Hmmm, It's Curious, pete
    • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, Chris Dollin
      • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, Ben Pfaff
      • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Ben Pfaff
      • Re: Hmmm, It's Curious, Jean-Claude Arbaut
      • Re: Hmmm, It's Curious, CBFalconer
      • Re: Hmmm, It's Curious, Stan Milam
      • Re: Hmmm, It's Curious, jdallen2000
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Randy Howard
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Stan Milam
    • Re: Hmmm, It's Curious, Mark
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Mark
      • Re: Hmmm, It's Curious, Mark
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Mark
      • Re: Hmmm, It's Curious, Netocrat
      • Re: Hmmm, It's Curious, Mark
• 1/2 =?, hyu163
  • Re: 1/2 =?, Lew Pitcher
    • Re: 1/2 =?, Robert Gamble
  • Re: 1/2 =?, pete
  • Re: 1/2 =?, Artie Gold
  • Re: 1/2 =?, Dan Henry
  • Re: 1/2 =?, CBFalconer
  • Re: 1/2 =?, MJ
  • Re: 1/2 =?, akarl
  • Re: 1/2 =?, snnn
  • Re: 1/2 =?, Robert Maas, see http://tinyurl.com/uh3t
    • Re: 1/2 =?, akarl
    • Re: 1/2 =?, Chris Croughton
    • Re: 1/2 =?, Walter Roberson
      • Re: 1/2 =?, CBFalconer
• C software achitecture, joel . winteregg
  • Re: C software achitecture, pete
    • Re: C software achitecture, hatman
  • Re: C software achitecture, Roger Leigh
    • Re: C software achitecture, hatman
      • Re: C software achitecture, pete
      • Re: C software achitecture, hatman
      • Re: C software achitecture, pete
      • Re: C software achitecture, hatman
      • Re: C software achitecture, pete
      • Re: C software achitecture, hatman
      • Re: C software achitecture, pete
      • Re: C software achitecture, hatman
      • Re: C software achitecture, pete
      • Re: C software achitecture, hatman
      • Re: C software achitecture, Roger Leigh
  • Re: C software achitecture, Gordon Burditt
    • Re: C software achitecture, hatman
      • Re: C software achitecture, hatman
      • Re: C software achitecture, Lawrence Kirby
      • Re: C software achitecture, Default User
      • Re: C software achitecture, Gordon Burditt
      • Re: C software achitecture, hatman
• Re: [OT] Re: "use CGI " hangs "CGI time out ", Gordon Burditt
  • Re: [OT] Re: "use CGI " hangs "CGI time out ", Stan R.
  • <Possible follow-ups>
  • Re: [OT] Re: "use CGI " hangs "CGI time out ", A. Sinan Unur
• how to let gcc warn me when I use = in conditions, PengYu.UT@xxxxxxxxx
  • Re: how to let gcc warn me when I use = in conditions, Emmanuel Delahaye
    • Re: how to let gcc warn me when I use = in conditions, PengYu.UT@xxxxxxxxx
      • Re: how to let gcc warn me when I use = in conditions, Emmanuel Delahaye
  • Re: how to let gcc warn me when I use = in conditions, CBFalconer
    • Re: how to let gcc warn me when I use = in conditions, Randy Howard
      • Re: how to let gcc warn me when I use = in conditions, websnarf
      • Re: how to let gcc warn me when I use = in conditions, Lawrence Kirby
      • Re: how to let gcc warn me when I use = in conditions, Richard Bos
      • Re: how to let gcc warn me when I use = in conditions, websnarf
      • Re: how to let gcc warn me when I use = in conditions, Mark
      • Re: how to let gcc warn me when I use = in conditions, Michael Mair
      • Re: how to let gcc warn me when I use = in conditions, Mark
      • Re: how to let gcc warn me when I use = in conditions, Michael Mair
      • Re: how to let gcc warn me when I use = in conditions, Lawrence Kirby
      • Re: how to let gcc warn me when I use = in conditions, CBFalconer
      • Re: how to let gcc warn me when I use = in conditions, Michael Wojcik
      • Re: how to let gcc warn me when I use = in conditions, Alan Balmer
      • Re: how to let gcc warn me when I use = in conditions, Stan R.
    • Re: how to let gcc warn me when I use = in conditions, Alan Balmer
      • Re: how to let gcc warn me when I use = in conditions, CBFalconer
      • Re: how to let gcc warn me when I use = in conditions, Alan Balmer
      • Re: how to let gcc warn me when I use = in conditions, Kenny McCormack
      • Re: how to let gcc warn me when I use = in conditions, Alan Balmer
      • Re: how to let gcc warn me when I use = in conditions, CBFalconer
      • Re: how to let gcc warn me when I use = in conditions, Eric Sosman
    • Re: how to let gcc warn me when I use = in conditions, Richard Bos
      • Re: how to let gcc warn me when I use = in conditions, CBFalconer
      • Re: how to let gcc warn me when I use = in conditions, Richard Bos
      • Re: how to let gcc warn me when I use = in conditions, websnarf
      • Re: how to let gcc warn me when I use = in conditions, Randy Howard
      • Re: how to let gcc warn me when I use = in conditions, CBFalconer
  • Re: how to let gcc warn me when I use = in conditions, Stan R.
  • Re: how to let gcc warn me when I use = in conditions, Rob Thorpe
    • Re: how to let gcc warn me when I use = in conditions, Kenny McCormack
    • Re: how to let gcc warn me when I use = in conditions, Alan Balmer
  • Re: how to let gcc warn me when I use = in conditions, akarl
  • Re: how to let gcc warn me when I use = in conditions, Cool Guy
  • Re: how to let gcc warn me when I use = in conditions, Anonymous 7843
    • Re: how to let gcc warn me when I use = in conditions, Mark
      • Re: how to let gcc warn me when I use = in conditions, Anonymous 7843
• GNU MP (gmp) implementation documentation, heinzSchmolke
  • Re: GNU MP (gmp) implementation documentation, Grumble
• What does it mean ?, ranjeet . gupta
  • Re: What does it mean ?, Jaspreet
  • Re: What does it mean ?, Eric Sosman
    • Re: What does it mean ?, forayer
      • Re: What does it mean ?, Eric Sosman
    • Re: What does it mean ?, ranjeet . gupta
      • Re: What does it mean ?, forayer
      • Re: What does it mean ?, Eric Sosman
      • Re: What does it mean ?, ranjeet . gupta
      • Re: What does it mean ?, forayer
      • Re: What does it mean ?, ranjeet . gupta
      • Re: What does it mean ?, ranjeet . gupta
  • Re: What does it mean ?, Mark
• code not working properly, Madhav
  • Re: code not working properly, Grumble
  • Re: code not working properly, manoj1978
  • Re: code not working properly, Keith Thompson
  • Re: code not working properly, jacob navia
• Trimming whitespaces, john_g83
  • Re: Trimming whitespaces, pete
    • Re: Trimming whitespaces, pete
  • Re: Trimming whitespaces, Rajan
  • Re: Trimming whitespaces, Rajan
    • Re: Trimming whitespaces, Al Bowers
      • Re: Trimming whitespaces, Ben Bacarisse
      • Re: Trimming whitespaces, Al Bowers
      • Re: Trimming whitespaces, Rajan
  • Re: Trimming whitespaces, john_bode
  • Re: Trimming whitespaces, CBFalconer
    • Re: Trimming whitespaces, Chris Torek
      • Re: Trimming whitespaces, Nils Weller
  • Re: Trimming whitespaces, SM Ryan
• Reason for the Format, ranjeet . gupta
  • Re: Reason for the Format, Jaspreet
  • Re: Reason for the Format, SM Ryan
    • Re: Reason for the Format, Grumble
      • Re: Reason for the Format, SM Ryan
      • Re: Reason for the Format, Chris Torek
  • Re: Reason for the Format, john_bode
    • Re: Reason for the Format, SM Ryan
• Origin of size_t? Curious., Confused User
  • Re: Origin of size_t? Curious., Morris Dovey
    • Re: Origin of size_t? Curious., Clark S . Cox III
      • Re: Origin of size_t? Curious., Morris Dovey
      • Re: Origin of size_t? Curious., P.J. Plauger
    • Re: Origin of size_t? Curious., Robert Gamble
  • Re: Origin of size_t? Curious., Gordon Burditt
    • Re: Origin of size_t? Curious., S.Tobias
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., S.Tobias
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Randy Howard
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., lawrence . jones
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., S.Tobias
      • Re: Origin of size_t? Curious., Christian Bau
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Chris Torek
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Chris Torek
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., pete
      • Re: Origin of size_t? Curious., Randy Howard
      • Re: Origin of size_t? Curious., CBFalconer
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., CBFalconer
      • Re: Origin of size_t? Curious., Lawrence Kirby
      • Re: Origin of size_t? Curious., Clark S . Cox III
      • Re: Origin of size_t? Curious., Robert Gamble
      • Re: Origin of size_t? Curious., Stan R.
  • Re: Origin of size_t? Curious., Stan R.
    • Re: Origin of size_t? Curious., Stan R.
• how come such code can compile?, linq936
  • Re: how come such code can compile?, Jean-Claude Arbaut
    • Re: how come such code can compile?, linq936
      • Re: how come such code can compile?, Jean-Claude Arbaut
      • Re: how come such code can compile?, akarl
  • Re: how come such code can compile?, Morris Dovey
    • Re: how come such code can compile?, linq936
      • Re: how come such code can compile?, Default User
    • Re: how come such code can compile?, Lawrence Kirby
    • Re: how come such code can compile?, Peter "Shaggy" Haywood
    • Re: how come such code can compile?, Old Wolf
• the usage of void argument, PengYu.UT@xxxxxxxxx
  • Re: the usage of void argument, Eric Sosman
    • Re: the usage of void argument, Alan Balmer
  • Re: the usage of void argument, Malcolm
  • Re: the usage of void argument, Rajan
    • Re: the usage of void argument, Suman
    • Re: the usage of void argument, Suman
      • Re: the usage of void argument, ade ishs
      • Re: the usage of void argument, Suman
  • Re: the usage of void argument, Joel
    • Re: the usage of void argument, forayer
      • Re: the usage of void argument, Lawrence Kirby
  • Re: the usage of void argument, john_bode
    • Re: the usage of void argument, PengYu.UT@xxxxxxxxx
      • Re: the usage of void argument, john_bode
  • Re: the usage of void argument, Jaspreet
• How to calculate the inverse of normal distribution using "C" ?, PCHOME
  • Re: How to calculate the inverse of normal distribution using "C" ?, Grumble
  • Re: How to calculate the inverse of normal distribution using "C" ?, Lawrence Kirby
    • Re: How to calculate the inverse of normal distribution using "C" ?, Jean-Claude Arbaut
• Endianness, bush
  • Re: Endianness, Eric Sosman
    • Re: Endianness, Felix Rawlings
      • Re: Endianness, Eric Sosman
      • Re: Endianness, Lawrence Kirby
  • Re: Endianness, Tydr Schnubbis
• Return type of main(), Christopher Benson-Manica
  • Re: Return type of main(), Chris Torek
  • Re: Return type of main(), Old Wolf
  • Re: Return type of main(), Jack Klein
  • Re: Return type of main(), Suman
• Writable strings, Jason Curl
  • Re: Writable strings, Lawrence Kirby
    • Re: Writable strings, Omri Barel
      • Re: Writable strings, Malcolm
      • Re: Writable strings, Jack Klein
      • Re: Writable strings, Rajan
      • Re: Writable strings, pete
      • Re: Writable strings, Rajan
      • Re: Writable strings, pete
      • Re: Writable strings, Default User
      • Re: Writable strings, Lawrence Kirby
• malloc_consolidate, bkkishore
  • Re: malloc_consolidate, Grumble
• Does wrong format specifier leads to memory corruption?, indushekara
  • Re: Does wrong format specifier leads to memory corruption?, Richard Bos
  • Re: Does wrong format specifier leads to memory corruption?, Alan Balmer
    • Re: Does wrong format specifier leads to memory corruption?, CBFalconer
      • Re: Does wrong format specifier leads to memory corruption?, Alan Balmer
• Really **wonderful** website for C interview questions!!!!!, rajanarayan2005
  • Re: Really **wonderful** website for C interview questions!!!!!, Morris Dovey
    • Re: Really **wonderful** website for C interview questions!!!!!, rajanarayan2005
  • Re: Really **wonderful** website for C interview questions!!!!!, Richard Bos
    • Re: Really **wonderful** website for C interview questions!!!!!, rajanarayan2005
      • Re: Really **wonderful** website for C interview questions!!!!!, Robert Gamble
      • Re: Really **wonderful** website for C interview questions!!!!!, Randy Howard
      • Re: Really **wonderful** website for C interview questions!!!!!, Mark
      • Re: Really **wonderful** website for C interview questions!!!!!, Robert Gamble
    • Re: Really **wonderful** website for C interview questions!!!!!, rajanarayan2005
    • Re: Really **wonderful** website for C interview questions!!!!!, rajanarayan2005
      • Re: Really **wonderful** website for C interview questions!!!!!, Lawrence Kirby
    • Re: Really **wonderful** website for C interview questions!!!!!, Suman
      • Re: Really **wonderful** website for C interview questions!!!!!, pete
  • Re: Really **wonderful** website for C interview questions!!!!!, Robert Gamble
    • Re: Really **wonderful** website for C interview questions!!!!!, Jason Curl
      • Re: Really **wonderful** website for C interview questions!!!!!, Malcolm
      • Re: Really **wonderful** website for C interview questions!!!!!, Lawrence Kirby
• smallest positive double number, gouqizi.lvcha@xxxxxxxxx
  • Re: smallest positive double number, CBFalconer
  • Re: smallest positive double number, Richard Bos
    • Re: smallest positive double number, Jean-Claude Arbaut
      • Re: smallest positive double number, Grumble
      • Re: smallest positive double number, Jean-Claude Arbaut
      • Re: smallest positive double number, pete
      • Re: smallest positive double number, Jean-Claude Arbaut
  • Re: smallest positive double number, Grumble
    • Re: smallest positive double number, Tim Prince
    • Re: smallest positive double number, AC
  • Re: smallest positive double number, E. Robert Tisdale
• Regardng algo book, MJ
  • Re: Regardng algo book, Keith Thompson
  • Re: Regardng algo book, Lawrence Kirby
    • Re: Regardng algo book, Jean-Claude Arbaut
      • Re: Regardng algo book, Robert Gamble
      • Re: Regardng algo book, Ben Pfaff
      • Re: Regardng algo book, Jean-Claude Arbaut
      • Re: Regardng algo book, pete
      • Re: Regardng algo book, Robert Gamble
      • Re: Regardng algo book, Ben Pfaff
      • Re: Regardng algo book, Robert Gamble
• Re: A World Beyond Capitalism 2005, An Annual International Multiracial Alliance Building Peace Conference Is Accepting Proposals..., mensanator@xxxxxxx
  • Re: A World Beyond Capitalism 2005, An Annual International Mult, Jenta
• string comparison, yadurajj
  • Re: string comparison, Lew Pitcher
  • Re: string comparison, SM Ryan
    • Re: string comparison, Lew Pitcher
      • Re: string comparison, Peter Nilsson
      • Re: string comparison, Netocrat
      • Re: string comparison, Lawrence Kirby
      • Re: string comparison, Netocrat
      • Re: string comparison, Netocrat
      • Re: string comparison, Ben Pfaff
      • Message not available
      • Re: string comparison, Al Bowers
      • Re: string comparison, pete
      • Re: string comparison, Lawrence Kirby
      • Re: string comparison, lawrence . jones
      • Re: string comparison, CBFalconer
      • Re: string comparison, Morris Dovey
      • Re: string comparison, Lew Pitcher
      • Re: string comparison, Netocrat
      • Re: string comparison, CBFalconer
      • Re: string comparison, Netocrat
      • Re: string comparison, Peter Nilsson
      • Re: string comparison, Lawrence Kirby
      • Re: string comparison, Old Wolf
  • Re: string comparison, kaby
    • Re: string comparison, Lawrence Kirby
  • Re: string comparison, Lawrence Kirby
  • Re: string comparison, websnarf
    • Re: string comparison, Netocrat
      • Re: string comparison, CBFalconer
      • Re: string comparison, Netocrat
      • Re: string comparison, Randy Howard
      • Re: string comparison, Netocrat
      • Re: string comparison, Randy Howard
      • Re: string comparison, Netocrat
      • Re: string comparison, CBFalconer
      • Re: string comparison, Netocrat
      • Re: string comparison, Lawrence Kirby
      • Re: string comparison, Netocrat
      • Re: string comparison, Lawrence Kirby
      • Re: string comparison, Netocrat
  • Re: string comparison, Rajan
    • Re: string comparison, pete
      • Re: string comparison, Rajan
      • Re: string comparison, pete
• The New C Standard - free ebook for C coders, jchludzinski@xxxxxxxxx
  • Re: The New C Standard - free ebook for C coders, Richard Bos
    • Re: The New C Standard - free ebook for C coders, Michael Wojcik
      • Re: The New C Standard - free ebook for C coders, lawrence . jones
      • Re: The New C Standard - free ebook for C coders, Michael Wojcik
      • Re: The New C Standard - free ebook for C coders, Derek M Jones
  • Re: The New C Standard - free ebook for C coders, lawrence . jones
  • Re: The New C Standard - free ebook for C coders, Randy Howard
    • Re: The New C Standard - free ebook for C coders, CBFalconer
      • Re: The New C Standard - free ebook for C coders, Randy Howard
• C code for converting IBM/370 floating point to IEEE 754?, Benjamin Rutt
  • Re: C code for converting IBM/370 floating point to IEEE 754?, Robert Gamble
  • Re: C code for converting IBM/370 floating point to IEEE 754?, lawrence . jones
• seeking in binary files, REH
  • Re: seeking in binary files, Ben Pfaff
    • Re: seeking in binary files, Lawrence Kirby
      • Re: seeking in binary files, Dik T. Winter
      • Re: seeking in binary files, Jean-Claude Arbaut
      • Re: seeking in binary files, Lawrence Kirby
      • Re: seeking in binary files, REH
      • Re: seeking in binary files, Ben Pfaff
      • Re: seeking in binary files, Richard Tobin
• program artichecture extractor tool, bsimaie
• passing pointers, PengYu.UT@xxxxxxxxx
  • Re: passing pointers, Lawrence Kirby
• Enlarge the stack size in gcc ?, Qoo
  • Re: Enlarge the stack size in gcc ?, David Resnick
  • Re: Enlarge the stack size in gcc ?, Anonymous 7843
• C calling conventions, aarklon
  • Re: C calling conventions, Roger Leigh
    • Re: C calling conventions, Jean-Claude Arbaut
      • Re: C calling conventions, Jean-Claude Arbaut
  • Re: C calling conventions, Jean-Claude Arbaut
  • Re: C calling conventions, Keith Thompson
    • Re: C calling conventions, jdallen2000
  • Re: C calling conventions, Eric Sosman
  • Re: C calling conventions, jacob navia
    • Re: C calling conventions, Keith Thompson
    • Re: C calling conventions, Spiro Trikaliotis
      • Re: C calling conventions, jacob navia
      • Re: C calling conventions, CBFalconer
      • Re: C calling conventions, Richard Bos
  • Re: C calling conventions, Malcolm
  • Off Topic: C Application Binary Interface (ABI), E. Robert Tisdale
  • Re: C calling conventions, CBFalconer
• Portability, Stephen Mayes
  • Re: Portability, P.J. Plauger
    • Re: Portability, CBFalconer
      • Re: Portability, Emmanuel Delahaye
    • Re: Portability, Ben Pfaff
      • Re: Portability, Eric Sosman
      • Re: Portability, Martijn
    • Re: Portability, Malcolm
      • Re: Portability, Roger Leigh
      • Re: Portability, Richard Harter
      • Re: Portability, pete
      • Re: Portability, Richard Bos
    • Re: Portability, websnarf
    • Re: Portability, Kevin Handy
  • Re: Portability, REH
  • Re: Portability, Eric Sosman
  • Re: Portability, Martijn
  • Re: Portability, john_bode
  • Re: Portability, Anonymous 7843
  • Re: Portability, Flash Gordon
  • Re: Portability, Malcolm
  • Re: Portability, Walter Roberson
    • Re: Portability, Anonymous 7843
      • Re: Portability, Walter Roberson
  • Re: Portability, robert . thorpe
  • Re: Portability, Michael Wojcik
• formatting output in the form of table, rashmi
  • Re: formatting output in the form of table, Rajan
• Char difference between C90 and C99, Jason Curl
  • Re: Char difference between C90 and C99, Keith Thompson
  • Re: Char difference between C90 and C99, Lawrence Kirby
    • Re: Char difference between C90 and C99, Stephen Mayes
      • Re: Char difference between C90 and C99, Lawrence Kirby
  • Re: Char difference between C90 and C99, Malcolm
    • Re: Char difference between C90 and C99, Jason Curl
      • Re: Char difference between C90 and C99, Lawrence Kirby
      • Re: Char difference between C90 and C99, Malcolm
      • Re: Char difference between C90 and C99, Old Wolf
      • Re: Char difference between C90 and C99, Jason Curl
      • Re: Char difference between C90 and C99, pete
• How does malloc align pointer, junky_fellow
  • Re: How does malloc align pointer, Keith Thompson
    • Re: How does malloc align pointer, Peter Ammon
      • Re: How does malloc align pointer, Keith Thompson
  • Re: How does malloc align pointer, Chris Dollin
  • Re: How does malloc align pointer, Anonymous 7843
    • Re: How does malloc align pointer, Lawrence Kirby
      • Re: How does malloc align pointer, Anonymous 7843
      • Re: How does malloc align pointer, Lawrence Kirby
      • Re: How does malloc align pointer, Anonymous 7843
• How to parse ?, junky_fellow
  • Re: How to parse ?, Zoran Cutura
  • Re: How to parse ?, john_bode
• Printing offset of a member of structure, junky_fellow
  • Re: Printing offset of a member of structure, Keith Thompson
    • Re: Printing offset of a member of structure, junky_fellow
      • Re: Printing offset of a member of structure, Lawrence Kirby
  • Re: Printing offset of a member of structure, Richard Bos
  • Re: Printing offset of a member of structure, CBFalconer
  • Re: Printing offset of a member of structure, Rajan
    • Re: Printing offset of a member of structure, Jack Klein
      • Re: Printing offset of a member of structure, Rajan
      • Re: Printing offset of a member of structure, Keith Thompson
  • Re: Printing offset of a member of structure, Lawrence Kirby
• Enumatrators And Macros, ranjeet . gupta
  • Re: Enumatrators And Macros, CBFalconer
  • Re: Enumatrators And Macros, akarl
• Problem while transferring mail ids from MS-outlook to the application, vamsikrishna_b
  • Re: Problem while transferring mail ids from MS-outlook to the application, SM Ryan
    • Re: Problem while transferring mail ids from MS-outlook to the application, Keith Thompson
• Socket programming problem: can't generate output in server socket, ferbar
  • Re: Socket programming problem: can't generate output in server socket, Jack Klein
    • Re: Socket programming problem: can't generate output in server socket, Fernando Barsoba
  • Re: Socket programming problem: can't generate output in server socket, Dave Thompson
• large program data structure, Robert S
  • Re: large program data structure, Joe Wright
• reading Java floats from C, sbalko
  • Re: reading Java floats from C, Lawrence Kirby
    • Re: reading Java floats from C, sbalko
      • Re: reading Java floats from C, Malcolm
      • Re: reading Java floats from C, Lawrence Kirby
      • Re: reading Java floats from C, Joe Wright
• Issue related to system() call and file handles., gmtonyhoyt
  • Re: Issue related to system() call and file handles., Keith Thompson
  • Re: Issue related to system() call and file handles., Joe Wright
    • Re: Issue related to system() call and file handles., Keith Thompson
• Re: How to convert from Ticks to date&time?, Mark McIntyre
  • <Possible follow-ups>
  • Re: How to convert from Ticks to date&time?, Tim Prince
    • Re: How to convert from Ticks to date&time?, Eric Sosman
      • Re: How to convert from Ticks to date&time?, Richard Bos
• Undefined behaviour when modifying the result of an assignment operator, Andy Lomax
  • Re: Undefined behaviour when modifying the result of an assignment operator, Kenny McCormack
    • Re: Undefined behaviour when modifying the result of an assignment operator, Andy Lomax
      • Re: Undefined behaviour when modifying the result of an assignment operator, Christian Bau
  • Re: Undefined behaviour when modifying the result of an assignment operator, lawrence . jones
    • Re: Undefined behaviour when modifying the result of an assignment operator, Andy Lomax
      • Re: Undefined behaviour when modifying the result of an assignment operator, Keith Thompson
      • Re: Undefined behaviour when modifying the result of an assignment operator, Andy Lomax
• malloc(0), Mehta Shailendrakumar
  • Re: malloc(0), Richard Bos
    • Re: malloc(0), Jean-Claude Arbaut