January 1989 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]

Starting: Sun Jan 1 07:18:23 AEST 1989
Ending: Tue Jan 31 17:58:19 AEST 1989
Messages: 762

• YALF (yet another lint foulup)   Ken Raeburn
• Is malloc() or calloc() "better"?   Peter da Silva
• Style wars   RAMontante
• Tabs vs. Spaces   Eric S. Raymond
• Is malloc() or calloc() "better"?   Eric S. Raymond
• Imposed indentation standards don't work   Jonathan Leech
• Strange lint mumblings   Doug Gwyn
• The world is not ready for 'volatile'   Doug Gwyn
• main() and exit() (was: Strange lint mumblings)   Doug Gwyn
• Is malloc() or calloc() "better"?   Doug Gwyn
• YALF (yet another lint foulup)   Doug Gwyn
• Style (was: C-DATABASE B-PLUS a quick look)   Doug Gwyn
• Suggested new C loop syntax   Mark A Terribile
• Proposal for a scientific look at C style choices   Mark A Terribile
• Always use braces (was: Suggested new C loop syntax)   Piercarlo Grandi
• Perfect hashing table/function   Gary D Duzan
• const, volatile, etc [was Re: #   Piercarlo Grandi
• Proposal for a scientific look at C style choices   Geoff Clemm
• The world is not ready for 'volatile'   Geoff Clemm
• printf, data presentation   Stuart Gathman
• Always use braces   Frans van Otten
• Proposal for a scientific look at C style choices   Frans van Otten
• Tabs vs. Spaces   Peter da Silva
• hardcoded constants   Simon A Reap
• C Programming Problem   Terrence Brannon
• YALF (yet another lint foulup)   David Goodenough
• toupper(EOF) (was Re: Style)   David Goodenough
• printf, data presentation   James C. Benz
• Imposed indentation standards don't work   Eric S. Raymond
• volatile registers (was: The world is not ready for 'volatile')   Liber
• correct code for pointer subtraction   Carl Paukstis
• Perfect hashing table/function   pardo at june.cs.washington.edu
• printf, data presentation   Greg Pasquariello X1190
• Style wars   david wald
• Is malloc() or calloc() "better"?   david wald
• The world is not ready for 'volatile'   Chris Torek
• const, volatile, etc   Doug Gwyn
• Style wars   Alan Filipski
• printf, data presentation   Vincent C. Hatem
• Request for info   Thanbo
• Imposed indentation standards don't work   Peter Desnoyers
• Perfect hashing table/function   Bernie Cosell
• Braces are not Compiler-Fluff.   T. William Wells
• correct code for pointer subtraction   Bob Larson
• Always use braces   Doug Gwyn
• The world is not ready for 'volatile'   Doug Gwyn
• The world is not ready for 'volatile'   Chris Torek
• C Programming Problem   Greg Pasquariello X1190
• printf, data presentation   Chris Calabrese[mav]
• Cachable functions (was: Re: const, volatile, etc [was Re: #defines with parameters]   Art Boyne
• Lisp to C. Another request!   Francois Lecouat
• Tabs vs. Spaces   Eric S. Raymond
• Proposal for a scientific look at C style choices   Conor O'Neill
• C Programming Problem   Y. Rock Lee
• common-lisp to c   Jeff Dalton
• printf, data presentation   Knudsen
• Lisp to C. Another request!   Geoff Clemm
• printf, data presentation   Doug Gwyn
• Always use braces (was: Suggested new C loop syntax)   Dave Decot
• C Programming Problem   rae98
• Proposal for a scientific look at C style choices   David Dyer-Bennet
• Tabs vs. Spaces   David Dyer-Bennet
• Type Curves and Laplace Transforms   Peter C. Bahrs
• printf, data presentation   Peter da Silva
• C Programming Problem   Mike Laman
• Is malloc() or calloc() "better"?   Dave Martindale
• printf, data presentation   A. Wen
• Is malloc() or calloc() "better"?   Cleve Ashcraft
• Strange lint mumblings   Mark Brader
• use of toupper (was: Style (was: C-DATABASE B-PLUS a quick look))   Karl Heuer
• The world is not ready for 'volatile'   Colin Plumb
• Expression Based Language   Eric S. Raymond
• Proposal for a scientific look at C style choices   Kenneth Almquist
• layout is not Style   Steve Summit
• Always use braces   Frans van Otten
• printf, data presentation   Stephen J. Friedl
• printf, data presentation   Dave Hammond
• Braces are not Compiler-Fluff.   T. William Wells
• printf, data presentation   Dave Hammond
• comments (was Re: hardcoded constants)   David Goodenough
• Name that algorithm (a small puzzle)   Charles Fineman
• Subroutine layout in C   David Geary
• Indent! Indent! (was Re: Proposal for a scientific look at C style choices)   T. William Wells
• Is malloc() or calloc() "better"?   Darin Johnson
• Style (was: C-DATABASE B-PLUS a quick look)   T. William Wells
• correct code for pointer subtraction   Tapani Tarvainen
• Is malloc() or calloc() "better"?   Peter C. Bahrs
• Always use braces   Doug Gwyn
• Lint libraries for dpANS C and POSIX?   Rich Salz
• Expression Based Language   Karl Heuer
• Is malloc() or calloc() "better"?   Liber
• Is malloc() or calloc() "better"?   Liber
• YALF (yet another lint foulup)   Liber
• Name that algorithm (a small puzzle)   Mark Kornell
• register volatile (was The world is not ready for 'volatile')   Chris Torek
• Indent! Indent!   Chris Torek
• Perfect hashing table/function   Doug Schmidt
• Perfect hashing table/function   Doug Schmidt
• Is malloc() or calloc() "better"?   Andrew Hume
• Is malloc() or calloc() "better"?   david wald
• printf, data presentation   Doug Gwyn
• Allocating Huge Arrays in MSC 5.0   Pierre-Yves Thoulon
• Is malloc() or calloc() "better"?   Steve Summit
• Braces are not Compiler-Fluff.   Daniel F. Fisher
• main() and exit() (was: Strange lint mumblings)   Steve Summit
• register volatile   Doug Gwyn
• Yet Another Lint Foul-up   Jack L. Vevea
• #define volatile /*empty*/ (was register volatile)   Chris Torek
• C++   William E. Davidsen Jr
• printf, data presentation   Chris Calabrese[mav]
• Yet Another Lint Foul-up   Andrew Duane
• Allocating Huge Arrays in MSC 5.0   Bill Ives
• Subroutine layout in C   <10000>Ariel Aloni
• YALF (yet another lint foulup)   david wald
• Proposal for a scientific look at C style choices   Mike Albaugh
• printf, data presentation   Bruce Robertson
• "C" Interpreter   Mike Haley
• Yet Another Lint Foul-up   Jim Shankland
• Subroutine layout in C   Jeff A. Bowles
• Yet Another Lint Foul-up   Guy Harris
• C Programming Problem   Guy Harris
• printf, data presentation   Guy Harris
• Subroutine layout in C   Matt Landau
• printf, data presentation   John F. Haugh II
• Yet Another Lint Foul-up   David F. Carlson
• Name that algorithm (a small puzzle)   Charles Fineman
• YALF (yet another lint foulup)   Karl Heuer
• Subroutine layout in C   Mark Nagel
• printf, data presentation   Peter da Silva
• printf, data presentation   Peter da Silva
• Tabs vs. Spaces   Peter da Silva
• C Style Guide   Peter da Silva
• Subroutine layout in C   Dave Jones
• YALF (yet another lint foulup)   Doug Gwyn
• main() and exit() (was: Strange lint mumblings)   Doug Gwyn
• printf, data presentation   John B Scalia
• Subroutine layout in C   Dave Jones
• Yet Another Lint Foul-up   Doug Gwyn
• Subroutine layout in C   Doug Gwyn
• Is malloc() or calloc() "better"?   Doug Gwyn
• #define volatile /*empty*/   Doug Gwyn
• correct code for pointer subtraction   Doug Gwyn
• #define volatile /*empty*/   Doug Gwyn
• How to use toupper()   Mark Brader
• passing variable numbers of arguments   David MacKenzie
• Yet Another Lint Foul-up   Bob Larson
• spiffy terminals (was: printf, data presentation)   Doug Gwyn
• passing variable numbers of arguments   Doug Gwyn
• Yet Another Lint Foul-up   Doug Gwyn
• Proposal for a scientific look at C style choices   Mark A Terribile
• Is malloc() or calloc() "better"?   Leo de Wit
• spiffy terminals (was: printf, data presentation)   John F. Haugh II
• passing variable numbers of arguments   Andrew Koenig
• Yet Another Lint Foul-up   Arthur David Olson
• correct code for pointer subtraction   Charles Marslett
• Keeping executables small (was: main() and exit())   Steve Summit
• Yet Another Lint Foul-up   John B. Nagle
• passing variable numbers of arguments   Chris Torek
• spiffy terminals (was: printf, data presentation)   pri=-10 Stuart Lynne
• printf, data presentation   Barry Shein
• #define volatile /*empty*/   Stephen J. Friedl
• Lint libraries for dpANS C and POSIX?   Stephen J. Friedl
• printf, data presentation   T. William Wells
• Yet Another Lint Foul-up   T. William Wells
• YALF (yet another lint foulup)   Alan J Rosenthal
• spiffy terminals (was: printf, data presentation)   Doug Gwyn
• passing variable numbers of arguments   Chris Torek
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   T. William Wells
• "C" Interpreter   Ken Raeburn
• printf, data presentation   mcdonald at uxe.cso.uiuc.edu
• correct code for pointer subtraction   Pete Alleman
• passing variable numbers of arguments   Dominick Samperi
• Is malloc() or calloc() "better"?   Michael Paul Hunter
• correct code for pointer subtraction   Tapani Tarvainen
• It is better to remain silent...   T. William Wells
• printf, data presentation   Kenneth Almquist
• passing variable numbers of arguments   Chris Torek
• passing variable numbers of arguments   Andrew Koenig
• passing variable numbers of arguments   Doug Gwyn
• curses (was: printf, data presentation)   Doug Gwyn
• passing variable numbers of arguments   Kenneth Almquist
• spiffy terminals (was: printf, data presentation)   Mike Albaugh
• passing variable numbers of arguments   Doug Gwyn
• "C" Interpreter   Sean Fagan
• printf, data presentation   Sean Fagan
• Subroutine layout in C   Wade Guthrie
• NULL is not '\0' (was: Is malloc() or calloc() "better"?)   Karl Heuer
• Yet Another Lint Foul-up   Guy Harris
• passing variable numbers of arguments   Karl Heuer
• cprintf function query   RAMontante
• printf, data presentation   Peter da Silva
• passing variable numbers of arguments   Guy Harris
• Using Make, SCCS, Lint, & C   3929] Brian Gilstrap
• YACC grammar for C language   Jung Hamel
• BIT Counting: C programming problem   Jim Becker
• lint question   Paul T. Shannon
• correct code for pointer subtraction   Mark Brader
• Virtual memory libraries under DOS   Steve Fullerton
• passing variable numbers of arguments   Doug Gwyn
• lint question   Doug Gwyn
• passing variable numbers of arguments   Steve Summit
• printf, data presentation   T. William Wells
• preventing sign extension   David MacKenzie
• BIT Counting: C programming problem   Miles Bader
• Would *you* get caught by this one?   Mark A Terribile
• C Style Guide   Dave Straker
• Suggested new C loop syntax (was `if (a = b)')   Richard J Cox
• "C" Interpreter   David Dymm
• new do-while syntax   Richard J Cox
• Is malloc() or calloc() "better"?   Jim Patterson
• Is malloc() or calloc() "better"?   Jim Patterson
• lint question   Peter da Silva
• lint question   T. William Wells
• "C" Interpreter   Geoff Clemm
• lint question   Doug Philips
• BIT Counting: C programming problem   Bernie Cosell
• portability   Richard Goerwitz
• Bit counting   Rich Neitzel
• Microsoft C cross compiler and linker for UNIX on a VAX   David Marks
• BIT Counting: C programming problem   John Worley
• printf, data presentation   Scott Wilson
• C Style Guide   George W. Leach
• "C" Interpreter   rogerson
• Bit counting   Rich Neitzel
• BIT Counting: C programming problem   chuck
• Braces are not Compiler-Fluff.   Ray Dunn
• spiffy terminals (was: printf, data presentation)   Kenneth P. Stox
• C Style   Peter da Silva
• C Style   Peter da Silva
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Tainter
• BIT Counting: C programming problem   Dave Jones
• lint question   Dave Jones
• passing variable numbers of arguments   Stephen J. Friedl
• spiffy terminals (was: printf, data presentation)   Paul De Bra
• how to post source?   Tony Field
• INKEY$ [Was: printf, data presentation]   Chip Rosenthal
• typechecking   Robert Forsman
• inkey$, noecho, and other impossibles   Chris Torek
• preventing sign extension   David MacKenzie
• Bit counting   Andrew Hume
• passing variable numbers of arguments   Sean Fagan
• lint question   Doug Gwyn
• preventing sign extension   Doug Gwyn
• C Style Guide   Doug Gwyn
• typechecking   Doug Gwyn
• C Style   Doug Gwyn
• lint question   Doug Gwyn
• inkey$, noecho, and other impossibles   Doug Gwyn
• BIT Counting: C programming problem   Barry Margolin
• spiffy terminals (was: printf, data presentation)   Dominic Dunlop
• inkey$, noecho, and other impossibles   Chris Torek
• C Style   T. William Wells
• spiffy terminals (was: printf, data presentation)   Dr. T. Andrews
• It is better to remain silent...   Ray Dunn
• BIT Counting: C programming problem   Jerry Leichter
• printf, data presentation   mcdonald at uxe.cso.uiuc.edu
• lint question   Farrell Woods
• BIT Counting: C programming problem   Jordan Henderson
• printf, data presentation   mcdonald at uxe.cso.uiuc.edu
• spiffy terminals (was: printf, data presentation)   Keith Muller
• Bit counting   Rich Neitzel
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Peter da Silva
• BIT Counting: C programming problem   Sean Malloy
• BIT Counting: C programming problem   was-John McMillan
• typechecking   Tom Tkacik
• C Style Guide   Peter Desnoyers
• Bit Counting program, lots of votes are in!   Jim Becker
• inkey$, noecho, and other impossibles   Peter Desnoyers
• YACC grammar for C language   Steve Vegdahl
• lint question   Guy Harris
• passing variable numbers of arguments   Guy Harris
• typechecking   RAMontante
• How to use toupper()   Karl Heuer
• INKEY$ [Was: printf, data presentation]   Scott Wilson
• What I expect from a C optimizer   Stuart Gathman
• BIT Counting: C programming problem   -for inetd server command
• lint question   Peter da Silva
• C Style   Peter da Silva
• typechecking   Doug Schmidt
• Proposal for a scientific look at C style choices   David Dyer-Bennet
• BIT Counting: C programming problem   Peter Desnoyers
• BIT Counting: C programming problem   greg yachuk
• main() and exit() (was: Strange lint mumblings)   John Woods
• YACC grammar for C language   Michael Meissner
• malloc impossible? (was: inkey$, noecho, and other impossibles)   Doug Gwyn
• ,alloc/sbrk (was: inkey$, noecho, and other impossibles)   Doug Gwyn
• BIT Counting: C programming problem   Doug Gwyn
• C Style   Doug Gwyn
• Braces are not Compiler-Fluff.   T. William Wells
• A brace vs. indentation hypothesis   T. William Wells
• spiffy terminals   Doug Gwyn
• malloc impossible? (was: inkey$, noecho, and other impossibles)   Chris Torek
• INKEY$ [Was: printf, data presentation]   Robert Claeson
• C Style   David Wolverton
• passing variable numbers of arguments   Farrell Woods
• malloc impossible?   Doug Gwyn
• Proposal for a scientific look at C style choices   Griff Smith
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Blair P. Houghton
• BIT Counting: C programming problem   Peter Desnoyers
• printf, data presentation   Jonathan Bayer
• C Style   Leo de Wit
• printf, data presentation   Chris Calabrese[mav]
• Keeping executables small (was: main() and exit())   Alan J Rosenthal
• malloc impossible?   Jim Shankland
• printf, data presentation   T. William Wells
• BIT Counting: C programming problem   Joe Buck
• Is malloc() or calloc() "better"?   Doug Gwyn
• BIT Counting: C programming problem   Clayton Cramer
• How to use toupper()   Wayne A. Throop
• Bit Counting program, lots of votes are in!   Shankar Unni
• Extended ASCII in Turbo C --> DESPIRATE!!!!   Brian Martin
• YACC grammar for C language   Dave Jones
• YACC grammar for C language   Dave Jones
• Would *you* get caught by this one?   Andrew Koenig
• portability   Wade Guthrie
• Having problems with float and functional prototypes   Mark Dornfeld
• passing variable numbers of arguments   Karl Heuer
• typechecking   Michael Meissner
• malloc impossible?   Dik T. Winter
• The Halting Problem (was: YALF (yet another lint foulup))   david wald
• C Style [check cpp symbol to decide file inclusion]   Paul Lew
• malloc impossible?   Chris Torek
• printf, data presentation   Scott Schwartz
• malloc impossible? (was: inkey$, noecho, and other impossibles)   Joe English
• Scientific C style choices (+ example of MY coding standard)   Pekka Akselin [The Mad Midnight Hacker]
• malloc impossible?   Doug Gwyn
• spiffy terminals   Doug Gwyn
• passing variable numbers of arguments   Doug Gwyn
• malloc impossible?   Doug Gwyn
• C Style   Doug Gwyn
• Would *you* get caught by this one?   LTH network news server
• The Halting Problem (was: YALF (yet another lint foulup))   Mark A Terribile
• malloc impossible? (was: inkey$, noecho, and other impossibles)   Stephen J. Friedl
• malloc impossible? (was: inkey$, noecho, and other impossibles)   Chris Torek
• lint question   Richard J Cox
• lint question   Richard J Cox
• Would *you* get caught by this one?   Steve Harrold
• YACC grammar for C language   Piet van Oostrum
• How to read 0xFFFF from a file ?!?!   Francesco Rossi
• spiffy terminals   Greg Hennessy
• spiffy terminals   Scott Wilson
• OH NO!! (Re: Standard Indentation etc.)   John Hascall
• The Halting Problem (was: YALF (yet another lint foulup))   Nick Crossley
• The Halting Problem (was: YALF (yet another lint foulup))   Peter Desnoyers
• INKEY$ [Was: printf, data presentation]   Peter da Silva
• #ifndef GRAPHICS_H (Re: C Style)   Peter da Silva
• Would *you* get caught by this one?   Tony Williams
• OH NO!! (Re: Standard Indentation etc.)   Dave Jones
• Proposal for a scientific look at C style choices   David Dyer-Bennet
• passing variable numbers of arguments   Daniel F. Fisher
• Microsoft C 5.1 question   David McIntyre
• portability   Miles Bader
• Playing with the bits of floats   Max Rible
• Comma Operator   nair at quintus
• spiffy terminals   Wilson Heydt
• passing variable numbers of arguments   Karl Heuer
• Comma Operator   Colin Plumb
• Re^2: BIT Counting: C programming problem   Maarten Litmaath
• Would *you* get caught by this one?   Mark A Terribile
• YACC grammar for C language   Doug Gwyn
• spiffy terminals   Doug Gwyn
• spiffy terminals   Doug Gwyn
• BIT Counting: C programming problem   Doug Gwyn
• Comma Operator   Doug Gwyn
• Would *you* get caught by this one?   Doug Gwyn
• spiffy terminals   Doug Gwyn
• Comma Operator   Chris Torek
• printf, data presentation   Richard J Cox
• passing variable numbers of arguments   Doug Gwyn
• printf, data presentation   Jonathan Bayer
• Broken compilers? (was Re: Comma Operator)   Blair P. Houghton
• Comma Operator   Andrew Koenig
• spiffy terminals   T. William Wells
• Microsoft C 5.1 question   John L. Furlani
• malloc impossible?   Tainter
• Comma Operator   Earle R. Horton
• C For Programmers   Stephan - Somogyi
• printf, data presentation   Paul Sander
• Broken compilers? (was Re: Comma Operator)   Doug Gwyn
• INKEY$ [Was: printf, data presentation]   Dave Levenson
• Catching DOS interrupt 24H (critical error handler)   tony at joshua.math.ucla.edu
• BIT Counting: C programming problem   Steve Summit
• printf, data presentation   Sean Fagan
• Using getopt to parse multi-argument options   Roy Smith
• typechecking   Roland Wilcher
• conditional includes   joe at modcomp.UUCP
• printf, data presentation   Jonathan Leech
• passing variable numbers of arguments   Daniel F. Fisher
• spiffy terminals   Robert Elz
• Broken compilers? (was Re: Comma Operator)   Chris Torek
• Using getopt to parse multi-argument options   Doug Gwyn
• malloc impossible?   Doug Gwyn
• Would *you* get caught by this one?   Doug Gwyn
• typechecking   RAMontante
• spiffy terminals (was: printf, data presentation)   Brandon S. Allbery
• portability   Michael Paul Hunter
• C Style [check cpp symbol to decide file inclusion]   Peter da Silva
• Keeping executables small (was: main() and exit())   Henry Spencer
• Bit counting   Henry Spencer
• BIT Counting: C programming problem   Alan J Rosenthal
• spiffy terminals (was: printf, data presentation)   Henry Spencer
• character-at-a-time i/o   Henry Spencer
• Using getopt to parse multi-argument options   Henry Spencer
• Command Syntax Standard (was Re: Using getopt to parse multi-argument options)   Daniel F. Fisher
• lint question   Henry Spencer
• C Style Guide   Henry Spencer
• Microsoft C 5.1 question   Kenneth Almquist
• Extended ASCII in Turbo C --> DESPIRATE!!!!   teittinen at cc.helsinki.fi
• Using getopt to parse multi-argument options   RAMontante
• turbo c 2.0 graphics?   robert r. calhoun
• new Quick C "2" ?   David Robins
• portability   rogerson
• printf, data presentation   Guy Harris
• lint question   Bennett Todd
• Playing with the bits of floats   Walter Bright
• Broken compilers? (was Re: Comma Operator)   Blair P. Houghton
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Chip Salzenberg
• Broken compilers? (was Re: Comma Operator)   Blair P. Houghton
• ANSI float.h   Mike McNally
• MS-DOS Profiler (PROBE source?)   John Milton
• Broken compilers? (was Re: Comma Operator)   Ken Arromdee
• Would *you* get caught by this one?   David Goodenough
• Broken compilers? (was Re: Comma Operator)   Tim Olson
• portability   Geoff Rimmer
• printf, data presentation   Bruce Albrecht
• spiffy terminals   Barry Shein
• C For Programmers   Geoff Rimmer
• lint question   Geoff Rimmer
• Playing with the bits of floats   Herman Rubin
• turbo c 2.0 graphics?   Brian Martin
• spiffy terminals   Blair P. Houghton
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Blair P. Houghton
• lint question   Chip Salzenberg
• ANSI C function declaration prototypes   rja
• ANSI float.h   Doug Gwyn
• Playing with the bits of floats   Doug Gwyn
• conditional includes   T. William Wells
• Braces are not Compiler-Fluff.   Ray Dunn
• lint question   James C. Benz
• portability   Doug Gwyn
• Using getopt to parse multi-argument options   Alan Fargusson at peace with the world
• Playing with the bits of floats   Marianne Mueller
• new Quick C "2" ?   Geoff Rimmer
• turbo c 2.0 graphics?   The Polymath
• Yet Another Lint Foul-up   Daniel E. Wilson
• malloc impossible?   John Woods
• Using getopt to parse multi-argument options   Daniel R. Levy
• comp.lang.c   Tony Field
• lint question   Guy Harris
• portability   RAMontante
• portability   Charles Marslett
• Bit counting   Bennett Todd
• typechecking   Bennett Todd
• Playing with the bits of floats   Herman Rubin
• using floats in functional prototypes   Royal Ontario Museum
• portability   mcdonald at uxe.cso.uiuc.edu
• Bit-reversed counting   Joseph Nathan Hall
• A brace vs. indentation hypothesis   David Goodenough
• More ANSI float.h stuff   Mike McNally
• portability   Prescott K. Turner
• static versus auto initialization   Bob Devine
• Yet Another Lint Foul-up   Guy Harris
• lint question   Doug Gwyn
• portability   Doug Gwyn
• malloc impossible?   Doug Gwyn
• Playing with the bits of floats   Doug Gwyn
• where can I get standards documents   Gordon Cross
• unsigned to double   Greg Fischer
• new Quick C "2" ?   Jim Alves-Foss
• Playing with the bits of floats   Raymond Juimong Chen
• Looking for Microsoft Windows developer's library   William Roetzheim
• Preprocessor question   Ray Berry
• porting smallc to 6502/Apple2e   Paul Nakada
• spiffy terminals   Unix Consultation Mailbox
• portability   Bob Larson
• new Quick C "2" ?   Jeff Leyser
• C Style   Leo de Wit
• turbo c 2.0   rja
• using floats in functional prototypes   Ralf.Brown at B.GP.CS.CMU.EDU
• static versus auto initialization   Doug Gwyn
• More ANSI float.h stuff   Doug Gwyn
• Preprocessor question   Doug Gwyn
• portability   Doug Gwyn
• static versus auto initialization   K.LAUX
• Use of " ? : " in format param to printf   Robert Seals
• lint question   Blair P. Houghton
• What should [fs]scanf return?   Dale Schumacher
• static versus auto initialization   Wade Guthrie
• static versus auto initialization   Guy Harris
• portability   Scott Wilson
• Using getopt to parse multi-argument options   Henry Spencer
• static versus auto initialization   John Mundt
• Use of " ? : " in format param to printf   Doug Gwyn
• Programming gems (Re: Bit-reversed counting)   Peter da Silva
• Preprocessor question   Curt Wohlgemuth
• new Quick C "2" ?   Brad Brown
• Use of " ? : " in format param to printf   Andrew Koenig
• using floats in functional prototypes   Larry Jones
• Preprocessor question   Larry Jones
• Looking for Microsoft Windows developer's library   Bruce Wright
• Preprocessor question   Glenn Fowler[eww]
• where can I get standards documents   Henry Spencer
• Behaviour of setjmp/longjmp and registers   David Haynes
• static versus auto initialization   Chris Torek
• portability   RAMontante
• portability   Mark Freedman
• IBM PC/RT pl8cc compiler and stack frames   Bjorn Engsig
• Yet another pcc botch   Lawrence V. Cipriani
• Passing variable #of args   Dave Hammond
• new Quick C "2" ?   Ned D Hanks
• ConcurrentC. Current status?   Jonathon Seymour
• Catching DOS interrupt 24H (critical error handler)   Gene McManus
• HASHING, revisited - A summary.   Greg Wettstein
• using floats in functional prototypes   Eric Johnson
• portability   Doug Gwyn
• conditional includes   Doug Gwyn
• C Style   Doug Gwyn
• static versus auto initialization   Doug Gwyn
• Preprocessor question   Doug Gwyn
• dereferencing function pointers   Don Allingham
• Behaviour of setjmp/longjmp and registers   Henry Spencer
• portability   Henry Spencer
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Tony Field
• where can I get standards documents   Brian Moffet
• static versus auto initialization   Guy Harris
• portability   Guy Harris
• What should [fs]scanf return?   Guy Harris
• Behaviour of setjmp/longjmp and registers   Guy Harris
• A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)   Tony Field
• new Quick C "2" ?   Clarence Dold
• conditional includes   joe at modcomp.UUCP
• ANSI C function declaration prototypes   Doug Gwyn
• dereferencing function pointers   Doug Gwyn
• Behaviour of setjmp/longjmp and registers   Chris Torek
• TC2.0 bugfree ?   Chris Torek
• Behaviour of setjmp/longjmp and registers   Tim Moore
• new Quick C "2" ?   Don Kneller
• Using getopt to parse multi-argument options   Daniel R. Levy
• "C" Interpreter   Bill Cramer
• Survey of "duplicate case in switch" errors   chase at orc.olivetti.com
• portability   Bob Larson
• Playing with the bits of floats   Billy G. Allie
• system() always returns 0?   Derek E. Terveer
• Behaviour of setjmp/longjmp and registers   Steve Summit
• Turbo C bug !   Tommy Levitte
• Passing variable #of args   Doug Gwyn
• portability   Doug Gwyn
• using floats in functional prototypes   Doug Gwyn
• Problem with strange macro definition   Jay M. Libove
• new Quick C "2" ?   Dean Roth
• Microsoft C 5.1 question   Scott "The Pseudo-Hacker" Neugroschl
• ANSI C Texts   Forrest Gehrke
• The One True Purpose of C (was Playing with the bits of floats)   Chris Torek
• Behaviour of setjmp/longjmp and registers   96 more school days
• Playing with the bits of floats   Doug Gwyn
• portability   Doug Gwyn
• Catching DOS interrupt 24H (critical error handler)   Mark Freedman
• Addresses of static versus auto variables   Kenneth Almquist
• Using getopt to parse multi-argument options   Henry Spencer
• Passing variable #of args   Henry Spencer
• Optimization bug in GCC V1.32 on BIG_ENDIAN machines   Jon Olson
• Microsoft C 5.1 question   Kenneth Almquist
• Behaviour of setjmp/longjmp and registers   Andrew Koenig
• Microsoft C 5.1 question   Andrew Koenig
• TC2.0 bugfree ?   Scott "The Pseudo-Hacker" Neugroschl
• Optimization bug in GCC V1.32 on BIG_ENDIAN machines   Devon E Bowen
• portability   Doug Gwyn
• Behaviour of setjmp/longjmp and registers   Doug Gwyn
• Behaviour of setjmp/longjmp and registers   Henry Spencer
• Behaviour of setjmp/longjmp and registers   Jim Shankland
• Behaviour of setjmp/longjmp and registers   101 more school days
• BIT Counting: C programming problem   Eric Robert Jablow
• using floats in functional prototypes   Geoff Rimmer
• Wanted - Auto function prototype generator   Geoff Rimmer
• Passing variable #of args   Ge Weijers
• Behaviour of setjmp/longjmp and registers   Geoff Rimmer
• Flat ASCII File Data Access   mcdonald at uxe.cso.uiuc.edu
• Yet another pcc botch   David Goodenough
• Green-Hills C compiler   Andrew Duane
• How poke in Quick-C to PC memory ?   aring at bmc.uu.se
• C Style   Leo de Wit
• Behaviour of setjmp/longjmp and registers   David F. Carlson
• Behaviour of setjmp/longjmp and registers   Henry Spencer
• portability   Henry Spencer
• Behaviour of setjmp/longjmp and registers   Gordon Cross
• using floats in functional prototypes   Jeff Siegal
• static versus auto initialization   Bob Devine
• Survey of "duplicate case in switch" errors   Dave Hollenbeck
• Turbo C bug !   Doug Gwyn
• static versus auto initialization   Blair P. Houghton
• Duplicate case labels problem (VMS does it right)   John Hascall
• The One True Purpose of C (was Playing with the bits of floats)   Blair P. Houghton
• Braces are not Compiler-Fluff.   flint at gistdev.UUCP
• Turbo C bug !   Norman Diamond
• What is wrong?   James Mork
• turbo c 2.0   The Polymath
• Scientific C style choices (+ example of MY coding standard)   James Logan III
• spiffy terminals (was: printf, data presentation)   Bill Stewart, usually
• static versus auto initialization   dmr at alice.UUCP
• system() always returns 0?   Joe English
• Using getopt to parse multi-argument options   John Woods
• Behaviour of setjmp/longjmp and registers   96 more school days
• Looking for Microsoft Windows developer's library   Jim Boritz
• Behaviour of setjmp/longjmp and registers   Chris Torek
• curses for the pc   Gordon Howell
• Would *you* get caught by this one?   G. Levine
• system() always returns 0?   Mark Alexander
• Behaviour of setjmp/longjmp and registers   Paul Gluckauf Haahr
• How is *this* for exception handling?   Stephen J. Friedl
• static versus auto initialization   Guy Harris
• system() always returns 0?   Brent K. Barrett
• Programming gems (Bit-reversed counting)   Dan Hoey
• Wanted - Auto function prototype generator   Jonathan Leech
• Yet another pcc botch   Lawrence V. Cipriani
• system() always returns 0?   Wietse Z. Venema
• Survey of "duplicate case in switch" errors   Jeffrey E. F. Friedl
• static versus auto initialization   Doug Gwyn
• What is wrong?   Andrew Koenig
• What is wrong?   Doug Gwyn
• Behaviour of setjmp/longjmp and registers   Wonderly
• What is wrong?   RAMontante
• BIT Counting: C programming problem   Matt Landau
• system() always returns 0? Yep...   RAMontante
• `va_dcl' macro question   Maarten Litmaath
• Yet another pcc botch   Chris Torek
• Address error quietly fixed on 680x0 systems   Ian Wilson
• Survey of "duplicate case in switch" errors   Frank Wales
• Undocumented options for command.com   Simon Gales
• What is wrong?   Mark A. Charette
• Behaviour of setjmp/longjmp and registers   Chris Torek
• HASHING, revisited - A summary.   Ray Dunn
• Behaviour of setjmp/longjmp and registers   Tim Olson
• system() always returns 0?   Ray Berry
• What is wrong?   Bill Svirsky
• Behaviour of setjmp/longjmp and registers   Andrew Koenig
• Problem with strange macro definition   Ray Butterworth
• BIT Counting: C programming problem   Blair P. Houghton
• system() always returns 0?   Walter Bright
• Yet another pcc botch   shirono at hcx3.SSD.HARRIS.COM
• What is wrong?   David Goodenough
• Catching DOS interrupt 24H (critical error handler)   Nick Mason
• BIT Counting: C programming problem   Dave Jones
• cast question.   Dahe Chen
• "for" loops (was Re: C++ vs. Modula2)   stepanek/cs assoc
• Flat ASCII File Data Access   Brad Brown
• Microsoft C 5.1 question   michael k finegan
• Behaviour of setjmp/longjmp and registers   94 more school days
• BIT Counting: C programming problem   Andrew Hume
• Yet another pcc botch   Norman Diamond
• system() always returns 0?   Earl H. Kinmonth
• Yet another pcc botch   Chris Torek
• system() always returns 0?   Steve Mawer
• turbo c 2.0   Mark H. Colburn
• Results of duplicate-case-in-nested-switch survey   chase at orc.olivetti.com
• gcc vs. commercial C compiler (Sun's)   Harold C.
• Microsoft C 5.1 question   Scott Garfinkle
• Behaviour of setjmp/longjmp and registers   93 more school days
• What is wrong?   Tim Meighan
• turbo c 2.0   Eric Schwarz
• Behaviour of setjmp/longjmp and registers   Ray Butterworth
• NULL is not '\0' (was: Is malloc() or calloc() "better"?)   Jean-Pierre Radley
• Flat ASCII File Data Access   Michael Paul Hunter
• Behaviour of setjmp/longjmp and registers   Robert Claeson
• Behaviour of setjmp/longjmp and registers   Charles Bryant
• `va_dcl' macro question   Doug Gwyn
• passing variable numbers of arguments   Karl Heuer
• Behavior of setjmp/longjmp and registers   d.a.morano
• using floats in functional prototypes   Karl Heuer
• What is wrong?   Bill Svirsky
• turbo c 2.0   Paul Connors
• where do you put prototype declarations?   Pete Holsberg
• Use of " ? : " in format param to printf   David Sherman
• BIT Counting: C programming problem   Joe English
• NULL is not '\0'   Doug Gwyn
• gcc vs. commercial C compiler (Sun's)   Stephen J. Friedl
• "for" loops (was Re: C++ vs. Modula2)   John Hascall
• "for" loops (was Re: C++ vs. Modula2)   Jeff A. Bowles
• Something new in C syntax   C. Allen Grabert
• Flat ASCII File Data Access   mcdonald at uxe.cso.uiuc.edu
• varargs and scanf   Victor Gavin
• return value of free   Walter Bright
• Thanks.   Dahe Chen
• "for" loops (was Re: C++ vs. Modula2)   Dave Seaman
• gcc vs. commercial C compiler (Sun's)   Clayton Cramer
• String Constant Concatenation in MPW (ANSI) C   Peter Desnoyers
• Include files   Vijay Raghavan
• "for" loops (was Re: C++ vs. Modula2)   Ken Arromdee
• "for" loops (was Re: C++ vs. Modula2)   Jim Giles
• for t in table (was Re: "for" loops (was Re: C++ vs. Modula2))   Dave Jones
• Include files   Juergen Wagner
• Something new in C syntax   Dave Jones
• "for" loops   Doug Gwyn
• where do you put prototype declarations?   Doug Gwyn
• "for" loops   Doug Gwyn
• Something new in C syntax   Doug Gwyn
• String Constant Concatenation in MPW (ANSI) C   Doug Gwyn
• return value of free   Doug Gwyn
• Include files   Doug Gwyn
• "for" loops   Doug Gwyn
• "for" loops (was Re: C++ vs. Modula2)   Roger Crew
• Address error quietly fixed on 680x0 systems   Guy Harris
• "for" loops (was Re: C++ vs. Modula2)   Guy Harris
• Something new in C syntax   Chris Torek
• Behaviour of setjmp/longjmp and registers   Doug Gwyn
• malloc impossible? (unions)   der Mouse
• malloc impossible? (unions)   Doug Gwyn
• Catching DOS interrupt 24H (critical error handler)   Victor Gavin
• Microsoft C 5.1 question   Brandon S. Allbery
• Include files   Vijay Raghavan
• "for" loops (was Re: C++ vs. Modula2)   Devin_E_Ben-Hur at cup.portal.com
• Address error quietly fixed on 680x0 systems   Bob Larson
• "for" loops (was Re: C++ vs. Modula2)   stepanek/cs assoc
• "for" loops   Jim Giles
• How poke in Quick-C to PC memory ?   Daniel E. Platt
• Address error quietly fixed on 680x0 systems   RAMontante
• curses for the pc   Jeff Dean
• ANSI "include" files?   RAMontante
• "%02d" vs "%.2d"   Chris Torek
• Something new in C syntax   mue at ugun21.UUCP
• "for" loops   Chris Torek
• "for" loops (was Re: C++ vs. Modula2)   Doug Schmidt
• "for" loops (was Re: C++ vs. Modula2)   T. William Wells
• gcc vs. commercial C compiler (Sun's)   Sean Fagan
• Include files   Juergen Wagner
• "for" loops (was Re: C++ vs. Modula2)   Norman Diamond
• Something new in C syntax   Norman Diamond
• Include files   Norman Diamond
• BIT Counting: C programming problem   Eric Robert Jablow
• variable limits (was Re: "for" loops)   T. William Wells
• uustatus - realtime uustat for HDB uucp (w/findpath)   Greg Woods
• "for" loops (was Re: C++ vs. Modula2)   John Woods
• Include files   Bob Larson
• binary stdin/stdout   John Stanley
• "for" loops (was Re: C++ vs. Modula2)   Frans van Otten
• Turbo C & qsort()   Scott W. Leonard
• uustatus - realtime uustat for HDB uucp (w/findpath)   William E. Davidsen Jr
• malloc hangs indefinitely   Dave Hammond
• NULL is not '\0'   William E. Davidsen Jr
• "for" loops (was Re: C++ vs. Modula2)   David Goodenough
• gcc vs. commercial C compiler (Sun's)   Lawrence V. Cipriani
• uustatus - realtime uustat for HDB uucp (w/findpath)   Ed Carp
• Behaviour of setjmp/longjmp and registers   Michael Meissner
• Laplace and Fourier Tansform package   Bruce A. Kern
• "for" loops (was Re: C++ vs. Modula2)   Barry Margolin
• List of 'C' keywords   Peter da Silva
• "%02d" vs "%.2d"   Kenneth Almquist
• gcc vs. commercial C compiler (Sun's)   Cris Simpson
• cast question   James R Drinkwater
• Strange cc warning   Dave Hammond
• gcc vs. commercial C compiler (Sun's)   Lawrence V. Cipriani
• uustatus - realtime uustat for HDB uucp (w/findpath)   Sanford 'Sandy' Zelkovitz
• C is not superfluous (Re: "for" loops (was Re: C++ vs. Modula2))   Dave Jones
• data types   Tom Middleton
• How poke in Quick-C to PC memory ?   James Buster
• shared memory   Michael Paul Hunter
• malloc hangs indefinitely   Earl H. Kinmonth
• uustatus - realtime uustat for HDB uucp (w/findpath)   Greg Woods
• "for" loops (was Re: C++ vs. Modula2)   Robert Marti
• Include files   Doug Gwyn
• binary stdin/stdout   Doug Gwyn
• malloc hangs indefinitely   Doug Gwyn
• Something new in C syntax   Doug Gwyn

Last message date: Tue Jan 31 17:58:19 AEST 1989
Archived on: Mon Feb 1 19:33:10 AEST 2016

• Messages sorted by: [ thread ] [ subject ] [ author ]