comp.lang.c

• Thread Index

---

• Re: What's The Best Practice Defining Error Codes in C
  • From: Ben Bacarisse
• Re: What's The Best Practice Defining Error Codes in C
  • From: rammy
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: Nobody
• Re: parse bib file in C
  • From: Ben Bacarisse
• Re: parse bib file in C
  • From: Barry Schwarz
• Re: parse bib file in C
  • From: Rudra Banerjee
• Re: parse bib file in C
  • From: Jorgen Grahn
• Re: parse bib file in C
  • From: Ben Bacarisse
• Re: What's The Best Practice Defining Error Codes in C
  • From: Malcolm McLean
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: Kenny McCormack
• Re: Variable-length arrays: should they be used at all?
  • From: Malcolm McLean
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: Malcolm McLean
• Re: Variable-length arrays: should they be used at all?
  • From: Ian Collins
• Re: parse bib file in C
  • From: Rudra Banerjee
• Re: parse bib file in C
  • From: none
• Re: parse bib file in C
  • From: Rudra Banerjee
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: jacob navia
• Re: parse bib file in C
  • From: Rudra Banerjee
• Re: parse bib file in C
  • From: Rudra Banerjee
• Re: parse bib file in C
  • From: Barry Schwarz
• parse bib file in C
  • From: Rudra Banerjee
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: Aaron W . Hsu
• Re: There is still a great need for a "C GUI Designer/Builder".
  • From: Les Cargill
• Re: typedef struct
  • From: Keith Thompson
• Re: typedef struct
  • From: Robert Miles
• There is still a great need for a "C GUI Designer/Builder".
  • From: vmars316
• Re: What's The Best Practice Defining Error Codes in C
  • From: Eric Sosman
• Re What's The Best Practice Defining Error Codes in C
  • From: Sergi Pasoev
• Re: What's The Best Practice Defining Error Codes in C
  • From: Keith Thompson
• Re: What's The Best Practice Defining Error Codes in C
  • From: rammy
• What's The Best Practice Defining Error Codes in C
  • From: rammy
• Re: Converting from UTC to "local" time
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: intToStr
  • From: Fred K
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: intToStr
  • From: Keith Thompson
• Re: Converting from UTC to "local" time
  • From: Gordon Burditt
• Re: Function casting - UB?
  • From: Tim Rentsch
• Re: Function casting - UB?
  • From: Tim Rentsch
• Re: Variable-length arrays: should they be used at all?
  • From: Tim Rentsch
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Converting from UTC to "local" time
  • From: Gordon Burditt
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: unsigned abs(int)?
  • From: Tim Rentsch
• Re: unsigned abs(int)?
  • From: Ben Bacarisse
• Re: Converting from UTC to "local" time
  • From: Gordon Burditt
• Re: intToStr
  • From: Malcolm McLean
• Re: intToStr
  • From: Mark Bluemel
• Re: intToStr
  • From: Heinrich Wolf
• Re: intToStr
  • From: Andrej Viktorovich
• Re: intToStr
  • From: Heinrich Wolf
• Learning C by Reading
  • From: Sergi Pasoev
• Re: intToStr
  • From: James Kuyper
• Re: intToStr
  • From: Heinrich Wolf
• Re: intToStr
  • From: Kenny McCormack
• Re: intToStr
  • From: pete
• Re: intToStr
  • From: Andrej Viktorovich
• Re: intToStr
  • From: Mark Bluemel
• intToStr
  • From: Andrej Viktorovich
• Re: va_list + function pointers
  • From: Lurkos
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: va_list + function pointers
  • From: Eric Sosman
• Re: va_list + function pointers
  • From: Lurkos
• Re: Learning C by reading
  • From: none
• Re: Learning C by reading
  • From: Rui Maciel
• Re: Learning C by reading
  • From: James Kuyper
• Re: A question for this group...
  • From: Andrew Cooper
• Re: Learning C by reading
  • From: Andrew Cooper
• Re: c for web development: well does anyone do it and save 1000's of megs ram?
  • From: Malcolm McLean
• Re: c for web development: well does anyone do it and save 1000's of megs ram?
  • From: Fred K
• Re: C scope and struct definitions
  • From: Kenneth Brody
• c for web development: well does anyone do it and save 1000's of megs ram?
  • From: quiet_lad
• Re: A question for this group...
  • From: Malcolm McLean
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: Learning C by reading
  • From: Aaron W . Hsu
• Re: va_list + function pointers
  • From: James Kuyper
• Re: va_list + function pointers
  • From: Ben Pfaff
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: va_list + function pointers
  • From: Ben Bacarisse
• Re: va_list + function pointers
  • From: James Kuyper
• Re: va_list + function pointers
  • From: Ben Pfaff
• va_list + function pointers
  • From: Lurkos
• Re: va_list e function pointer
  • From: Lurkos
• va_list e function pointer
  • From: Lurkos
• va_list + function pointers
  • From: Lurkos
• Re: A question for this group...
  • From: io_x
• Re: Function casting - UB?
  • From: io_x
• Re: Learning C by reading
  • From: Johann Klammer
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: A question for this group...
  • From: James Kuyper
• Re: A question for this group...
  • From: James Kuyper
• Re: A question for this group...
  • From: Heikki Kallasjoki
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Learning C as an existing programmer
  • From: Malcolm McLean
• Re: A question for this group...
  • From: Malcolm McLean
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Learning C by reading
  • From: James Kuyper
• Re: Learning C as an existing programmer
  • From: io_x
• Learning C by reading
  • From: Sergi Pasoev
• Re: Function casting - UB?
  • From: Jens Gustedt
• Re: Learning C as an existing programmer
  • From: nick_keighley_nospam
• Re: A question for this group...
  • From: nick_keighley_nospam
• Re: Function casting - UB?
  • From: Johannes Bauer
• Re: Function casting - UB?
  • From: Johannes Bauer
• Re: A question for this group...
  • From: io_x
• Re: Learning C as an existing programmer
  • From: io_x
• Re: Variable-length arrays: should they be used at all?
  • From: Ian Collins
• Re: Function casting - UB?
  • From: Tim Rentsch
• Re: Variable-length arrays: should they be used at all?
  • From: Tim Rentsch
• Re: Static size array arguments
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: Function casting - UB?
  • From: christian.bau
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: Variable-length arrays: should they be used at all?
  • From: Ian Collins
• Re: Static size array arguments
  • From: Andrew Cooper
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Variable-length arrays: should they be used at all?
  • From: Rui Maciel
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: Variable-length arrays: should they be used at all?
  • From: Ben Bacarisse
• Re: Variable-length arrays: should they be used at all?
  • From: jacob navia
• Re: Function casting - UB?
  • From: James Kuyper
• Re: Variable-length arrays: should they be used at all?
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Kenneth Brody
• Re: Function casting - UB?
  • From: Les Cargill
• Re: Function casting - UB?
  • From: Les Cargill
• Re: Function casting - UB?
  • From: Heikki Kallasjoki
• Re: Function casting - UB?
  • From: Tim Rentsch
• Re: how to use volatile key word?
  • From: Tim Rentsch
• Re: Static size array arguments
  • From: Tim Rentsch
• Re: Function casting - UB?
  • From: Eric Sosman
• Function casting - UB?
  • From: nroberts
• Re: Converting from UTC to "local" time
  • From: Heinrich Wolf
• Re: Variable-length arrays: should they be used at all?
  • From: Eric Sosman
• Re: A question for this group...
  • From: Neil Cerutti
• Re: Variable-length arrays: should they be used at all?
  • From: Ben Bacarisse
• Re: Converting from UTC to "local" time
  • From: nick_keighley_nospam
• Re: A question for this group...
  • From: nick_keighley_nospam
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: Learning C as an existing programmer
  • From: James Kuyper
• Re: A question for this group...
  • From: Kenny McCormack
• Re: Converting from UTC to "local" time
  • From: nick_keighley_nospam
• Re: Variable-length arrays: should they be used at all?
  • From: gwowen
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: Variable-length arrays: should they be used at all?
  • From: Gareth Owen
• Re: C scope and struct definitions
  • From: Jens Gustedt
• Re: Variable-length arrays: should they be used at all?
  • From: Gareth Owen
• Re: Learning C as an existing programmer
  • From: Gareth Owen
• Re: Variable-length arrays: should they be used at all?
  • From: jacob navia
• Re: Variable-length arrays: should they be used at all?
  • From: Ian Collins
• Re: Variable-length arrays: should they be used at all?
  • From: jacob navia
• Re: Learning C as an existing programmer
  • From: Ben Bacarisse
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: Variable-length arrays: should they be used at all?
  • From: Malcolm McLean
• Re: uninitialised value & valgrind
  • From: Johann Klammer
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: Converting from UTC to "local" time
  • From: Gordon Burditt
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: C scope and struct definitions
  • From: Jens Gustedt
• Re: Variable-length arrays: should they be used at all?
  • From: David Resnick
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Nobody
• Re: Variable-length arrays: should they be used at all?
  • From: Keith Thompson
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: Variable-length arrays: should they be used at all?
  • From: Keith Thompson
• Re: Variable-length arrays: should they be used at all?
  • From: Rui Maciel
• Re: Variable-length arrays: should they be used at all?
  • From: Rui Maciel
• Re: uninitialised value & valgrind
  • From: James Kuyper
• Re: Bitwise Not Operator
  • From: James Kuyper
• Re: Variable-length arrays: should they be used at all?
  • From: Jens Gustedt
• Re: how to use volatile key word?
  • From: Jens Gustedt
• Re: Variable-length arrays: should they be used at all?
  • From: jacob navia
• Re: Bitwise Not Operator
  • From: Jens Gustedt
• Re: Bitwise Not Operator
  • From: aleksa
• Re: uninitialised value & valgrind
  • From: Mark
• Re: uninitialised value & valgrind
  • From: James Kuyper
• Re: Bitwise Not Operator
  • From: Les Cargill
• Re: Bitwise Not Operator
  • From: Ike Naar
• Re: how to use volatile key word?
  • From: Eric Sosman
• Re: how to use volatile key word?
  • From: Xavier Roche
• uninitialised value & valgrind
  • From: Mark
• how to use volatile key word?
  • From: 伏虎
• Re: bitfields
  • From: Jorgen Grahn
• Re: Variable-length arrays: should they be used at all?
  • From: Eric Sosman
• Bitwise Not Operator
  • From: aleksa
• Re: Will 'free' return the memory Immediately to the OS ?
  • From: Stephen Sprunk
• Re: A question for this group...
  • From: nick_keighley_nospam
• Variable-length arrays: should they be used at all?
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: bitfields
  • From: David Brown
• Re: Static size array arguments
  • From: Ben Bacarisse
• Re: assianing value of pointer
  • From: Tim Rentsch
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: bitfields
  • From: nick_keighley_nospam
• Re: bitfields
  • From: nick_keighley_nospam
• Re: Static size array arguments
  • From: Jens Gustedt
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: Static size array arguments
  • From: Ben Bacarisse
• Re: fread/fwrite 2
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: C scope and struct definitions
  • From: Jens Gustedt
• Re: Static size array arguments
  • From: jacob navia
• Static size array arguments
  • From: Guillaume Dargaud
• Re: bitfields
  • From: Malcolm McLean
• Re: Learning C as an existing programmer
  • From: Ian Collins
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: nick_keighley_nospam
• Re: bitfields
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: James Kuyper
• Re: Infinite arrays in the CCL
  • From: gwowen
• Re: Learning C as an existing programmer
  • From: jacob navia
• Re: Learning C as an existing programmer
  • From: jacob navia
• Re: Learning C as an existing programmer
  • From: gwowen
• Re: Learning C as an existing programmer
  • From: gwowen
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: bitfields
  • From: David Brown
• Re: Learning C as an existing programmer
  • From: Ike Naar
• Re: Learning C as an existing programmer
  • From: Robert Wessel
• Re: bitfields
  • From: Ian Collins
• Re: fread/fwrite 2
  • From: nick_keighley_nospam
• Re: bitfields
  • From: nick_keighley_nospam
• Re: bitfields
  • From: nick_keighley_nospam
• Re: string
  • From: nick_keighley_nospam
• Re: Learning C as an existing programmer
  • From: Keith Thompson
• Re: Learning C as an existing programmer
  • From: nick_keighley_nospam
• Re: Learning C as an existing programmer
  • From: Malcolm McLean
• Re: Learning C as an existing programmer
  • From: nick_keighley_nospam
• Re: Learning C as an existing programmer
  • From: nick_keighley_nospam
• Re: Learning C as an existing programmer
  • From: J. J. Farrell
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Owen Jacobson
• Re: assianing value of pointer
  • From: Keith Thompson
• Re: string
  • From: James Kuyper
• Re: assianing value of pointer
  • From: James Kuyper
• Re: string
  • From: Keith Thompson
• Re: Microsoft User Research: Looking Nationwide for Devs for upcoming research study --$100 VISA gift card for your participation!
  • From: itc . vijay
• Re: bitfields
  • From: itc . vijay
• string
  • From: itc . vijay
• C command
  • From: itc . vijay
• assianing value of pointer
  • From: vj
• Re: fread/fwrite 2
  • From: Ben Bacarisse
• Re: Infinite arrays in the CCL
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: William Ahern
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: Learning C as an existing programmer
  • From: pete
• Re: Learning C as an existing programmer
  • From: Les Cargill
• Re: Learning C as an existing programmer
  • From: James Kuyper
• Re: Learning C as an existing programmer
  • From: Nachy
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: Learning C as an existing programmer
  • From: Tim Rentsch
• Re: Learning C as an existing programmer
  • From: Keith Thompson
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Keith Thompson
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: James Kuyper
• Re: fread/fwrite 2
  • From: Keith Thompson
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Keith Thompson
• Re: Learning C as an existing programmer
  • From: James Kuyper
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Gordon Burditt
• Re: Infinite arrays in the CCL
  • From: jacob navia
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Ian Collins
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Pre And Post Increment Operator Output
  • From: Tim Rentsch
• Re: Learning C as an existing programmer
  • From: James Kuyper
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: James Kuyper
• Re: Learning C as an existing programmer
  • From: Edward Rutherford
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Ian Collins
• Re: Learning C as an existing programmer
  • From: Nachy
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Paul N
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Keith Thompson
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Eric Sosman
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: James Kuyper
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Ben Bacarisse
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Eric Sosman
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: James Kuyper
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: C scope and struct definitions
  • From: Nick Bowler
• Re: Infinite arrays in the CCL
  • From: Ben Bacarisse
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: James Kuyper
• Re: Map C++ feature to C
  • From: BGB
• Re: Map C++ feature to C
  • From: BGB
• Re: A question for this group...
  • From: Kenny McCormack
• Re: Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: christian.bau
• Different sizes of data and function pointers on a machine -- void* return type of malloc, calloc, and realloc
  • From: Myth__Buster
• Re: Pre And Post Increment Operator Output
  • From: Kenneth Brody
• Re: C scope and struct definitions
  • From: Kenneth Brody
• Re: C scope and struct definitions
  • From: Kenneth Brody
• Re: C scope and struct definitions
  • From: Kenneth Brody
• Re: C scope and struct definitions
  • From: Kenneth Brody
• Re: Infinite arrays in the CCL
  • From: jacob navia
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Pre And Post Increment Operator Output
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: Learning C as an existing programmer
  • From: gwowen
• Re: Infinite arrays in the CCL
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: Heikki Kallasjoki
• Re: Learning C as an existing programmer
  • From: Ronald Benedik
• Re: Learning C as an existing programmer
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Learning C as an existing programmer
  • From: Jorgen Grahn
• Re: Map C++ feature to C
  • From: Jorgen Grahn
• Re: Learning C as an existing programmer
  • From: Ronald Benedik
• Re: Learning C as an existing programmer
  • From: Rui Maciel
• Re: Infinite arrays in the CCL
  • From: jacob navia
• Re: Infinite arrays in the CCL
  • From: Ike Naar
• Re: Pre And Post Increment Operator Output
  • From: BartC
• Re: A question for this group...
  • From: Malcolm McLean
• Infinite arrays in the CCL
  • From: jacob navia
• Re: Learning C as an existing programmer
  • From: Weland
• Re: Learning C as an existing programmer
  • From: Malcolm McLean
• Re: signed vs. unsigned multiplication
  • From: Joe.
• Re: Pre And Post Increment Operator Output
  • From: nick_keighley_nospam
• Re: signed vs. unsigned multiplication
  • From: Joe.
• Re: Learning C as an existing programmer
  • From: David Brown
• Re: Learning C as an existing programmer
  • From: Joe.
• Re: Learning C as an existing programmer
  • From: Joe.
• Re: C scope and struct definitions
  • From: nick_keighley_nospam
• Re: Learning C as an existing programmer
  • From: Joe.
• Re: Learning C as an existing programmer
  • From: Joe.
• Re: Design decisions
  • From: Joe.
• Re: Design decisions
  • From: Joe.
• Re: Design decisions
  • From: Joe.
• Re: Design decisions
  • From: Joe.
• Re: Design decisions
  • From: Joe.
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: Idiomatic module encapsulation
  • From: Robert Miles
• Re: Will 'free' return the memory Immediately to the OS ?
  • From: Robert Miles
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: Map C++ feature to C
  • From: Leo Havmøller
• Re: Map C++ feature to C
  • From: William Ahern
• Re: fread/fwrite 2
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: Ben Bacarisse
• Re: Learning C as an existing programmer
  • From: Charles Richmond
• Re: Learning C as an existing programmer
  • From: Ian Collins
• Re: Map C++ feature to C
  • From: Ian Collins
• Re: Pre And Post Increment Operator Output
  • From: Tim Rentsch
• Re: Map C++ feature to C
  • From: Ian Collins
• Learning C as an existing programmer
  • From: rammy
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: Map C++ feature to C
  • From: zgene
• Re: fread/fwrite 2
  • From: Ben Bacarisse
• Re: Pre And Post Increment Operator Output
  • From: Phil Carmody
• Re: Pre And Post Increment Operator Output
  • From: Phil Carmody
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: Map C++ feature to C
  • From: Paul N
• Re: fread/fwrite 2
  • From: Ben Bacarisse
• Re: Map C++ feature to C
  • From: BGB
• Re: Map C++ feature to C
  • From: christian.bau
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Tim Rentsch
• Re: Design decisions
  • From: jacob navia
• Re: Signed mod unsigned
  • From: Tim Rentsch
• Re: C scope and struct definitions
  • From: Tim Rentsch
• Re: Pre And Post Increment Operator Output
  • From: Tim Rentsch
• Re: fread/fwrite 2
  • From: John Gordon
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: Map C++ feature to C
  • From: Ian Collins
• Re: C scope and struct definitions
  • From: Jens Gustedt
• Re: C scope and struct definitions
  • From: Jens Gustedt
• Map C++ feature to C
  • From: zgene
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: A question for this group...
  • From: Robert Miles
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: James Kuyper
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: C scope and struct definitions
  • From: Keith Thompson
• Re: fread/fwrite 2
  • From: Ike Naar
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: fread/fwrite 2
  • From: Bill Cunningham
• Re: C scope and struct definitions
  • From: Alan Curry
• fread/fwrite 2
  • From: Bill Cunningham
• Re: Design decisions
  • From: Gareth Owen
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Jens Gustedt
• Re: Design decisions
  • From: jacob navia
• What's in a name?
  • From: Johann Klammer
• Re: Design decisions
  • From: Ian Collins
• Re: Design decisions
  • From: jacob navia
• *** air max 180 shoes（www.nike-black.com）
  • From: *** nfl
• Re: dequeue() not working
  • From: pete
• Re: Print numbers according to their native promoted type
  • From: Tim Rentsch
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Tim Rentsch
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Tim Rentsch
• Re: Design decisions
  • From: Ian Collins
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: Design decisions
  • From: jacob navia
• Re: dequeue() not working
  • From: Heikki Kallasjoki
• Re: dequeue() not working
  • From: Martin Shobe
• Re: dequeue() not working
  • From: Joe keane
• Re: C scope and struct definitions
  • From: Ben Pfaff
• Re: C scope and struct definitions
  • From: Alan Curry
• Re: Design decisions
  • From: Ian Collins
• Re: Design decisions
  • From: jacob navia
• Re: Design decisions
  • From: Ian Collins
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Pre And Post Increment Operator Output
  • From: Keith Thompson
• Re: Pre And Post Increment Operator Output
  • From: Keith Thompson
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: Pre And Post Increment Operator Output
  • From: lawrence . jones
• Re: C scope and struct definitions
  • From: Eric Sosman
• Re: Pre And Post Increment Operator Output
  • From: Kenneth Brody
• Re: Pre And Post Increment Operator Output
  • From: Les Cargill
• C scope and struct definitions
  • From: Kenneth Brody
• Re: Design decisions
  • From: Jens Gustedt
• Re: Design decisions
  • From: jacob navia
• Re: Design decisions
  • From: Gareth Owen
• Re: Design decisions
  • From: Gareth Owen
• Re: Pre And Post Increment Operator Output
  • From: John Bode
• Re: Design decisions
  • From: Neil Cerutti
• Re: Pre And Post Increment Operator Output
  • From: Ben Bacarisse
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Design decisions
  • From: David Resnick
• Re: Design decisions
  • From: Ben Bacarisse
• Re: Design decisions
  • From: gwowen
• Re: Design decisions
  • From: Neil Cerutti
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: Pre And Post Increment Operator Output
  • From: nick_keighley_nospam
• Re: BartC (was: Pre And Post Increment Operator Output)
  • From: BartC
• Re: Pre And Post Increment Operator Output
  • From: Noob
• Re: Pre And Post Increment Operator Output
  • From: Mark Bluemel
• Re: Pre And Post Increment Operator Output
  • From: Ian Collins
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Pre And Post Increment Operator Output
  • From: BartC
• Re: Design decisions
  • From: jacob navia
• Re: Pre And Post Increment Operator Output
  • From: Heinrich Wolf
• Re: Design decisions
  • From: jacob navia
• Re: Design decisions
  • From: gwowen
• Re: Design decisions
  • From: Ian Collins
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: Pre And Post Increment Operator Output
  • From: Mark Bluemel
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: Design decisions
  • From: jacob navia
• Re: Pre And Post Increment Operator Output
  • From: nick_keighley_nospam
• Re: Design decisions
  • From: io_x
• Re: Pre And Post Increment Operator Output
  • From: Yogesh Yadav Pacheria
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Pre And Post Increment Operator Output
  • From: Keith Thompson
• Re: fread/fwrite
  • From: Keith Thompson
• Re: Pre And Post Increment Operator Output
  • From: BartC
• Re: Design decisions
  • From: James Kuyper
• Re: fread/fwrite
  • From: James Kuyper
• Re: Design decisions
  • From: Gareth Owen
• Re: Pre And Post Increment Operator Output
  • From: Keith Thompson
• Re: fread/fwrite
  • From: Keith Thompson
• Microsoft User Research: Looking Nationwide for Devs for upcoming research study --$100 VISA gift card for your participation!
  • From: Gina-Microsoft
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Pre And Post Increment Operator Output
  • From: BartC
• Re: Design decisions
  • From: BartC
• Re: Pre And Post Increment Operator Output
  • From: Eric Sosman
• Re: Design decisions
  • From: Andrew Cooper
• Re: Pre And Post Increment Operator Output
  • From: Andrew Cooper
• Design decisions
  • From: jacob navia
• Re: Pre And Post Increment Operator Output
  • From: John Gordon
• Re: Pre And Post Increment Operator Output
  • From: Paul N
• Re: fread/fwrite
  • From: James Kuyper
• Pre And Post Increment Operator Output
  • From: Yogesh Yadav Pacheria
• Re: What a stupid gcc!
  • From: Andrew Smallshaw
• Re: fread/fwrite
  • From: Ian Collins
• Re: fread/fwrite
  • From: Kenneth Brody
• Re: What a stupid gcc!
  • From: Kenneth Brody
• Re: pointer and array
  • From: Varun Tewari
• Re: pointer and array
  • From: BartC
• Re: pointer and array
  • From: Eric Sosman
• pointer and array
  • From: Zhang Yuan
• Re: fread/fwrite
  • From: Mark Bluemel
• Re: What a stupid gcc!
  • From: Andrew Smallshaw
• Re: What a stupid gcc!
  • From: David Brown
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: dequeue() not working
  • From: Neil Cerutti
• Re: fread/fwrite
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: fread/fwrite
  • From: tom st denis
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: BartC
• Re: dequeue() not working
  • From: Johann Klammer
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: dequeue() not working
  • From: Ike Naar
• Re: dequeue() not working
  • From: Ike Naar
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: dequeue() not working
  • From: Ike Naar
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: fread/fwrite
  • From: nick_keighley_nospam
• dequeue() not working
  • From: arnuld
• Re: fread/fwrite
  • From: Ben Bacarisse
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: fread/fwrite
  • From: Ben Bacarisse
• Re: fread/fwrite
  • From: Ian Collins
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: fread/fwrite
  • From: Ian Collins
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: fread/fwrite
  • From: Ian Collins
• Re: fread/fwrite
  • From: Bill Cunningham
• Re: fread/fwrite
  • From: BartC
• Re: What a stupid gcc!
  • From: BartC
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: Kenneth Brody
• Re: What a stupid gcc!
  • From: Kenneth Brody
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: John Gordon
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: Johannes Bauer
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: billcun
• Re: fread/fwrite
  • From: tom st denis
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: Kenneth Brody
• Re: What a stupid gcc!
  • From: Kenneth Brody
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: fread/fwrite
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: fread/fwrite
  • From: Mark Bluemel
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: Updates to the ccl
  • From: jacob navia
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: What a stupid gcc!
  • From: Joe Pfeiffer
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Lew Pitcher
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Les Cargill
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: What a stupid gcc!
  • From: BartC
• Re: fread/fwrite
  • From: billcun
• Re: What a stupid gcc!
  • From: Ike Naar
• Re: fread/fwrite
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: Kaz Kylheku
• Re: What a stupid gcc!
  • From: BartC
• Re: fread/fwrite
  • From: Eric Sosman
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Stephen Sprunk
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: fread/fwrite
  • From: billcun
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Ian Collins
• Re: What a stupid gcc!
  • From: Ian Collins
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: BartC
• Re: What a stupid gcc!
  • From: Ike Naar
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: nick_keighley_nospam
• *** nike shoes (www.nike-black.com)
  • From: *** brand sunglasses
• Re: fread/fwrite
  • From: Eric Sosman
• Re: What a stupid gcc!
  • From: Paul J Gans
• Re: What a stupid gcc!
  • From: Paul J Gans
• Re: What a stupid gcc!
  • From: Ian Collins
• Re: What a stupid gcc!
  • From: Les Cargill
• Re: decompile
  • From: Gordon Burditt
• Re: What a stupid gcc!
  • From: Ben Bacarisse
• Re: What a stupid gcc!
  • From: BartC
• Re: fread/fwrite
  • From: Ike Naar
• Re: What a stupid gcc!
  • From: Ian Collins
• Re: What a stupid gcc!
  • From: Paul J Gans
• Re: What a stupid gcc!
  • From: Ike Naar
• Re: fread/fwrite
  • From: billcun
• Re: What a stupid gcc!
  • From: ImpalerCore
• Re: fread/fwrite
  • From: John Gordon
• Re: What a stupid gcc!
  • From: Noob
• Re: fread/fwrite
  • From: Eric Sosman
• Re: What a stupid gcc!
  • From: Ian Collins
• Re: fread/fwrite
  • From: Ian Collins
• fread/fwrite
  • From: billcun@xxxxxxxxxxxxx
• Re: What a stupid gcc!
  • From: BartC
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: Aaron W. Hsu
• Re: What a stupid gcc!
  • From: Andrew Smallshaw
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: John Bode
• Re: What a stupid gcc!
  • From: ImpalerCore
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Rich Webb
• Re: What a stupid gcc!
  • From: gwowen
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Les Cargill
• Re: Updates to the ccl
  • From: jacob navia
• Re: What a stupid gcc!
  • From: BartC
• Re: @parm @topic @doc
  • From: Jorgen Grahn
• Re: What a stupid gcc!
  • From: Jorgen Grahn
• Re: Updates to the ccl
  • From: nick_keighley_nospam
• Re: Updates to the ccl
  • From: nick_keighley_nospam
• Re: What a stupid gcc!
  • From: Jorgen Grahn
• Re: Updates to the ccl
  • From: nick_keighley_nospam
• Re: @parm @topic @doc
  • From: Robert Wessel
• Re: @parm @topic @doc
  • From: pvolkovskiy
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: nick_keighley_nospam
• @parm @topic @doc
  • From: Joseph Moschini
• Re: Updates to the ccl
  • From: gwowen
• Re: What a stupid gcc!
  • From: Noob
• Re: What a stupid gcc!
  • From: Joe Pfeiffer
• Re: signed vs. unsigned multiplication
  • From: Heikki Kallasjoki
• Re: signed vs. unsigned multiplication
  • From: BartC
• Re: Updates to the ccl
  • From: Malcolm McLean
• Re: signed vs. unsigned multiplication
  • From: Robert Wessel
• Re: signed vs. unsigned multiplication
  • From: wrschlanger
• Without any Serial number.....
  • From: abdo shosho
• Re: signed vs. unsigned multiplication
  • From: Ben Bacarisse
• Re: signed vs. unsigned multiplication
  • From: Eric Sosman
• Re: signed vs. unsigned multiplication
  • From: Xavier Roche
• Re: What a stupid gcc!
  • From: Rui Maciel
• signed vs. unsigned multiplication
  • From: wrschlanger
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: Updates to the ccl
  • From: BartC
• Re: What a stupid gcc!
  • From: BartC
• *** nike Shox NZ R4 shoes in (www.nike-black.com)
  • From: *** brand sunglasses
• Re: Print numbers according to their native promoted type
  • From: Jorgen Grahn
• Re: What a stupid gcc!
  • From: Jorgen Grahn
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• Re: Updates to the ccl
  • From: Joe.
• tentative to wrote a minamal smtp server
  • From: fakessh
• Re: Print numbers according to their native promoted type
  • From: Les Cargill
• Re: Print numbers according to their native promoted type
  • From: BartC
• Re: Print numbers according to their native promoted type
  • From: BartC
• Re: Print numbers according to their native promoted type
  • From: Ben Bacarisse
• Re: Print numbers according to their native promoted type
  • From: Ben Bacarisse
• Re: Print numbers according to their native promoted type
  • From: BartC
• Re: Print numbers according to their native promoted type
  • From: Kenny McCormack
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Jens Gustedt
• Re: Makefile Linux
  • From: James Kuyper
• Re: Print numbers according to their native promoted type
  • From: Ian Collins
• Re: Print numbers according to their native promoted type
  • From: BartC
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: Paul J Gans
• Re: Print numbers according to their native promoted type
  • From: Jens Gustedt
• Re: Print numbers according to their native promoted type
  • From: Kaz Kylheku
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Ian Collins
• Re: Print numbers according to their native promoted type
  • From: BartC
• Re: Makefile Linux
  • From: Barry
• Re: Print numbers according to their native promoted type
  • From: John Reye
• Re: Print numbers according to their native promoted type
  • From: John Reye
• Print numbers according to their native promoted type
  • From: John Reye
• Re: Makefile Linux
  • From: James Kuyper
• Re: Makefile Linux
  • From: Barry
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Noob
• Re: Determining the 'type' of a variable, if only its name is given
  • From: Jens Gustedt
• Re: Extended identifiers?
  • From: Rui Maciel
• Re: Determining the 'type' of a variable, if only its name is given
  • From: BartC
• Re: Extended identifiers?
  • From: Eric Sosman
• Re: bitfields
  • From: Nobody
• Re: Empty function parameter list
  • From: James Kuyper
• Re: Determining the 'type' of a variable, if only its name is given
  • From: pete
• Re: Determining the 'type' of a variable, if only its name is given
  • From: James Kuyper
• Re: Makefile Linux
  • From: James Kuyper
• Re: Extended identifiers?
  • From: Ben Bacarisse
• Re: Empty function parameter list
  • From: Ben Bacarisse
• Re: Extended identifiers?
  • From: Rui Maciel
• Extended identifiers?
  • From: Rui Maciel
• Extended identifiers?
  • From: Rui Maciel
• Re: Empty function parameter list
  • From: Maxim Fomin
• Re: Determining the 'type' of a variable, if only its name is given
  • From: John Reye
• Determining the 'type' of a variable, if only its name is given
  • From: John Reye
• Re: Empty function parameter list
  • From: Dinesh Kalal
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: Malcolm McLean
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: Ben Bacarisse
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Les Cargill
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Kaz Kylheku
• Re: What a stupid gcc!
  • From: Kaz Kylheku
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Joe keane
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: Fred K
• Re: Programming "only" in an environment of C and it's friends - Being a toolsmith
  • From: John Bode
• Re: linked list
  • From: Michael Press
• Re: What a stupid gcc!
  • From: Noob
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: io_x
• Re: bitfields
  • From: Joe Pfeiffer
• Re: Makefile Linux
  • From: Barry
• Re: Makefile Linux
  • From: Barry
• Re: What a stupid gcc!
  • From: Rui Maciel
• Re: What a stupid gcc!
  • From: Rui Maciel
• Re: bitfields
  • From: Ike Naar
• Re: Makefile Linux
  • From: Barry
• Re: bitfields
  • From: Eric Sosman
• Re: Makefile Linux
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Nomen Nescio
• bitfields
  • From: sinbad
• Re: Makefile Linux
  • From: Barry
• Re: standard C? -> int b = ({int a; a = 5; a;})
  • From: gwowen
• Re: What a stupid gcc!
  • From: Noob
• Re: What a stupid gcc!
  • From: James Kuyper
• Re: standard C? -> int b = ({int a; a = 5; a;})
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Varun Tewari
• Re: standard C? -> int b = ({int a; a = 5; a;})
  • From: jacob navia
• Re: What a stupid gcc!
  • From: Rui Maciel
• standard C? -> int b = ({int a; a = 5; a;})
  • From: John Reye
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Ike Naar
• Re: Open letter to Ian Collins
  • From: pete
• Re: Makefile Linux
  • From: Stephen Sprunk
• Re: Makefile Linux
  • From: James Kuyper
• Re: Makefile Linux
  • From: James Kuyper
• Re: Open letter to Ian Collins
  • From: jacob navia
• Re: Open letter to Ian Collins
  • From: pete
• Open letter to Ian Collins
  • From: pete
• Re: What a stupid gcc!
  • From: Nick Bowler
• Re: Makefile Linux
  • From: Barry
• Re: Makefile Linux
  • From: Stephen Sprunk
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: James Kuyper
• Re: What a stupid gcc!
  • From: Joe Pfeiffer
• Re: Empty function parameter list
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Les Cargill
• Re: Empty function parameter list
  • From: James Kuyper
• Re: Empty function parameter list
  • From: Eric Sosman
• Re: What a stupid gcc!
  • From: Jens Thoms Toerring
• Re: What a stupid gcc!
  • From: Eric Sosman
• Re: What a stupid gcc!
  • From: James Kuyper
• Empty function parameter list
  • From: Maxim Fomin
• Re: Need: Senior Developer- .NET at Winston Salem, NC for 4+ months
  • From: Raj Pashwar
• What a stupid gcc!
  • From: zgene
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Joe keane
• Re: decompile
  • From: Michael Angelo Ravera
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Willem
• Re: Why was there a GOTO?
  • From: Gareth Owen
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Les Cargill
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Ben Bacarisse
• Re: Makefile Linux
  • From: Barry
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: gwowen
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: James Kuyper
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: James Kuyper
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: James Kuyper
• Re: Makefile Linux
  • From: James Kuyper
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Zhang Yuan
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Joe Pfeiffer
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Ike Naar
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Ben Bacarisse
• Re: Makefile Linux
  • From: Barry
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: James Kuyper
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Zhang Yuan
• Evil in Programming Was: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: nick_keighley_nospam
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Zhang Yuan
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: James Kuyper
• Re: when apply to <ctype.h>,why should I declare a char as an int?
  • From: Ben Bacarisse
• Re: Makefile Linux
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: James Kuyper
• when apply to <ctype.h>,why should I declare a char as an int?
  • From: Zhang Yuan
• Re: Why the sizeof is 4
  • From: Ike Naar
• Re: Makefile Linux
  • From: David RF
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: nick_keighley_nospam
• Re: sorry for interrupt.I need some advise.
  • From: David RF
• Re: The C Conference, 2012-08-28, San Diego, CA
  • From: gwowen
• Re: Three stupid C questions: ++,...
  • From: nick_keighley_nospam
• Re: Three stupid C questions: ++,...
  • From: nick_keighley_nospam
• Re: Undefined Reference to Main
  • From: Gareth Owen
• Re: Why the sizeof is 4
  • From: Hill Pang
• Re: sorry for interrupt.I need some advise.
  • From: Sjouke Burry
• sorry for interrupt.I need some advise.
  • From: Zhang Yuan
• Makefile Linux
  • From: Barry
• Re: The C Conference, 2012-08-28, San Diego, CA
  • From: Brandon Philips
• Re: Three stupid C questions: ++,...
  • From: Eric Sosman
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Joe keane
• Re: Why the sizeof is 4
  • From: Keith Thompson
• Re: Three stupid C questions: ++,...
  • From: BartC
• Re: Three stupid C questions: ++,...
  • From: James Kuyper
• Re: Need: Senior Developer- .NET at Winston Salem, NC for 4+ months
  • From: Raj Pashwar
• Re: Three stupid C questions: ++,...
  • From: jean francois
• Re: Undefined Reference to Main
  • From: Ben Bacarisse
• Re: Three stupid C questions: ++,...
  • From: Fred K
• Re: Three stupid C questions: ++,...
  • From: Eric Sosman
• Re: Undefined Reference to Main
  • From: Joe Pfeiffer
• Undefined Reference to Main
  • From: Raj Pashwar
• Re: Why the sizeof is 4
  • From: Ben Bacarisse
• Re: Three stupid C questions: ++,...
  • From: John Gordon
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Zhang Yuan
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Barry Schwarz
• Re: Three stupid C questions: ++,...
  • From: James Kuyper
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Zhang Yuan
• Re: Three stupid C questions: ++,...
  • From: Fred K
• Re: Three stupid C questions: ++,...
  • From: Neil Cerutti
• Re: possible useful macros...
  • From: io_x
• Re: Why the sizeof is 4
  • From: Noob
• Re: Why the sizeof is 4
  • From: Hill Pang
• Re: Why the sizeof is 4
  • From: Johann Klammer
• Re: Three stupid C questions: ++,...
  • From: James Kuyper
• Re: Three stupid C questions: ++,...
  • From: Noob
• Re: Why the sizeof is 4
  • From: Hill Pang
• Re: Why the sizeof is 4
  • From: Johann Klammer
• Re: possible useful macros...
  • From: nick_keighley_nospam
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: nick_keighley_nospam
• Re: Three stupid C questions: ++,...
  • From: nick_keighley_nospam
• Re: Three stupid C questions: ++,...
  • From: Nomen Nescio
• Re: Why the sizeof is 4
  • From: James Kuyper
• Re: Problem with pointer, array and function parameter
  • From: James Kuyper
• Re: Why the sizeof is 4
  • From: Zhang Yuan
• Re: Why the sizeof is 4
  • From: Zhang Yuan
• Re: Problem with pointer, array and function parameter
  • From: Ike Naar
• Re: Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Ike Naar
• Re: Three stupid C questions: ++,...
  • From: MarkBluemel
• Re: Why the sizeof is 4
  • From: Ike Naar
• Sorry for interrupt,because my mother language is not English,it may be a little confused to read the c programming language.
  • From: Zhang Yuan
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: io_x
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: io_x
• Re: Why the sizeof is 4
  • From: Ian Collins
• Re: Richard Harter
  • From: Twain Benson
• Re: Why the sizeof is 4
  • From: Ian Collins
• Re: Why the sizeof is 4
  • From: Johann Klammer
• Problem with pointer, array and function parameter
  • From: fl
• Why the sizeof is 4
  • From: Hill Pang
• Re: decompile
  • From: pete
• Re: Breakthrough
  • From: pete
• Re: possible useful macros...
  • From: Thad Smith
• Re: Signed mod unsigned
  • From: Keith Thompson
• Re: linked list
  • From: Keith Thompson
• Re: Three stupid C questions: ++,...
  • From: Geoff
• Re: Three stupid C questions: ++,...
  • From: John Gordon
• Re: Three stupid C questions: ++,...
  • From: Barry Schwarz
• Re: Three stupid C questions: ++,...
  • From: John Gordon
• Re: Three stupid C questions: ++,...
  • From: Ben Bacarisse
• Re: Three stupid C questions: ++,...
  • From: BartC
• Three stupid C questions: ++,...
  • From: jean francois
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: BartC
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Joe keane
• Need: Senior Developer- .NET at Winston Salem, NC for 4+ months
  • From: Ravi
• Re: linked list
  • From: Zhang Yuan
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Ben Bacarisse
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Phil Carmody
• Re: decompile
  • From: John Bode
• Webinar - Testing the Untestable - Unit Testing Dependencies and Legacy Code (in C++)
  • From: Avi
• Re: decompile
  • From: Kenneth Brody
• Re: linked list
  • From: nick_keighley_nospam
• Cheap iphone 5, IPad, IPod, Digital Cameras Canon, Kindle, PS3, Xbox 360, Wii etc sale
  • From: classichandbagsfr@xxxxxxxxxxx
• Re: pointer vs pointer to pointer
  • From: Ben Bacarisse
• Re: Code problem
  • From: Charles Richmond
• Re: pointer vs pointer to pointer
  • From: Ike Naar
• Re: decompile
  • From: gwowen
• Re: pointer vs pointer to pointer
  • From: Ike Naar
• Re: pointer vs pointer to pointer
  • From: Barry Schwarz
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: nick_keighley_nospam
• Re: possible useful macros...
  • From: Phil Carmody
• pointer vs pointer to pointer
  • From: arnuld
• Re: Updates to the ccl
  • From: jacob navia
• Re: Richard Harter
  • From: hersheyhv
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: io_x
• Re: Updates to the ccl
  • From: Kenny McCormack
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Joe keane
• Re: Updates to the ccl
  • From: Noob
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: io_x
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: linked list
  • From: pete
• Re: char change to int, very wired
  • From: Ben Bacarisse
• Re: char change to int, very wired
  • From: Johannes Bauer
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: pete
• Re: Breakthrough
  • From: pete
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Ike Naar
• Re: Array sizes and const
  • From: Joe keane
• Re: linked list
  • From: pete
• Re: char change to int, very wired
  • From: James Kuyper
• Re: decompile
  • From: Jean-Christophe
• Re: linked list
  • From: pete
• Re: decompile
  • From: Rowan K. Fullack III
• Re: decompile
  • From: BartC
• Re: linked list
  • From: Keith Thompson
• Re: linked list
  • From: Keith Thompson
• Re: linked list
  • From: Ben Bacarisse
• Re: decompile
  • From: Ben Bacarisse
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Malcolm McLean
• Re: variable size structs and diminishing returns
  • From: David Mathog
• Re: decompile
  • From: Geoff
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: BartC
• Re: linked list
  • From: Zhang Yuan
• Re: char change to int, very wired
  • From: Kenneth Brody
• Re: decompile
  • From: Kenneth Brody
• Re: Code problem
  • From: TheGunslinger
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Malcolm McLean
• Re: char change to int, very wired
  • From: Ben Bacarisse
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Jean-Christophe
• Re: linked list
  • From: pete
• Re: linked list
  • From: pete
• Re: char change to int, very wired
  • From: BartC
• Re: variable size structs and diminishing returns
  • From: Heikki Kallasjoki
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Zhang Yuan
• Re: char change to int, very wired
  • From: pembed2012
• Re: linked list
  • From: Ike Naar
• Re: linked list
  • From: Ike Naar
• Re: Code problem
  • From: Ralph Spitzner
• Re: linked list
  • From: Ian Collins
• Re: linked list
  • From: Ian Collins
• variable size structs and diminishing returns
  • From: David Mathog
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Ian Collins
• Re: linked list
  • From: Ian Collins
• Re: linked list
  • From: Ike Naar
• Re: linked list
  • From: Zhang Yuan
• Re: linked list
  • From: Kaz Kylheku
• linked list
  • From: Zhang Yuan
• Re: copy size
  • From: Tim Rentsch
• Re: Array sizes and const
  • From: Tim Rentsch
• Re: char change to int, very wired
  • From: James Kuyper
• Re: typedef struct
  • From: Zhang Yuan
• Re: decompile
  • From: Datesfat Chicks
• Re: Breakthrough
  • From: pete
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: BartC
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Angel
• Re: Updates to the ccl
  • From: Kenny McCormack
• Re: Code problem
  • From: Keith Thompson
• Re: Updates to the ccl
  • From: Kenny McCormack
• Re: Array sizes and const
  • From: Les Cargill
• Re: char change to int, very wired
  • From: Keith Thompson
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: mike3
• Re: Code problem
  • From: Angel
• Re: decompile
  • From: Jean-Christophe
• Re: decompile
  • From: Eric Sosman
• Re: typedef struct
  • From: Keith Thompson
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: decompile
  • From: Keith Thompson
• Re: Code problem
  • From: Keith Thompson
• Re: char change to int, very wired
  • From: Joe Pfeiffer
• Re: Code problem
  • From: Keith Thompson
• Re: Updates to the ccl
  • From: Ian Collins
• Re: Signed mod unsigned
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Keith Thompson
• Re: Updates to the ccl
  • From: jacob navia
• Re: char change to int, very wired
  • From: James Kuyper
• Re: char change to int, very wired
  • From: James Kuyper
• Re: char change to int, very wired
  • From: Jean-Christophe
• Re: Array sizes and const
  • From: Joe keane
• char change to int, very wired
  • From: pembed2012
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: copy size
  • From: christian.bau
• Re: typedef struct
  • From: Zhang Yuan
• Re: Updates to the ccl
  • From: BartC
• Re: copy size
  • From: Tim Rentsch
• Re: typedef struct
  • From: James Kuyper
• Re: decompile
  • From: Jean-Christophe
• Re: copy size
  • From: Keith Thompson
• Re: decompile
  • From: James Kuyper
• Re: typedef struct
  • From: Zhang Yuan
• Re: copy size
  • From: Tim Rentsch
• Re: typedef struct
  • From: Zhang Yuan
• Re: typedef struct
  • From: Zhang Yuan
• Re: typedef struct
  • From: James Kuyper
• Re: Signed mod unsigned
  • From: Tim Rentsch
• Re: typedef struct
  • From: James Kuyper
• Re: Updates to the ccl
  • From: James Kuyper
• Re: typedef struct
  • From: Zhang Yuan
• Re: Signed mod unsigned
  • From: Tim Rentsch
• Re: typedef struct
  • From: Zhang Yuan
• Re: Updates to the ccl
  • From: BruceS
• Re: Signed mod unsigned
  • From: Tim Rentsch
• Re: typedef struct
  • From: Eric Sosman
• Re: Array sizes and const
  • From: Tim Rentsch
• Re: typedef struct
  • From: 张源 西北工业大学
• Re: Code problem
  • From: Les Cargill
• Re: typedef struct
  • From: Eric Sosman
• Re: typedef struct
  • From: 张源 西北工业大学
• Re: typedef struct
  • From: Eric Sosman
• Re: typedef struct
  • From: 张源 西北工业大学
• Re: Code problem
  • From: io_x
• Re: typedef struct
  • From: 张源 西北工业大学
• Re: Code problem
  • From: io_x
• Re: Code problem
  • From: John Gordon
• Re: Code problem
  • From: BartC
• Re: Code problem
  • From: James Kuyper
• Re: Code problem
  • From: Angel
• Re: Code problem
  • From: Kaz Kylheku
• Re: Code problem
  • From: Eric Sosman
• Code problem
  • From: rage
• Re: copy size
  • From: Eric Sosman
• Re: copy size
  • From: pete
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Angel
• Re: copy size
  • From: pete
• Re: Breakthrough
  • From: pete
• Re: copy size
  • From: David T . Ashley
• Re: copy size
  • From: Eric Sosman
• Re: copy size
  • From: David T . Ashley
• Re: Array sizes and const
  • From: Les Cargill
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: Signed mod unsigned
  • From: Tim Rentsch
• Re: Array sizes and const
  • From: Tim Rentsch
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Tim Rentsch
• Re: Updates to the ccl
  • From: jacob navia
• Re: Updates to the ccl
  • From: Kenny McCormack
• Re: Updates to the ccl
  • From: Joe.
• Re: copy size
  • From: Keith Thompson
• copy size
  • From: sinbad
• Re: Signed mod unsigned
  • From: Eric Sosman
• Re: Breakthrough
  • From: jacob navia
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: mike3
• Re: Signed mod unsigned
  • From: James Kuyper
• Re: Signed mod unsigned
  • From: Edward Rutherford
• Re: Signed mod unsigned
  • From: Ben Bacarisse
• Re: Breakthrough
  • From: Willem
• Re: Why no warning?
  • From: Jorgen Grahn
• Updates to the ccl
  • From: jacob navia
• Re: Signed mod unsigned
  • From: Eric Sosman
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: Signed mod unsigned
  • From: BartC
• Re: Signed mod unsigned
  • From: James Kuyper
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: Signed mod unsigned
  • From: Johannes Bauer
• Re: Breakthrough
  • From: pete
• Re: different result valgrind on different OS
  • From: Ben Bacarisse
• Re: Signed mod unsigned
  • From: James Kuyper
• Re: Signed mod unsigned
  • From: Edward Rutherford
• different result valgrind on different OS
  • From: fakessh @
• Re: Why no warning?
  • From: Ben Bacarisse
• Re: Why no warning?
  • From: Ben Bacarisse
• Re: Why no warning?
  • From: James Kuyper
• Re: Error returns and repeated code, GOTOs, etc.
  • From: gwowen
• Re: Why no warning?
  • From: Ralph Spitzner
• Re: Signed mod unsigned
  • From: gwowen
• Re: Signed mod unsigned
  • From: James Kuyper
• Re: Breakthrough
  • From: Robert Wessel
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: James Kuyper
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Rui Maciel
• Signed mod unsigned
  • From: Johannes Bauer
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Willem
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: pete
• Re: Breakthrough
  • From: pete
• Re: Why no warning?
  • From: Willem
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Angel
• Re: Why no warning?
  • From: James Kuyper
• Re: Why no warning?
  • From: Ben Bacarisse
• Re: Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: Ben Bacarisse
• Re: Why no warning?
  • From: Hill Pang
• Re: Why no warning?
  • From: David Brown
• Re: Why no warning?
  • From: Noob
• Re: Why no warning?
  • From: Noob
• Re: Why no warning?
  • From: James Kuyper
• Re: Why no warning?
  • From: David Brown
• Re: Why no warning?
  • From: Hill Pang
• Re: Why no warning?
  • From: Noob
• Why was there a GOTO? (was Re: GOTOs discovered in "real world" program!)
  • From: mike3
• Why no warning?
  • From: Hill Pang
• Re: Breakthrough
  • From: Robert Wessel
• Re: Breakthrough
  • From: pete
• Re: interpret this code?
  • From: George
• Re: crash on centos 5
  • From: fakessh @
• Re: crash on centos 5
  • From: BartC
• Re: crash on centos 5
  • From: Ike Naar
• Re: crash on centos 5
  • From: fakessh @
• Re: crash on centos 5
  • From: James Kuyper
• crash on centos 5
  • From: fakessh @
• Urgent requirement of NetApp SAN/NAS Storage Engineer-Infrastructure Engineer @ Hartford, CT for 6+ months
  • From: Ravi
• Re: interpret this code?
  • From: James Kuyper
• Re: interpret this code?
  • From: Nick Bowler
• Re: GOTOs discovered in "real world" program!
  • From: Joe keane
• Re: interpret this code?
  • From: Noob
• Re: interpret this code?
  • From: Noob
• Re: interpret this code?
  • From: Ben Bacarisse
• Re: interpret this code?
  • From: BartC
• Re: Quasi 0
  • From: Joe keane
• Re: interpret this code?
  • From: James Kuyper
• interpret this code?
  • From: George
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Quasi 0
  • From: James Kuyper
• Re: Decomposing a FLOAT
  • From: Malcolm McLean
• Re: Quasi 0
  • From: nick_keighley_nospam
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: James Kuyper
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Ike Naar
• Re: Breakthrough
  • From: Ike Naar
• Re: Q: Local variables initialization shortcut.
  • From: David Brown
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Edward A. Falk
• Re: Q: Local variables initialization shortcut.
  • From: Noob
• Re: Breakthrough
  • From: Noob
• Re: GOTOs discovered in "real world" program!
  • From: Joe Pfeiffer
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Martin Shobe
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Joe keane
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Joe keane
• Re: Breakthrough
  • From: BartC
• Re: Array sizes and const
  • From: Joe keane
• Re: Breakthrough
  • From: jacob navia
• Re: Breakthrough
  • From: Ian Collins
• Re: Quasi 0
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Alan Curry
• Re: Breakthrough
  • From: pete
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Joe keane
• Re: Decomposing a FLOAT
  • From: Keith Thompson
• Re: Breakthrough
  • From: jacob navia
• Re: Breakthrough
  • From: BartC
• Re: Breakthrough
  • From: jacob navia
• Re: Breakthrough
  • From: BartC
• Re: Array sizes and const
  • From: James Kuyper
• Re: Quasi 0
  • From: James Kuyper
• Re: Quasi 0
  • From: BartC
• Re: Quasi 0
  • From: David RF
• Re: Quasi 0
  • From: David RF
• Re: Quasi 0
  • From: James Kuyper
• Re: Array sizes and const
  • From: Jens Gustedt
• Re: Quasi 0
  • From: BartC
• Re: Quasi 0
  • From: David RF
• Breakthrough
  • From: jacob navia
• Re: Quasi 0
  • From: James Dow Allen
• Re: Array sizes and const
  • From: BartC
• Re: Quasi 0
  • From: David RF
• Re: Quasi 0
  • From: James Kuyper
• Re: Quasi 0
  • From: BartC
• Re: Quasi 0
  • From: David RF
• Re: Quasi 0
  • From: Eric Sosman
• Re: Quasi 0
  • From: David RF
• Re: Quasi 0
  • From: Noob
• Re: Array sizes and const
  • From: Malcolm McLean
• Quasi 0
  • From: David RF
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Ike Naar
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Martin Shobe
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Array sizes and const
  • From: Ben Bacarisse
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: Ben Bacarisse
• Re: Array sizes and const
  • From: Ben Bacarisse
• Re: Array sizes and const
  • From: Ian Collins
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Ian Collins
• Re: Array sizes and const
  • From: BartC
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Joe keane
• Re: Decomposing a FLOAT
  • From: Eric Sosman
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: BartC
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: Malcolm McLean
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: BartC
• Re: Array sizes and const
  • From: Ian Collins
• Re: Decomposing a FLOAT
  • From: Ian Collins
• Re: Decomposing a FLOAT
  • From: Ian Collins
• Re: Array sizes and const
  • From: Malcolm McLean
• Re: Decomposing a FLOAT
  • From: Raj Pashwar
• Re: Decomposing a FLOAT
  • From: Raj Pashwar
• Re: Array sizes and const
  • From: Malcolm McLean
• Re: Array sizes and const
  • From: Keith Thompson
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Ben Bacarisse
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Ben Bacarisse
• Re: Array sizes and const
  • From: David Brown
• Re: Decomposing a FLOAT
  • From: Keith Thompson
• Re: Q: Local variables initialization shortcut.
  • From: David Brown
• Re: Q: Local variables initialization shortcut.
  • From: David Brown
• Re: Q: Local variables initialization shortcut.
  • From: David Brown
• Re: Q: Local variables initialization shortcut.
  • From: David Brown
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Array sizes and const
  • From: James Kuyper
• Re: Q: Local variables initialization shortcut.
  • From: Malcolm McLean
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Jean-Christophe
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: io_x
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: io_x
• Re: Decomposing a FLOAT
  • From: Malcolm McLean
• Re: Array sizes and const
  • From: Malcolm McLean
• Re: Array sizes and const
  • From: Nobody
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Decomposing a FLOAT
  • From: Eric Sosman
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Willem
• Re: Array sizes and const
  • From: BartC
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: io_x
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: io_x
• Re: Error returns and repeated code, GOTOs, etc.
  • From: io_x
• Re: Q: Local variables initialization shortcut.
  • From: io_x
• Re: Q: Local variables initialization shortcut.
  • From: io_x
• Re: Decomposing a FLOAT
  • From: Raj Pashwar
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Array sizes and const
  • From: Les Cargill
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Ben Bacarisse
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: typedef struct
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Keith Thompson
• Re: Array sizes and const
  • From: James Kuyper
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: Array sizes and const
  • From: Ian Collins
• Re: Array sizes and const
  • From: Nobody
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Array sizes and const
  • From: Les Cargill
• Re: Array sizes and const
  • From: Keith Thompson
• Re: Decomposing a FLOAT
  • From: Keith Thompson
• Re: Q: Local variables initialization shortcut.
  • From: Keith Thompson
• Re: Q: Local variables initialization shortcut.
  • From: Keith Thompson
• Re: Array sizes and const
  • From: Les Cargill
• Re: Q: Local variables initialization shortcut.
  • From: Eric Sosman
• Re: Array sizes and const
  • From: Les Cargill
• Re: typedef struct
  • From: Fritz Wuehler
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Array sizes and const
  • From: Eric Sosman
• Re: Array sizes and const
  • From: Ian Collins
• Array sizes and const
  • From: Les Cargill
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Eric Sosman
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Jean-Christophe
• Re: Decomposing a FLOAT
  • From: Nobody
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Joe keane
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Martin Shobe
• Re: Q: Local variables initialization shortcut.
  • From: Eric Sosman
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Ike Naar
• Re: Q: Local variables initialization shortcut.
  • From: Robert Wessel
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Joe keane
• Re: GOTOs discovered in "real world" program!
  • From: blmblm
• Re: GOTOs discovered in "real world" program!
  • From: Robert Wessel
• Re: GOTOs discovered in "real world" program!
  • From: BartC
• Re: Error returns and repeated code, GOTOs, etc.
  • From: io_x
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: James Kuyper
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Ben Bacarisse
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Noob
• Re: GOTOs discovered in "real world" program!
  • From: Malcolm McLean
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: Q: Local variables initialization shortcut.
  • From: Eric Sosman
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Joe keane
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Thad Smith
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Eric Sosman
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: pete
• Re: Q: Local variables initialization shortcut.
  • From: pete
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Generic programming in C.
  • From: pete
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: BartC
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: Q: Local variables initialization shortcut.
  • From: Jens Thoms Toerring
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: Q: Local variables initialization shortcut.
  • From: Ian Collins
• Re: Q: Local variables initialization shortcut.
  • From: jacob navia
• Q: Local variables initialization shortcut.
  • From: Jean-Christophe
• Re: GOTOs discovered in "real world" program!
  • From: Aaron W. Hsu
• Re: GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: BartC
• Re: Generic programming in C.
  • From: io_x
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: Decomposing a FLOAT
  • From: Joe keane
• Re: Decomposing a FLOAT
  • From: Kenny McCormack
• Re: Decomposing a FLOAT
  • From: Malcolm McLean
• Re: Decomposing a FLOAT
  • From: Joe keane
• Re: typedef struct
  • From: BartC
• Re: typedef struct
  • From: Ike Naar
• Re: typedef struct
  • From: Ian Collins
• Re: typedef struct
  • From: Keith Thompson
• Updates to the containers library
  • From: jacob navia
• Re: Aliasing in C99
  • From: Tim Rentsch
• Re: GOTOs discovered in "real world" program!
  • From: Aaron W. Hsu
• Re: Error returns and repeated code, GOTOs, etc.
  • From: tom st denis
• Re: GOTOs discovered in "real world" program!
  • From: mike3
• Re: Returning a structure without any temporary variable
  • From: James Kuyper
• Re: Returning a structure without any temporary variable
  • From: Xavier Roche
• Re: Returning a structure without any temporary variable
  • From: Xavier Roche
• Re: Returning a structure without any temporary variable
  • From: jacob navia
• Re: Returning a structure without any temporary variable
  • From: David RF
• Re: typedef struct
  • From: Nomen Nescio
• Returning a structure without any temporary variable
  • From: Xavier Roche
• Re: Aliasing in C99
  • From: David Brown
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Willem
• Re: Another problem (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: Ian Collins
• Re: GOTOs discovered in "real world" program!
  • From: Ben Bacarisse
• Re: Aliasing in C99
  • From: Tim Rentsch
• Re: typedef struct
  • From: Nomen Nescio
• Re: Error returns and repeated code, GOTOs, etc.
  • From: Tim Rentsch
• Another problem (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: mike3
• GOTOs discovered in "real world" program! (was Re: Error returns and repeated code, GOTOs, etc.)
  • From: mike3
• Re: Error returns and repeated code, GOTOs, etc.
  • From: mike3
• Re: condition true or false? -> (-1 < sizeof("test"))
  • From: Tim Rentsch
• Re: Decomposing a FLOAT
  • From: James Kuyper
• Re: Decomposing a FLOAT
  • From: Ike Naar
• Re: Decomposing a FLOAT
  • From: Ben Bacarisse
• Re: Aliasing in C99
  • From: David Brown
• Re: Decomposing a FLOAT
  • From: Steven G. Kargl
• Re: "Open letter" to jake
  • From: Keith Thompson
• Re: typedef struct
  • From: Keith Thompson
• Re: Aliasing in C99
  • From: Tim Rentsch