comp.lang.c

• Date Index

---

• string search?, Bertram Trabant
  • Re: string search?, Richard Heathfield
• need for an extra variable., chandanlinster
  • Re: need for an extra variable., Zero
  • Re: need for an extra variable., Richard Heathfield
  • Re: need for an extra variable., Richard Tobin
    • Re: need for an extra variable., Richard Heathfield
• realloc(): invalid next size, solanki.chandrakant@xxxxxxxxx
  • Re: realloc(): invalid next size, Richard Heathfield
  • Re: realloc(): invalid next size, Herbert Rosenau
• how to design an testing example, qazwsx746
  • Re: how to design an testing example, Subbu
    • Re: how to design an testing example, Richard Heathfield
    • Re: how to design an testing example, Keith Thompson
• not writing to file, John Smith
  • Re: not writing to file, Adrian
  • Re: not writing to file, Jens Thoms Toerring
  • Re: not writing to file, Herbert Rosenau
• Triangular Matrix, Je-Givara
  • Re: Triangular Matrix, Simon Biber
  • Re: Triangular Matrix, Eric Sosman
• debugging, Sheldon
  • Re: debugging, Bill Pursell
    • Re: debugging, Sheldon
      • Re: debugging, Bill Pursell
      • Re: debugging, Sheldon
• C Interview Questions, dhruvaraj
  • Re: C Interview Questions, David Wade
  • Re: C Interview Questions, Richard Heathfield
    • Re: C Interview Questions, Adrian
      • Re: C Interview Questions, Richard Heathfield
      • Re: C Interview Questions, Simon Biber
      • Re: C Interview Questions, Richard Heathfield
    • Re: C Interview Questions, J. J. Farrell
      • Re: C Interview Questions, Keith Thompson
      • Re: C Interview Questions, Old Wolf
      • Re: C Interview Questions, Richard Heathfield
      • Re: C Interview Questions, Harald van Dijk
      • Re: C Interview Questions, Richard Heathfield
      • Re: C Interview Questions, William Hughes
• type identifier and OO design, Laurent Deniau
• if clause, rogz
  • Re: if clause, Nick Keighley
    • Re: if clause, rogz
    • Re: if clause, Bart
  • Re: if clause, mark_bluemel
  • Re: if clause, Barry
  • Re: if clause, Ancient_Hacker
    • Re: if clause, Michal Nazarewicz
      • Re: if clause, Ancient_Hacker
      • Re: if clause, Bill Medland
    • Re: if clause, Richard Heathfield
    • Re: if clause, Clever Monkey
    • Re: if clause, Al Balmer
    • Re: if clause, Eric Sosman
      • Re: if clause, Richard Heathfield
      • Re: if clause, Chris Dollin
      • Re: if clause, Richard Heathfield
      • Re: if clause, Chris Dollin
      • Re: if clause, Richard Heathfield
• Run a program behind screen, hurry
  • Re: Run a program behind screen, Richard Heathfield
• I have a problem in my study, qazwsx746
  • Re: I have a problem in my study, Cong Wang
    • Re: I have a problem in my study, Richard Heathfield
      • Re: I have a problem in my study, Cong Wang
  • Re: I have a problem in my study, mark_bluemel
  • Re: I have a problem in my study, Andrew Poelstra
    • Re: I have a problem in my study, Harald van Dijk
    • Re: I have a problem in my study, Chris Dollin
    • Re: I have a problem in my study, Herbert Rosenau
  • Re: I have a problem in my study, yuyang . sz
  • Re: I have a problem in my study, Mark McIntyre
    • Re: I have a problem in my study, Herbert Rosenau
      • Re: I have a problem in my study, Richard Heathfield
• structure pointers, raghu
  • Re: structure pointers, Richard Heathfield
    • Re: structure pointers, raghu
      • Re: structure pointers, Steven Kirby
      • Re: structure pointers, raghu
      • Re: structure pointers, Richard Heathfield
      • Re: structure pointers, Steven Kirby
  • Re: structure pointers, Fred Kleinschmidt
• finding how much the file system is full, from a C program?, prasadjoshi124
  • Re: finding how much the file system is full, from a C program?, SM Ryan
    • Re: finding how much the file system is full, from a C program?, Herbert Rosenau
      • Re: finding how much the file system is full, from a C program?, Walter Roberson
      • Re: finding how much the file system is full, from a C program?, Jordan Abel
      • Re: finding how much the file system is full, from a C program?, SM Ryan
      • Re: finding how much the file system is full, from a C program?, Herbert Rosenau
  • Re: finding how much the file system is full, from a C program?, "Nils O. Selåsdal"
    • Re: finding how much the file system is full, from a C program?, prasadjoshi124
  • Re: finding how much the file system is full, from a C program?, Walter Roberson
  • Re: finding how much the file system is full, from a C program?, Herbert Rosenau
  • Re: finding how much the file system is full, from a C program?, Iwo Mergler
• memory leakage problem, chets
  • Re: memory leakage problem, Walter Roberson
  • Re: memory leakage problem, Simon Biber
• free void*-- why not undefined behavior?, Kavya
  • Re: free void*-- why not undefined behavior?, Walter Roberson
  • Re: free void*-- why not undefined behavior?, Stephen Sprunk
    • Re: free void*-- why not undefined behavior?, Kavya
  • Re: free void*-- why not undefined behavior?, Andrew Poelstra
    • Re: free void*-- why not undefined behavior?, Default User
• how to use bit operation to do \sqrt(n), Thomas Zhu
  • Re: how to use bit operation to do \sqrt(n), websnarf
  • Re: how to use bit operation to do \sqrt(n), hurry
    • Re: how to use bit operation to do \sqrt(n), Yin Zhu
      • Re: how to use bit operation to do \sqrt(n), Richard Heathfield
      • Re: how to use bit operation to do \sqrt(n), Yin Zhu
      • Re: how to use bit operation to do \sqrt(n), Eric Sosman
      • Re: how to use bit operation to do \sqrt(n), Fred Kleinschmidt
      • Re: how to use bit operation to do \sqrt(n), Richard Bos
      • Re: how to use bit operation to do \sqrt(n), Martin Ambuhl
  • Re: how to use bit operation to do \sqrt(n), Ico
  • Re: how to use bit operation to do \sqrt(n), Richard Harter
• Out-of-bounds Restrictions?, Frederick Gotham
  • Re: Out-of-bounds Restrictions?, Eric Sosman
  • Re: Out-of-bounds Restrictions?, Kenny McCormack
  • Re: Out-of-bounds Restrictions?, Barry Schwarz
    • Re: Out-of-bounds Restrictions?, Frederick Gotham
  • Re: Out-of-bounds Restrictions?, Peter Nilsson
    • Re: Out-of-bounds Restrictions?, Dik T. Winter
      • Re: Out-of-bounds Restrictions?, Harald van Dijk
      • Re: Out-of-bounds Restrictions?, Dik T. Winter
      • Re: Out-of-bounds Restrictions?, Kavya
      • Re: Out-of-bounds Restrictions?, Harald van Dijk
• Sort it with one array and some tmp files, jason735
  • Re: Sort it with one array and some tmp files, CBFalconer
    • Re: Sort it with one array and some tmp files, Walter Roberson
      • Re: Sort it with one array and some tmp files, jason735
  • Re: Sort it with one array and some tmp files, Flash Gordon
  • Re: Sort it with one array and some tmp files, Julian V. Noble
• Structures or Array Notation for many possible strings of finite length?, nospam
  • Re: Structures or Array Notation for many possible strings of finite length?, Malcolm
  • Re: Structures or Array Notation for many possible strings of finite length?, Barry Schwarz
• Include path question, Jan Engelhardt
  • Re: Include path question, Richard Heathfield
  • Re: Include path question, Malcolm
    • Re: Include path question, Richard Heathfield
      • Re: Include path question, Malcolm
      • Re: Include path question, Barry
      • Systems w/o directories (Was: Include path question), Kenny McCormack
      • Re: Include path question, Ancient_Hacker
      • Re: Include path question, Malcolm
      • Re: Include path question, Barry Schwarz
      • Re: Include path question, Walter Roberson
      • Re: Include path question, Barry Schwarz
      • Re: Include path question, Walter Roberson
      • Re: Include path question, Jalapeno
      • Re: Include path question, Jalapeno
      • Re: Include path question, Gordon Burditt
      • Re: Include path question, Leor Zolman
      • Re: Include path question, Gordon Burditt
      • Re: Include path question, CBFalconer
      • Re: Include path question, Gordon Burditt
      • Re: Include path question, Leor Zolman
      • Re: Include path question, Kenny McCormack
      • Re: Include path question, Richard Heathfield
      • Re: Include path question, CBFalconer
  • Re: Include path question, Jean-Marc Bourguet
    • Re: Include path question, Jan Engelhardt
• Re: The Quantum Pyramid, Barry Schwarz
  • Re: The Quantum Pyramid, Richard Heathfield
  • Re: The Quantum Pyramid, Martin Ambuhl
  • <Possible follow-ups>
  • Re: The Quantum Pyramid, Bill Reid
    • [ot]Re: The Quantum Pyramid, pete
      • Re: [ot]Re: The Quantum Pyramid, Bill Reid
      • Re: [ot]Re: The Quantum Pyramid, Clever Monkey
  • Re: The Quantum Pyramid, Ancient_Hacker
• assembly in future C standard, fermineutron
  • Re: assembly in future C standard, Richard Heathfield
  • Re: assembly in future C standard, Andrew Poelstra
  • Re: assembly in future C standard, Michal Nazarewicz
  • Re: assembly in future C standard, sjdevnull@xxxxxxxxx
    • Re: assembly in future C standard, jacob navia
      • Re: assembly in future C standard, fermineutron
      • Re: assembly in future C standard, Richard Heathfield
      • Re: assembly in future C standard, fermineutron
      • Re: assembly in future C standard, Richard Heathfield
      • Re: assembly in future C standard, CBFalconer
      • Re: assembly in future C standard, fermineutron
      • Re: assembly in future C standard, Flash Gordon
      • Re: assembly in future C standard, Keith Thompson
      • Re: assembly in future C standard, Keith Thompson
      • Re: assembly in future C standard, Rod Pemberton
      • Re: assembly in future C standard, Keith Thompson
      • Re: assembly in future C standard, Kenny McCormack
      • Re: assembly in future C standard, Richard Heathfield
      • Re: assembly in future C standard, Kenny McCormack
      • Re: assembly in future C standard, Richard Heathfield
      • Re: assembly in future C standard, Rod Pemberton
      • Re: assembly in future C standard, Richard Heathfield
      • Re: assembly in future C standard, Default User
      • Re: assembly in future C standard, Rod Pemberton
      • Re: assembly in future C standard, Bill Reid
      • Re: assembly in future C standard, Kenny McCormack
      • Re: assembly in future C standard, Rod Pemberton
      • Re: assembly in future C standard, Kenny McCormack
      • Re: assembly in future C standard, Keith Thompson
      • Re: assembly in future C standard, Richard Bos
      • Re: assembly in future C standard, Eric Sosman
      • Re: assembly in future C standard, Ian Collins
      • Re: assembly in future C standard, Stephen Sprunk
      • Re: assembly in future C standard, John Bode
      • Re: assembly in future C standard, Jordan Abel
      • Re: assembly in future C standard, Arthur J. O'Dwyer
      • Re: assembly in future C standard, Richard Harter
      • Re: assembly in future C standard, John Bode
      • Re: assembly in future C standard, Chris Dollin
      • Re: assembly in future C standard, Gordon Burditt
      • Re: assembly in future C standard, Richard Bos
      • Re: assembly in future C standard, Bart
      • Re: assembly in future C standard, Eric Sosman
      • Re: assembly in future C standard, Chris Torek
      • Re: assembly in future C standard, sjdevnull@xxxxxxxxx
      • Re: assembly in future C standard, jacob navia
      • Re: assembly in future C standard, Richard Bos
  • Re: assembly in future C standard, Thomas Lumley
  • Re: assembly in future C standard, Gordon Burditt
    • Re: assembly in future C standard, Peter Nilsson
      • Re: assembly in future C standard, Keith Thompson
  • Re: assembly in future C standard, jacob navia
    • Re: assembly in future C standard, Chris Torek
• Memory allocation based on a big array, Frank W. Steiner
  • Re: Memory allocation based on a big array, CBFalconer
    • Re: Memory allocation based on a big array, jaysome
      • Re: Memory allocation based on a big array, CBFalconer
  • Re: Memory allocation based on a big array, Andrew Poelstra
• compiling problems, Sheldon
  • Re: compiling problems, Eric Sosman
  • Re: compiling problems, Bill Pursell
    • Re: compiling problems, Sheldon
  • Re: compiling problems, CBFalconer
    • Re: compiling problems, Sheldon
    • Re: compiling problems, Kenny McCormack
      • Re: compiling problems, Sheldon
      • Re: compiling problems, Keith Thompson
      • Re: compiling problems, Richard Heathfield
• printing all escape sequence characters, chandanlinster
  • Re: printing all escape sequence characters, Andrew Poelstra
  • Re: printing all escape sequence characters, backasswards
  • Re: printing all escape sequence characters, Barry Schwarz
    • Re: printing all escape sequence characters, Giorgio Silvestri
• pointer to an array -Is there an out of bound access?, Kavya
  • Re: pointer to an array -Is there an out of bound access?, Cong Wang
  • Re: pointer to an array -Is there an out of bound access?, Frederick Gotham
    • Re: pointer to an array -Is there an out of bound access?, Frederick Gotham
      • Re: pointer to an array -Is there an out of bound access?, Richard Heathfield
      • Re: pointer to an array -Is there an out of bound access?, Frederick Gotham
      • Re: pointer to an array -Is there an out of bound access?, Old Wolf
      • Re: pointer to an array -Is there an out of bound access?, Keith Thompson
      • Re: pointer to an array -Is there an out of bound access?, Richard Heathfield
      • Re: pointer to an array -Is there an out of bound access?, Keith Thompson
      • Re: pointer to an array -Is there an out of bound access?, Barry Schwarz
      • Re: pointer to an array -Is there an out of bound access?, Frederick Gotham
      • Re: pointer to an array -Is there an out of bound access?, Frederick Gotham
      • Re: pointer to an array -Is there an out of bound access?, Richard Heathfield
      • Re: pointer to an array -Is there an out of bound access?, Andrey Tarasevich
  • Re: pointer to an array -Is there an out of bound access?, pete
  • Re: pointer to an array -Is there an out of bound access?, james of tucson
• about TorboC, CCMC
  • Re: about TorboC, Kavya
    • Re: about TorboC, CBFalconer
      • [OT] Re: about TorboC, Joe Estock
  • Re: about TorboC, Malcolm
    • Re: about TorboC, Richard Bos
• C exe on winXP memory limitation, fermineutron
  • Re: C exe on winXP memory limitation, fermineutron
    • Re: C exe on winXP memory limitation, jacob navia
    • Re: C exe on winXP memory limitation, Ancient_Hacker
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, jacob navia
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Coos Haak
      • Re: C exe on winXP memory limitation, Flash Gordon
      • Re: C exe on winXP memory limitation, Mark McIntyre
  • Re: C exe on winXP memory limitation, T.M. Sommers
  • Re: C exe on winXP memory limitation, Bill Medland
    • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Kenneth Brody
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Richard Heathfield
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, Richard Heathfield
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, Walter Roberson
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, Flash Gordon
      • Re: C exe on winXP memory limitation, CBFalconer
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, Keith Thompson
      • Re: C exe on winXP memory limitation, Bart
      • Re: C exe on winXP memory limitation, Mark McIntyre
      • Re: C exe on winXP memory limitation, Iwo Mergler
      • Re: C exe on winXP memory limitation, Bill Medland
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Keith Thompson
      • Re: C exe on winXP memory limitation, Eric Sosman
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, fermineutron
      • Re: C exe on winXP memory limitation, Keith Thompson
      • Re: C exe on winXP memory limitation, Richard Heathfield
      • Re: C exe on winXP memory limitation, fermineutron
  • Re: C exe on winXP memory limitation, Richard Heathfield
    • Re: C exe on winXP memory limitation, Simon Biber
      • Re: C exe on winXP memory limitation, Richard Heathfield
• Weird Pointer In C, Please Help. Code supply..., MQ.john@xxxxxxxxx
  • Re: Weird Pointer In C, Please Help. Code supply..., Chris Johnson
    • Re: Weird Pointer In C, Please Help. Code supply..., Walter Roberson
    • Re: Weird Pointer In C, Please Help. Code supply..., Christopher Benson-Manica
      • Re: Weird Pointer In C, Please Help. Code supply..., Keith Thompson
    • Re: Weird Pointer In C, Please Help. Code supply..., MQ.john@xxxxxxxxx
      • Re: Weird Pointer In C, Please Help. Code supply..., Richard Heathfield
      • Re: Weird Pointer In C, Please Help. Code supply..., Eric Sosman
      • Re: Weird Pointer In C, Please Help. Code supply..., MQ.john@xxxxxxxxx
      • Re: Weird Pointer In C, Please Help. Code supply..., Chris Dollin
      • Re: Weird Pointer In C, Please Help. Code supply..., Eric Sosman
  • Re: Weird Pointer In C, Please Help. Code supply..., Chris Dollin
    • Re: Weird Pointer In C, Please Help. Code supply..., Keith Thompson
• Why do integer-to-double conversions do not happen in printf, arindam . mukerjee
  • Re: Why do integer-to-double conversions do not happen in printf, Chris Dollin
  • Re: Why do integer-to-double conversions do not happen in printf, mark_bluemel
    • Re: Why do integer-to-double conversions do not happen in printf, Ian Malone
  • Re: Why do integer-to-double conversions do not happen in printf, Bill Medland
  • Re: Why do integer-to-double conversions do not happen in printf, Eric Sosman
    • Re: Why do integer-to-double conversions do not happen in printf, arindam . mukerjee
      • Re: Why do integer-to-double conversions do not happen in printf, Eric Sosman
      • Re: Why do integer-to-double conversions do not happen in printf, Keith Thompson
      • Re: Why do integer-to-double conversions do not happen in printf, Eric Sosman
      • CT: Where did "implicit cast" originate? Was Re: Why do integer-to-double conversions do not happen in printf, Rod Pemberton
      • Re: CT: Where did "implicit cast" originate? Was Re: Why do integer-to-double conversions do not happen in printf, Joe Wright
      • Re: CT: Where did "implicit cast" originate? Was Re: Why do integer-to-double conversions do not happen in printf, Mark McIntyre
      • Re: CT: Where did "implicit cast" originate? Was Re: Why do integer-to-double conversions do not happen in printf, pete
  • Re: Why do integer-to-double conversions do not happen in printf, CBFalconer
    • Re: Why do integer-to-double conversions do not happen in printf, Keith Thompson
  • Re: Why do integer-to-double conversions do not happen in printf, james of tucson
  • Re: Why do integer-to-double conversions do not happen in printf, Keith Thompson
• operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Kavya
  • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Bart
  • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Richard Tobin
    • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Ahmed Kalembo
      • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Keith Thompson
      • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Ahmed Kalembo
      • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Frederick Gotham
      • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Frederick Gotham
      • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Dik T. Winter
  • Re: operators requiring lvalue/rvalue operands and resulting in rvalue/lvalue, Andrey Tarasevich
• Accessing structure members indirectly, Kavya
  • Re: Accessing structure members indirectly, Jens Thoms Toerring
    • Re: Accessing structure members indirectly, Ark
  • Re: Accessing structure members indirectly, Bart
  • Re: Accessing structure members indirectly, Richard Bos
  • Re: Accessing structure members indirectly, Walter Roberson
    • Re: Accessing structure members indirectly, Kavya
  • Re: Accessing structure members indirectly, Christopher Benson-Manica
    • Re: Accessing structure members indirectly, Kavya
      • Re: Accessing structure members indirectly, Christopher Benson-Manica
      • Re: Accessing structure members indirectly, Kavya
  • Re: Accessing structure members indirectly, Nick Keighley
  • Re: Accessing structure members indirectly, Andrew Poelstra
    • Re: Accessing structure members indirectly, Andrew Poelstra
    • Re: Accessing structure members indirectly, Keith Thompson
• re-definition of standard types, Roman Mashak
  • Re: re-definition of standard types, Bart
    • Re: re-definition of standard types, BRG
      • Re: re-definition of standard types, Malcolm
      • Re: re-definition of standard types, BRG
      • Re: re-definition of standard types, Malcolm
      • Re: re-definition of standard types, BRG
  • Re: re-definition of standard types, Harald van Dijk
  • Re: re-definition of standard types, websnarf
• typedef aliasing, James Brown
  • Re: typedef aliasing, Richard Heathfield
    • Re: typedef aliasing, James Brown
  • Re: typedef aliasing, Jens Thoms Toerring
    • Re: typedef aliasing, James Brown
• time() sleep() and dst, reppisch
  • Re: time() sleep() and dst, Richard Bos
    • Re: time() sleep() and dst, Jordan Abel
      • Re: time() sleep() and dst, CBFalconer
      • Re: time() sleep() and dst, Jordan Abel
      • Re: time() sleep() and dst, Flash Gordon
      • Re: time() sleep() and dst, Jordan Abel
      • Re: time() sleep() and dst, Gordon Burditt
      • Re: time() sleep() and dst, CBFalconer
      • Re: time() sleep() and dst, Eric Sosman
  • Re: time() sleep() and dst, Jordan Abel
    • Re: time() sleep() and dst, CBFalconer
  • Re: time() sleep() and dst, Ancient_Hacker
• Print bitmap file, Myombi Natuse
  • Re: Print bitmap file, Richard Bos
  • Re: Print bitmap file, Martin Ambuhl
  • Re: Print bitmap file, Bart
    • Re: Print bitmap file, Richard Heathfield
    • Re: Print bitmap file, Kenneth Brody
  • Re: Print bitmap file, CBFalconer
    • Re: Print bitmap file, Richard Tobin
  • Re: Print bitmap file, Andrew Poelstra
  • Re: Print bitmap file, Mark McIntyre
• Debugging C vs debugging C++, jacob navia
  • Re: Debugging C vs debugging C++, Spiros Bousbouras
    • Re: Debugging C vs debugging C++, Spiros Bousbouras
  • Re: Debugging C vs debugging C++, jacob navia
  • Re: Debugging C vs debugging C++, Ancient_Hacker
    • Re: Debugging C vs debugging C++, jacob navia
  • Re: Debugging C vs debugging C++, robertwessel2@xxxxxxxxx
  • Re: Debugging C vs debugging C++, websnarf
  • Re: Debugging C vs debugging C++, Ian Collins
    • Re: Debugging C vs debugging C++, Ancient_Hacker
      • Re: Debugging C vs debugging C++, CBFalconer
      • Re: Debugging C vs debugging C++, Ian Collins
• in something not a structure or union, Kodorna
  • Re: in something not a structure or union, Ancient_Hacker
    • Re: in something not a structure or union, Kodorna
      • Re: in something not a structure or union, Kodorna
      • Re: in something not a structure or union, Ancient_Hacker
    • Re: in something not a structure or union, CBFalconer
      • Re: in something not a structure or union, Joe Estock
  • Re: in something not a structure or union, Fred Kleinschmidt
• problems calling a function contained in a dll, Alan
  • Re: problems calling a function contained in a dll, Bill Medland
    • Re: problems calling a function contained in a dll, Alan
  • Re: problems calling a function contained in a dll, Keith Thompson
  • Re: problems calling a function contained in a dll, Ancient_Hacker
    • Re: problems calling a function contained in a dll, jacob navia
    • Re: problems calling a function contained in a dll, Alan
  • Re: problems calling a function contained in a dll, jacob navia
    • Re: problems calling a function contained in a dll, Ancient_Hacker
  • Re: problems calling a function contained in a dll, CBFalconer
    • Re: problems calling a function contained in a dll, Alan
      • Re: problems calling a function contained in a dll, Mark McIntyre
      • Re: problems calling a function contained in a dll, CBFalconer
      • Re: problems calling a function contained in a dll, Kenny McCormack
      • Re: problems calling a function contained in a dll, Kenny McCormack
• C / asm / long ints, fermineutron
  • Re: C / asm / long ints, Richard Heathfield
  • Re: C / asm / long ints, mensanator@xxxxxxx
  • Re: C / asm / long ints, Jack \"Abram\" Off
    • Re: C / asm / long ints, Richard Bos
      • Re: C / asm / long ints, stevenj
      • Re: C / asm / long ints, Richard Bos
  • Re: C / asm / long ints, Nishu
    • Re: C / asm / long ints, Chris Thomasson
      • Re: C / asm / long ints, CBFalconer
      • Re: C / asm / long ints, Chris Thomasson
      • Re: C / asm / long ints, Richard Bos
  • Re: C / asm / long ints, Rod Pemberton
    • Re: C / asm / long ints, Richard Heathfield
      • Re: C / asm / long ints, Rod Pemberton
      • Re: C / asm / long ints, Richard Heathfield
    • Re: C / asm / long ints, Mark F. Haigh
      • Re: C / asm / long ints, Rod Pemberton
      • Re: C / asm / long ints, Mark F. Haigh
  • Re: C / asm / long ints, Ancient_Hacker
• va_arg(), LIT
  • Re: va_arg(), Richard Tobin
  • Re: va_arg(), mark_bluemel
    • Re: va_arg(), LIT
      • Re: va_arg(), David Resnick
      • Re: va_arg(), mark_bluemel
      • Re: va_arg(), Laurent Deniau
      • Re: va_arg(), David Tiktin
      • Re: va_arg(), Eric Sosman
      • Re: va_arg(), Christopher Benson-Manica
      • Re: va_arg(), David Resnick
      • Re: va_arg(), Keith Thompson
      • Re: va_arg(), David Resnick
      • Re: va_arg(), Keith Thompson
      • Re: va_arg(), Keith Thompson
      • Re: va_arg(), Eric Sosman
      • Re: va_arg(), Christopher Benson-Manica
• define a struct that has its own type as a field somehow?, Ben
  • Re: define a struct that has its own type as a field somehow?, Papastefanos Serafeim
    • Re: define a struct that has its own type as a field somehow?, Ben
    • Re: define a struct that has its own type as a field somehow?, Chris Torek
  • Re: define a struct that has its own type as a field somehow?, Ben
  • Re: define a struct that has its own type as a field somehow?, Mark McIntyre
    • Re: define a struct that has its own type as a field somehow?, Keith Thompson
      • Re: define a struct that has its own type as a field somehow?, Mark McIntyre
      • Re: define a struct that has its own type as a field somehow?, SM Ryan
      • Re: define a struct that has its own type as a field somehow?, Christopher Benson-Manica
  • Re: define a struct that has its own type as a field somehow?, SM Ryan
• K&R2 variable definition, Clausfor
  • Re: K&R2 variable definition, Zara
    • Re: K&R2 variable definition, Clausfor
  • Re: K&R2 variable definition, Richard Tobin
  • Re: K&R2 variable definition, Chris Dollin
  • Re: K&R2 variable definition, Richard Heathfield
• string manipulation, avida
  • Re: string manipulation, mark_bluemel
    • Re: string manipulation, avida
      • Re: string manipulation, mark_bluemel
      • Re: string manipulation, Malcolm
  • Re: string manipulation, Martin Ambuhl
  • Re: string manipulation, Mark McIntyre
• about Database in C, raghu
  • Re: about Database in C, Ico
    • Re: about Database in C, thunder1
  • Re: about Database in C, mark_bluemel
  • Re: about Database in C, dcorbit
• gdb: breakpoint condition to compare string, Pawel
  • Re: gdb: breakpoint condition to compare string, Ian Collins
• How to test for the existence of __func__?, dave_140390
  • Re: How to test for the existence of __func__?, Ian Collins
    • Re: How to test for the existence of __func__?, Richard Bos
    • Re: How to test for the existence of __func__?, dave_140390
  • Re: How to test for the existence of __func__?, Hallvard B Furuseth
  • Re: How to test for the existence of __func__?, Rod Pemberton
    • Re: How to test for the existence of __func__?, Greg Comeau
  • Re: How to test for the existence of __func__?, Old Wolf
    • Re: How to test for the existence of __func__?, Keith Thompson
  • Re: How to test for the existence of __func__?, Ancient_Hacker
• New to Programming, SG
  • Re: New to Programming, Glenn Hutchings
  • Re: New to Programming, J. J. Farrell
    • Re: New to Programming, Richard
      • Re: New to Programming, Richard Heathfield
      • Re: New to Programming, Jordan Abel
      • Re: New to Programming, Spiros Bousbouras
      • Re: New to Programming, J. J. Farrell
      • Re: New to Programming, Ian Collins
      • Re: New to Programming, Lowell Gilbert
      • Re: New to Programming, arnuld
  • Re: New to Programming, Richard Heathfield
  • Re: New to Programming, Hallvard B Furuseth
  • Re: New to Programming, CBFalconer
    • Re: New to Programming, Charlton Wilbur
  • Re: New to Programming, Spiros Bousbouras
  • Re: New to Programming, Ancient_Hacker
    • Re: New to Programming, Richard Heathfield
      • Re: New to Programming, Keith Thompson
      • Re: New to Programming, Joe Wright
      • Re: New to Programming, arnuld
      • Re: New to Programming, arnuld
      • [OT] Re: New to Programming, Flash Gordon
      • Re: [OT] Re: New to Programming, CBFalconer
      • Re: [OT] Re: New to Programming, Gordon Burditt
      • Re: New to Programming, Richard Heathfield
      • Re: New to Programming, Keith Thompson
      • Re: New to Programming, Richard Heathfield
  • Re: New to Programming, Malcolm
  • Re: New to Programming, arnuld
• A simple program , need to see where's the mistake :), Odinn
  • Re: A simple program , need to see where's the mistake :), michael . kirby
  • Re: A simple program , need to see where's the mistake :), Christopher Benson-Manica
    • Re: A simple program , need to see where's the mistake :), Odinn
  • Re: A simple program , need to see where's the mistake :), Andrew Poelstra
  • Re: A simple program , need to see where's the mistake :), CBFalconer
    • Re: A simple program , need to see where's the mistake :), fermineutron
      • Re: A simple program , need to see where's the mistake :), Barry Schwarz
      • Re: A simple program , need to see where's the mistake :), Richard Heathfield
    • Re: A simple program , need to see where's the mistake :), Fred Kleinschmidt
      • Re: A simple program , need to see where's the mistake :), CBFalconer
      • Re: A simple program , need to see where's the mistake :), Keith Thompson
  • Re: A simple program , need to see where's the mistake :), Andrew Poelstra
    • Re: A simple program , need to see where's the mistake :), Christopher Benson-Manica
      • Re: A simple program , need to see where's the mistake :), Andrew Poelstra
• bit position, Serve Laurijssen
  • Re: bit position, Richard Heathfield
  • Re: bit position, Giorgio Silvestri
  • Re: bit position, Serve Laurijssen
    • Re: bit position, Eric Sosman
      • Re: bit position, Eric Sosman
    • Re: bit position, Simon Biber
  • Re: bit position, Nishu
  • Re: bit position, Ico
  • Re: bit position, Hallvard B Furuseth
    • Re: bit position, Keith Thompson
      • Re: bit position, Hallvard B Furuseth
• Stack and Queue, raghu
  • Re: Stack and Queue, Richard Heathfield
  • Re: Stack and Queue, michael . kirby
  • Re: Stack and Queue, Malcolm
    • Re: Stack and Queue, CBFalconer
• how to fabricate a good computer, lasaihome
  • Re: how to fabricate a good computer, Richard Heathfield
  • Re: how to fabricate a good computer, jmcgill
    • Re: how to fabricate a good computer, Rod Pemberton
  • Re: how to fabricate a good computer, CBFalconer
  • Re: how to fabricate a good computer, Richard Bos
  • Re: how to fabricate a good computer, Rod Pemberton
    • Re: how to fabricate a good computer, Clever Monkey
• fclose then fopen equivalent for stdout?, David Mathog
  • Re: fclose then fopen equivalent for stdout?, David Mathog
  • Re: fclose then fopen equivalent for stdout?, Eric Sosman
    • Re: fclose then fopen equivalent for stdout?, David Mathog
      • Re: fclose then fopen equivalent for stdout?, Christopher Benson-Manica
      • Re: fclose then fopen equivalent for stdout?, David Mathog
      • Re: fclose then fopen equivalent for stdout?, Jordan Abel
      • Re: fclose then fopen equivalent for stdout?, David Mathog
      • Re: fclose then fopen equivalent for stdout?, Eric Sosman
      • Re: fclose then fopen equivalent for stdout?, CBFalconer
      • Re: fclose then fopen equivalent for stdout?, Rod Pemberton
    • Re: fclose then fopen equivalent for stdout?, Harald van Dijk
      • Re: fclose then fopen equivalent for stdout?, David Mathog
      • Re: fclose then fopen equivalent for stdout?, Eric Sosman
  • Re: fclose then fopen equivalent for stdout?, Chris Torek
  • Re: fclose then fopen equivalent for stdout?, Serve Laurijssen
    • Re: fclose then fopen equivalent for stdout?, David Mathog
      • Re: fclose then fopen equivalent for stdout?, Keith Thompson
      • Re: fclose then fopen equivalent for stdout?, Jordan Abel
    • Re: fclose then fopen equivalent for stdout?, Walter Roberson
      • Re: fclose then fopen equivalent for stdout?, CBFalconer
• C code to calculate gradient of a function, Olw
  • Re: C code to calculate gradient of a function, Clever Monkey
    • Re: C code to calculate gradient of a function, Olw
      • Re: C code to calculate gradient of a function, Fred Kleinschmidt
      • Re: C code to calculate gradient of a function, Mark McIntyre
      • Re: C code to calculate gradient of a function, William Hughes
      • Re: C code to calculate gradient of a function, Olw
  • Re: C code to calculate gradient of a function, Fred Kleinschmidt
  • Re: C code to calculate gradient of a function, CBFalconer
  • Re: C code to calculate gradient of a function, Bill Pursell
  • Re: C code to calculate gradient of a function, dcorbit
  • Re: C code to calculate gradient of a function, xhunga
  • Re: C code to calculate gradient of a function, Olw
  • Re: C code to calculate gradient of a function, David Wade
    • Re: C code to calculate gradient of a function, Olw
• getchar, CDROOM
  • Re: getchar, mark_bluemel
  • Re: getchar, jmcgill
    • Re: getchar, CDROOM
    • Re: getchar, CDROOM
  • Re: getchar, Baishampayan Ghose
• Another Mersenne Twister question, Simon
  • Re: Another Mersenne Twister question, mark_bluemel
  • Re: Another Mersenne Twister question, Arthur J. O'Dwyer
    • Re: Another Mersenne Twister question, Simon
    • Re: Another Mersenne Twister question, Keith Thompson
      • Re: Another Mersenne Twister question, Jack Klein
      • Re: Another Mersenne Twister question, fermineutron
  • Re: Another Mersenne Twister question, websnarf
    • Re: Another Mersenne Twister question, Keith Thompson
  • Re: Another Mersenne Twister question, CBFalconer
    • Re: Another Mersenne Twister question, Keith Thompson
• Printing bitmap on HP Printer, Yann KERNIN
  • Re: Printing bitmap on HP Printer, Christopher Benson-Manica
  • Re: Printing bitmap on HP Printer, Tom St Denis
    • Re: Printing bitmap on HP Printer, Keith Thompson
• Source code reverse engineering with graphviz output., bradphelan
  • Re: Source code reverse engineering with graphviz output., bradphelan
• EOF Question, jobo
  • Re: EOF Question, Simon Biber
    • Re: EOF Question, Simon Biber
  • Re: EOF Question, Andrew Poelstra
• Detecting EOF, jobo
  • Re: Detecting EOF, Papastefanos Serafeim
  • Re: Detecting EOF, Andrew Poelstra
    • Re: Detecting EOF, Richard Heathfield
  • <Possible follow-ups>
  • Detecting EOF, jobo
• File handling with structures problem, Rav
  • Re: File handling with structures problem, "Nils O. Selåsdal"
  • Re: File handling with structures problem, Jack Klein
• Strange Behaviour of this function, g.ankush1@xxxxxxxxx
  • Re: Strange Behaviour of this function, "Nils O. Selåsdal"
  • Re: Strange Behaviour of this function, Keith Thompson
    • Re: Strange Behaviour of this function, Peter Nilsson
      • Re: Strange Behaviour of this function, Keith Thompson
      • Things you aren't allowed to say (Was: Strange Behaviour of this function), Kenny McCormack
      • Re: Strange Behaviour of this function, Peter Nilsson
      • Re: Strange Behaviour of this function, Keith Thompson
  • Re: Strange Behaviour of this function, Andrew Poelstra
    • Re: Strange Behaviour of this function, Keith Thompson
      • Re: Strange Behaviour of this function, Andrew Poelstra
      • Re: Strange Behaviour of this function, Keith Thompson
      • Re: Strange Behaviour of this function, CBFalconer
      • Re: Strange Behaviour of this function, Dik T. Winter
      • Re: Strange Behaviour of this function, Keith Thompson
  • Re: Strange Behaviour of this function, raghu
    • Re: Strange Behaviour of this function, Richard Heathfield
    • Re: Strange Behaviour of this function, mark_bluemel
    • Re: Strange Behaviour of this function, Keith Thompson
      • Re: Strange Behaviour of this function, raghu
      • Re: Strange Behaviour of this function, Chris Dollin
      • Re: Strange Behaviour of this function, Richard Tobin
      • Re: Strange Behaviour of this function, Chris Dollin
• Behavior of logical or, michaelp
  • Re: Behavior of logical or, Conor Hughes
    • Re: Behavior of logical or, michaelp
  • Re: Behavior of logical or, "Nils O. Selåsdal"
    • Re: Behavior of logical or, michaelp
      • Re: Behavior of logical or, Keith Thompson
  • Re: Behavior of logical or, Keith Thompson
    • Re: Behavior of logical or, michaelp
  • Re: Behavior of logical or, Rachael
  • Re: Behavior of logical or, Lew Pitcher
  • Re: Behavior of logical or, Kenneth Brody
• Finding the Integers Question, jobo
  • Re: Finding the Integers Question, T.M. Sommers
    • Re: Finding the Integers Question, jobo
      • Re: Finding the Integers Question, T.M. Sommers
      • Re: Finding the Integers Question, Keith Thompson
      • Re: Finding the Integers Question, hookah_frog
      • Re: Finding the Integers Question, Ben Bacarisse
      • Re: Finding the Integers Question, Simon Biber
      • Re: Finding the Integers Question, Richard Heathfield
      • Re: Finding the Integers Question, CBFalconer
      • Re: Finding the Integers Question, Andrew Poelstra
      • Re: Finding the Integers Question, Default User
      • Re: Finding the Integers Question, Andrew Poelstra
      • Re: Finding the Integers Question, hookah_frog
      • Re: Finding the Integers Question, Richard Heathfield
      • Re: Finding the Integers Question, CBFalconer
      • Re: Finding the Integers Question, Keith Thompson
  • Re: Finding the Integers Question, Robert Latest
    • Re: Finding the Integers Question, Richard Heathfield
      • Re: Finding the Integers Question, Robert Latest
      • Re: Finding the Integers Question, Richard Heathfield
      • Re: Finding the Integers Question, Andrew Poelstra
  • Re: Finding the Integers Question, Simon Biber
• ( ) -> operators associativity confused, bochengnever
  • Re: ( ) -> operators associativity confused, Eric Sosman
  • Re: ( ) -> operators associativity confused, Andrey Tarasevich
• C in Linux vs C in Windows, is there any difference?, VijaKhara
  • Re: C in Linux vs C in Windows, is there any difference?, Dr_Locke_Z2A
  • Re: C in Linux vs C in Windows, is there any difference?, Walter Roberson
  • Re: C in Linux vs C in Windows, is there any difference?, Ben Bacarisse
  • Re: C in Linux vs C in Windows, is there any difference?, CBFalconer
  • Re: C in Linux vs C in Windows, is there any difference?, Robert Latest
    • Re: C in Linux vs C in Windows, is there any difference?, Walter Roberson
  • Re: C in Linux vs C in Windows, is there any difference?, David Wade
• C compiler and editor, marco . delvecchio
  • Re: C compiler and editor, Mitsteig
  • Re: C compiler and editor, Simon Biber
  • Re: C compiler and editor, Tom St Denis
  • Re: C compiler and editor, Christopher Benson-Manica
    • Re: C compiler and editor, CBFalconer
  • Re: C compiler and editor, jussij
• unsigned char, FlyingBird
  • Re: unsigned char, Clark S. Cox III
    • Re: unsigned char, Peter Nilsson
      • Re: unsigned char, CBFalconer
  • Re: unsigned char, Bill Medland
    • Re: unsigned char, Eric Sosman
      • Re: unsigned char, Bill Medland
      • Re: unsigned char, Eric Sosman
    • Re: unsigned char, Clark S. Cox III
  • Re: unsigned char, cassius
  • Re: unsigned char, Frederick Gotham
  • Re: unsigned char, Jack Klein
    • Re: unsigned char, CBFalconer
      • Re: unsigned char, Harald van Dijk
• general array in C, Cyn
  • Re: general array in C, jacob navia
  • Re: general array in C, Ancient_Hacker
    • Re: general array in C, jacob navia
      • Re: general array in C, Ancient_Hacker
      • Re: general array in C, Bart
    • Re: general array in C, Frederick Gotham
      • Re: general array in C, Ancient_Hacker
      • Re: general array in C, Frederick Gotham
  • Re: general array in C, pete
    • Re: general array in C, Simon Biber
      • Re: general array in C, Cyn
      • Re: general array in C, Laurent Deniau
    • Re: general array in C, jacob navia
  • Re: general array in C, Bart
  • Re: general array in C, Laurent Deniau
    • Re: general array in C, Keith Thompson
      • Re: general array in C, Laurent Deniau
      • Re: general array in C, Keith Thompson
  • Re: general array in C, Michal Nazarewicz
    • Re: general array in C, Laurent Deniau
• how to allocate memory to a member at run time, raghu
  • Re: how to allocate memory to a member at run time, mark_bluemel
  • Re: how to allocate memory to a member at run time, thunder1
    • Re: how to allocate memory to a member at run time, Christopher Benson-Manica
    • Re: how to allocate memory to a member at run time, Andrew Poelstra
      • Re: how to allocate memory to a member at run time, CBFalconer
• how to allocate memory to a member dynamically, raghu
  • Re: how to allocate memory to a member dynamically, Jens Thoms Toerring
    • Re: how to allocate memory to a member dynamically, raghu
      • Re: how to allocate memory to a member dynamically, Christopher Benson-Manica
      • Re: how to allocate memory to a member dynamically, mark_bluemel
      • Re: how to allocate memory to a member dynamically, CBFalconer
  • Re: how to allocate memory to a member dynamically, mark_bluemel
    • Re: how to allocate memory to a member dynamically, mark_bluemel
  • Re: how to allocate memory to a member dynamically, Ancient_Hacker
    • Re: how to allocate memory to a member dynamically, Andrew Poelstra
      • Re: how to allocate memory to a member dynamically, Richard Bos
  • Re: how to allocate memory to a member dynamically, Ancient_Hacker
    • Re: how to allocate memory to a member dynamically, Michal Nazarewicz
      • Re: how to allocate memory to a member dynamically, Ancient_Hacker
  • Re: how to allocate memory to a member dynamically, Andrew Poelstra
• How to reverse a Unsigned Char??, ranjanmg1
  • Re: How to reverse a Unsigned Char??, mark_bluemel
  • Re: How to reverse a Unsigned Char??, Jens Thoms Toerring
  • Re: How to reverse a Unsigned Char??, Jordan Abel
  • Re: How to reverse a Unsigned Char??, pete
• block in open(), freegnu
  • Re: block in open(), Nick Keighley
  • Re: block in open(), Jens Thoms Toerring
  • Re: block in open(), CBFalconer
    • Re: block in open(), Jordan Abel
      • Re: block in open(), CBFalconer
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Richard Bos
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Keith Thompson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Richard Bos
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Richard Bos
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Stephen Sprunk
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), CBFalconer
      • Re: block in open(), CBFalconer
      • Re: block in open(), riedel
      • Re: block in open(), Jordan Abel
      • Re: block in open(), CBFalconer
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
      • Re: block in open(), Mark McIntyre
      • Re: block in open(), Walter Roberson
      • Re: block in open(), Jordan Abel
• C standard, xdevel
  • Re: C standard, jmcgill
    • Re: C standard, xdevel
      • Re: C standard, Mark McIntyre
  • Re: C standard, Elijah Cardon
• is it possible to run a C program from batch file., sjayaramit
  • Re: is it possible to run a C program from batch file., Cinder6
  • Re: is it possible to run a C program from batch file., pankaj
  • Re: is it possible to run a C program from batch file., Mark McIntyre
    • Re: is it possible to run a C program from batch file., pete
  • Re: is it possible to run a C program from batch file., Simon Biber
• c PROGRAMMERS--READ THIS AND THINK ABOUT YOURSELF, Google Questions
• Doubts on Array Size, Harry
  • Re: Doubts on Array Size, J. J. Farrell
  • Re: Doubts on Array Size, mark_bluemel
• initializer element is not constant, Paul Edwards
  • Re: initializer element is not constant, Paul Edwards
    • Re: initializer element is not constant, Jack Klein
      • Re: initializer element is not constant, Paul Edwards
      • Re: initializer element is not constant, pete
      • Re: initializer element is not constant, Keith Thompson
      • Re: initializer element is not constant, Paul Edwards
  • Re: initializer element is not constant, Jack Klein
• Highest Common Factor, Frederick Gotham
  • Re: Highest Common Factor, nachch
    • Re: Highest Common Factor, gw7rib
  • Re: Highest Common Factor, bert
  • Re: Highest Common Factor, Julian V. Noble
  • Re: Highest Common Factor, Afghan Hound
  • Re: Highest Common Factor, Elijah Cardon
    • Re: Highest Common Factor, mensanator@xxxxxxx
      • Re: Highest Common Factor, Elijah Cardon
  • Message not available
    • Re: Highest Common Factor, Harald van Dijk
• Evaluation order of assignment statement, nachch
  • Re: Evaluation order of assignment statement, John Smith
  • Re: Evaluation order of assignment statement, Walter Roberson
  • Re: Evaluation order of assignment statement, Andrey Tarasevich
    • Re: Evaluation order of assignment statement, nachch
      • Re: Evaluation order of assignment statement, Walter Roberson
      • Re: Evaluation order of assignment statement, nachch
      • Re: Evaluation order of assignment statement, robertwessel2@xxxxxxxxx
      • Re: Evaluation order of assignment statement, Walter Roberson
      • Re: Evaluation order of assignment statement, Chris Torek
      • Re: Evaluation order of assignment statement, Walter Roberson
• memcpy() problem, danu
  • Re: memcpy() problem, Walter Roberson
    • Re: memcpy() problem, danu
      • Re: memcpy() problem, Walter Roberson
      • Re: memcpy() problem, J. J. Farrell
      • Re: memcpy() problem, J. J. Farrell
  • Re: memcpy() problem, Bill Medland
  • <Possible follow-ups>
  • memcpy() problem, danu
• address after end of array?, Serve Laurijssen
  • Re: address after end of array?, Richard Heathfield
    • Re: address after end of array?, Frederick Gotham
      • Re: address after end of array?, "Nils O. Selåsdal"
      • Re: address after end of array?, Harald van Dijk
  • Re: address after end of array?, Jean-Marc Bourguet
• realloc but not copy, ivan . leben
  • Re: realloc but not copy, Richard Heathfield
  • Re: realloc but not copy, Al Balmer
  • Re: realloc but not copy, websnarf
    • Re: realloc but not copy, CBFalconer
      • Re: realloc but not copy, James Antill
      • Re: realloc but not copy, CBFalconer
  • Re: realloc but not copy, Miquel van Smoorenburg
  • Re: realloc but not copy, robertwessel2@xxxxxxxxx
  • Re: realloc but not copy, Eric Sosman
    • Re: realloc but not copy, robertwessel2@xxxxxxxxx
      • Re: realloc but not copy, Eric Sosman
      • Re: realloc but not copy, Scott Fluhrer
      • Re: realloc but not copy, Al Balmer
  • LOW INTELLIGENCE ALERT, Frederick Gotham
    • Re: LOW INTELLIGENCE ALERT, Scott Fluhrer
      • Re: LOW INTELLIGENCE ALERT, Frederick Gotham
      • Re: LOW INTELLIGENCE ALERT, Robert Latest
  • Re: realloc but not copy, Frederick Gotham
    • Re: realloc but not copy, websnarf
• verify float number, Xancatal
  • Re: verify float number, Bill Medland
    • Re: verify float number, Xancatal
      • Re: verify float number, Bill Medland
      • Re: verify float number, Xancatal
      • Re: verify float number, Bill Medland
      • Re: verify float number, Bill Medland
      • Re: verify float number, Xancatal
      • Re: verify float number, Bill Medland
      • Re: verify float number, Keith Thompson
      • Re: verify float number, Xancatal
      • Re: verify float number, Ian Collins
      • Re: verify float number, Xancatal
      • Re: verify float number, Richard Heathfield
      • Re: verify float number, CBFalconer
      • Re: verify float number, Richard Tobin
      • Re: verify float number, J. J. Farrell
      • Re: verify float number, Chris Torek
  • Re: verify float number, CBFalconer
    • Re: verify float number, Xancatal
      • Re: verify float number, Fred Kleinschmidt
      • Re: verify float number, Xancatal
      • Re: verify float number, Nick Keighley
      • Re: verify float number, Xancatal
      • Re: verify float number, Bill Medland
      • Re: verify float number, Xancatal
      • Re: verify float number, Ben Pfaff
      • Re: verify float number, Bill Medland
      • Re: verify float number, CBFalconer
      • Re: verify float number, Bill Medland
      • Re: verify float number, jmcgill
  • Re: verify float number, Neil
    • Re: verify float number, Xancatal
      • Re: verify float number, Keith Thompson
  • Re: verify float number, av
    • Re: verify float number, Nick Keighley
  • Re: verify float number, John Bode
• POSIX system() call return value, jensthiede
  • Re: POSIX system() call return value, Igmar Palsenberg
    • Re: POSIX system() call return value, jensthiede
    • Re: POSIX system() call return value, Kenneth Brody
  • Re: POSIX system() call return value, Keith Thompson
• Please help me spot the difference, Andreas Vinther
  • Re: Please help me spot the difference, Christian MOENNE-LOCCOZ
  • Re: Please help me spot the difference, Ico
  • Re: Please help me spot the difference, Papastefanos Serafeim
    • Re: Please help me spot the difference, Richard Bos
    • Re: Please help me spot the difference, Andrew Poelstra
  • Re: Please help me spot the difference, Jens Thoms Toerring
    • Re: Please help me spot the difference, Andreas
      • Re: Please help me spot the difference, Jens Thoms Toerring
• grammar files for a shell, junky_fellow@xxxxxxxxxxx
  • Re: grammar files for a shell, Mark McIntyre
  • Re: grammar files for a shell, Rod Pemberton
    • Re: grammar files for a shell, junky_fellow@xxxxxxxxxxx
      • Re: grammar files for a shell, Rod Pemberton
• Endian revisited, Sheldon
  • Re: Endian revisited, Robert Latest
    • Re: Endian revisited, CBFalconer
      • Re: Endian revisited, Robert Latest
      • Re: Endian revisited, Bill Medland
    • Re: Endian revisited, Sheldon
  • Re: Endian revisited, Bill Medland
    • Re: Endian revisited, Sheldon
  • Re: Endian revisited, Thad Smith
  • Re: Endian revisited, Nick Keighley
• Re: is the compiler displaying logical or linear address value?, "Nils O. Selåsdal"
• help with linklist with I/O file, and word node, spidey12345
  • Re: help with linklist with I/O file, and word node, Ben Bacarisse
  • Re: help with linklist with I/O file, and word node, Simon Biber
    • Re: help with linklist with I/O file, and word node, spidey12345
      • Re: help with linklist with I/O file, and word node, Keith Thompson
      • Re: help with linklist with I/O file, and word node, Simon Biber
      • Re: help with linklist with I/O file, and word node, spidey12345
      • Re: help with linklist with I/O file, and word node, Bill Pursell
• Please help me overcome the segmentation fault, Rav
  • Re: Please help me overcome the segmentation fault, Ancient_Hacker
  • Re: Please help me overcome the segmentation fault, Ancient_Hacker
  • Re: Please help me overcome the segmentation fault, Eric Sosman
  • Re: Please help me overcome the segmentation fault, Barry Schwarz
  • Re: Please help me overcome the segmentation fault, Thad Smith
    • Re: Please help me overcome the segmentation fault, CBFalconer
      • Re: Please help me overcome the segmentation fault, Richard Heathfield
      • Re: Please help me overcome the segmentation fault, CBFalconer
      • Re: Please help me overcome the segmentation fault, Richard Heathfield
      • Re: Please help me overcome the segmentation fault, Simon Biber
• c & time problem, RVO
  • Re: c & time problem, Ian Collins
    • Re: c & time problem, RVO
      • Re: c & time problem, Ian Collins
      • Re: c & time problem, Ian Collins
      • Re: c & time problem, RVO
      • Re: c & time problem, CBFalconer
      • Re: c & time problem, Andrew Poelstra
      • Re: c & time problem, RVO