May 1988 Archives by date

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

Starting: Sun May 1 00:53:38 AEST 1988
Ending: Tue May 31 15:38:43 AEST 1988
Messages: 689

• Useful macro...or dangerous??   gordan
• const void *   Doug Gwyn
• gotos   Chris Torek
• Noalias trivia question   Doug Gwyn
• Is &a[NTHINGS] legal   Doug Gwyn
• volatile (in comp.lang.c)   Eugene D. Brooks III
• Is &a[NTHINGS] legal   Chris Torek
• Noalias trivia question   Larry Jones
• Alignment [was Re: Optimization, volatile]   Tim Olson
• Turbo C's fscanf()   Michael J. Schmelzer
• Put your code... (was Re: gotos   Henry Spencer
• gotos   Henry Spencer
• State Machines, The Ultimate Goto   Richard Harter
• Noalias trivia question   Theodore Stevens Norvell
• volatile (in comp.lang.c)   John Mashey
• Command line as a stream?   Barry Margolin
• marketing vs. demerit   Rahul Dhesi
• Joystick handler routines needed.   Julius A Cisek
• Source level debugger wanted.   Julius A Cisek
• Is &a[NTHINGS] legal   Daniel R. Levy
• optimization (was Re: volatile)   SuperUser
• discrete-event simulation package in c or c++?   Gideon Yuval
• C--   Chris Torek
• Vector operations   Chris Torek
• State Machines, The Ultimate Goto   Herman Rubin
• The Journal of Object-Oriented Programming   David Collier-Brown
• CURSES package for Atari ST   Barnacle Wes
• CURSES package for Atari ST   Barnacle Wes
• Source level debugger wanted.   A1 jeff giordano
• gotos   Daniel R. Levy
• Re^3: gotos   Brian T. Schellenberger
• Is there an ACK backend for the PDP-11?   Barnacle Wes
• Is &a[NTHINGS] legal   Theodore Stevens Norvell
• arrays...   Frank Swarbrick
• unsigned comparsions   Chris Torek
• Put your code... (was Re: gotos   Barnacle Wes
• Question about use of enum in typedef and struct   Barnacle Wes
• Is &a[NTHINGS] legal   Chris Torek
• volatile (in comp.lang.c)   Bill.Stewart.<ho95c>
• A tale of two C's.   Brian T. Schellenberger
• CURSES package for Atari ST   Julius A Cisek
• State Machines, The Ultimate Goto   Richard Harter
• volatile (in comp.lang.c)   David Collier-Brown
• State Machines, The Ultimate Goto   Lee Sailer
• Put your code... (was Re: gotos   David Goodenough
• C--   SIEMON
• Is there any reader on my FIFO ?   Kim Chr. Madsen
• #pragma volatile   Wayne A. Throop
• Question about use of enum in typedef and struct   Wayne A. Throop
• Indexing vs pointers   Craig Schmackpfeffer
• Useful macro...or dangerous??   Brian Matthews
• cdecl keyword   Markku Savela
• unsigned comparsions   SuperUser
• Indexing vs pointers   Walter Bays
• volatile (in comp.lang.c)   David Collier-Brown
• X3J11 response to comments (was: Block Closure)   Shankar Unni
• cdecl keyword and flames   Ray Dunn
• X3J11 response to comments (was: Block Closure)   Henry Spencer
• Help me cast this!   Bill Daniels
• Hello! am at computer-lab.cambridge.ac.uk   Dave Jones
• A tale of two C's.   Richard A. O'Keefe
• Toy compilers (was Re: gotos)   Larry Campbell
• A different view of volatile   Brian T. Schellenberger
• CURSES package for Atari ST   Guy Harris
• gotos   Brian T. Schellenberger
• CURSES package for Atari ST   Pete Schmitt
• arrays...   Chris Torek
• X3J11 response to comments (was: Block Closure)   Mark E. Mallett
• Optimization (was Re: volatile)   Mark E. Mallett
• Is &a[NTHINGS] legal (and the shim)   Dick Dunn
• Help me cast this!   Stephen J. Friedl
• Help me cast this!   Alan Myrvold
• UUCP over SunLink X.25   Bob Sutterfield
• arrays...   Craig Schmackpfeffer
• Optimization (was: Re^3: gotos)   Doug Gwyn
• A tale of two C's.   Doug Gwyn
• A tale of two C's.   Doug Gwyn
• Help me cast this!   Doug Gwyn
• Help me cast this!   Chris Torek
• Is &a[NTHINGS] legal (and the shim)   Chris Torek
• 5th International Obfuscated C Code Contest Rules - Repost   Landon Curt Noll
• X3J11 response to comments (was: Block Closure)   Mike Coffin
• CURSES package for Atari ST   Julius A Cisek
• Optimization, volatile (was Re: volatile)   Rob McMahon
• arrays...   Rich Salz
• UUCP over SunLink X.25   Rick Adams
• Thank Ghod, the noalias wars are over!   Eric S. Raymond
• Noalias trivia question   Walter Bays
• Toy compilers (was Re: gotos)   Robert Firth
• Bug in cpp (4.1BSD, 2.9BSD)   William E. Davidsen Jr
• Optimization (was Re: volatile)   Ray Dunn
• Availability of comp.std.c   Karl Heuer
• cdecl keyword and flames   Rahul Dhesi
• X3J11 response to comments (was: Block Closure)   Barry Margolin
• Keywords and optimization   Ray Dunn
• Help me cast this!   Bob Henderson
• gotos   Peter J Desnoyers
• Is &a[NTHINGS] legal   Carl Paukstis
• Help me cast this!   Carl Paukstis
• A tale of two C's.   00704a-Liber
• State Machines, The Ultimate Goto   00704a-Liber
• Help me cast this!   Greg Limes
• Optimization (was Re: volatile)   00704a-Liber
• A different view of volatile   mikew at wyse.wyse.com
• arrays...   Larry Jones
• But what about kernel printfs?   Lawrence V. Cipriani
• UUCP over SunLink X.25, unbundled products   Carl S. Gutekunst
• Help me cast this!   Chris Torek
• Help me cast this!: Ultrix 2.x bug   Chris Torek
• Noalias trivia question   Michael R. DeCorte
• Optimization, volatile (was Re: volatile)   Arthur David Olson
• gotos   Dave Burton
• Optimization (was Re: volatile)   Chip Salzenberg
• CURSES package for Atari ST   Barnacle Wes
• Help me cast this!   Walter Murray
• volatile (in comp.lang.c)   John R. Levine
• volatile, noalias and optimization   Ray Dunn
• Help me cast this!   Larry Miller
• X3J11 response to comments   Peter J Desnoyers
• Is &a[NTHINGS] legal   William E. Davidsen Jr
• X3J11 response to comments (was: Block Closure)   William E. Davidsen Jr
• Indexing vs pointers   Walter Bright
• But what about kernel printfs?   Doug Gwyn
• Is &a[NTHINGS] legal   Doug Gwyn
• Noalias trivia question   Doug Gwyn
• X3J11 response to comments   Doug Gwyn
• arrays...   Andrew Scott
• Optimization (was Re: volatile)   Henry Spencer
• Help me find a hidden connection   Mark D. Freeman
• Optimization, volatile (was Re: volatile)   Rahul Dhesi
• X3J11 response to comments (was: Block Closure)   Henry Spencer
• Help me cast this!   Henry Spencer
• Bug in new K&R?   mcdaniel at uicsrd.csrd.uiuc.edu
• How constant is "const"?   mcdaniel at uicsrd.csrd.uiuc.edu
• Put your code... (was Re: gotos   Dave Jones
• I'm not sure comp.std.c is worthwhile   Rich Salz
• Help me cast this!: Ultrix 2.x bug   SuperUser
• Journal of Object-Oriented Programming -- subscription info   ark at alice.UUCP
• volatile   John Woods
• Optimization, volatile (was Re: volatile)   Stephen J. Friedl
• Optimization (was Re: volatile)   Stephen J. Friedl
• A tale of two C's.   Richard A. O'Keefe
• But what about kernel printfs?   Marc R.S. Chang Sing Pang
• A tale of two C's.   Richard A. O'Keefe
• Help me cast this!   Niels J|rgen Kruse
• Referencing through a null pointer   Lars Henrik Mathiesen
• Alignment in C - it's simple   Mike O'Dell
• Is &a[NTHINGS] legal   David Collier-Brown
• $99 C++ compiler   Ashok P. Nadkarni DTN 226-7448
• volatile (in comp.lang.c)   Ray Dunn
• volatile (in comp.lang.c)   mcdonald at uxe.cso.uiuc.edu
• X3J11 response to comments (was: Block Closure)   Doug Gwyn
• Is &a[NTHINGS] legal   Brian R. Bainter
• A different view of volatile   Chris Torek
• A different view of volatile   00704a-Liber
• Implementation-DEPENDENT code (was:strcpy)   Jim Patterson
• Noalias trivia question   Henry Spencer
• Is &a[NTHINGS] legal   Henry Spencer
• X3J11 response to comments (was: Block Closure)   Henry Spencer
• Optimization (was Re: volatile)   Dave Cornutt
• Indexing vs pointers   Michael Ryan
• Malloc problems   Dave Hammond
• Noalias trivia question   Wayne A. Throop
• X3J11 response to comments   Peter J Desnoyers
• Is &a[NTHINGS] legal   Brad Daniels
• Optimization, volatile (was Re: volatile)   Greg Limes
• X3J11 response to comments (was: Block Closure)   Richard A. O'Keefe
• But what about kernel printfs?   00704a-Liber
• X3J11 response to comments (was: Block Closure)   Kent Forschmiedt
• UUCP over SunLink X.25   Joe Angelo
• Help me cast this!   John F. Haugh II
• Help me cast this!: Ultrix 2.x bug   Chris Torek
• A different view of volatile   Bjorn Engsig
• arrays...   David Collier-Brown
• Optimization, volatile (was Re: volatile)   Wayne A. Throop
• discrete-event simulation package in c or c++?   bs at alice.UUCP
• Help me cast this!   Henry Spencer
• Referencing through a null pointer   Henry Spencer
• Help me cast this!   paul pedersen
• A different view of volatile   Henry Spencer
• C Style (Was Re: == vs =)   hutchson at convex.UUCP
• Help me cast this!   Doug Gwyn
• X3J11 response to comments (was: Block Closure)   Doug Gwyn
• Is &a[NTHINGS] legal   Carl Paukstis
• Indexing vs pointers   Walter Bright
• Is &a[NTHINGS] legal   Greg Limes
• But what about kernel printfs?   Greg Limes
• Bug in cpp (4.1BSD, 2.9BSD)   Maarten Litmaath
• sets in C   Frank Swarbrick
• "recursive" function prototype?   Bakul Shah
• A different view of volatile   Dr. T. Andrews
• anonymous functions   Chris Torek
• But what about kernel printfs?   Richard A. O'Keefe
• Help me cast this!   Richard A. O'Keefe
• Is &a[NTHINGS] legal   Chris Torek
• $99 C++ compiler   Wolf N. Paul
• State Machines (was Re: gotos)   Peter da Silva
• Bug in new K&R?   Chris Torek
• Handling deep breaks   Peter da Silva
• Optimization, volatile (was Re: volatile)   Rob McMahon
• Indexing vs pointers (Datalight Optimizer)   Joseph Reger
• Is &a[NTHINGS] legal   Doug Gwyn
• Bug in new K&R?   Doug Gwyn
• 407 magic number (was: Referencing through a null pointer)   Doug Gwyn
• Bug in new K&R?   Henry Spencer
• Is there any reader on my FIFO ?   Leslie Mikesell
• discrete-event simulation package in c or c++?   Dave Jones
• disabling interrupts under OS-9   Bob Babcock
• Expanding user functions inline   pls at cup.portal.com
• Is &a[NTHINGS] legal   Richard Hargrove
• A different view of volatile   Chris Torek
• State Machines, The Ultimate Goto   Richard Harter
• Indexing vs pointers   Markku Savela
• longjmp() over several stacks   David Keppel
• Bug in new K&R?   dmr at alice.UUCP
• Tenne-c New C Compiler   Steven Vore
• arrays...   David Goodenough
• volatile (in comp.lang.c)   Ray Dunn
• drystone (sp?) benchmark, version 2.0   Peter Bumbulis
• volatile (in comp.lang.c)   Dieter Woerz
• Bug in new K&R?   Doug Gwyn
• Help me cast this!: Ultrix 2.x bug   SuperUser
• anonymous functions   SuperUser
• Bug in new K&R?   Henry Spencer
• Function prototyping   Wayne A. Christopher
• free()   Michael J. Schmelzer
• free()   Richard Harter
• Fancy preprocessor stuff   William E. Davidsen Jr
• Bug in new K&R?   Ed Nather
• X3J11 response to comments (was: Block Closure)   David E. Bakken
• free()   Michael J. Schmelzer
• Optimization (really .sig flame)   Dave Sill
• Help me cast this!: Ultrix 2.x bug   Guy Harris
• Bug in new K&R?   Stan Switzer
• anonymous functions   Chris Torek
• Help me cast this!: Ultrix 2.x bug   Chris Torek
• Variable argument lists.   Cary Bates
• flex   John Campbell
• negative addresses   Tim Olson
• C Cross Compiler for NSC 32000 on a 68000 host wanted   Hilkka Zirkle
• Variable argument lists.   Doug Gwyn
• Variable argument lists.   Chris Torek
• anonymous functions   Wayne A. Throop
• $99 C++ compiler   Jeffrey J Wieland
• Variable argument lists.   Joseph Nathan Hall
• v14i090: New version of Cdecl, parse C declarations, Part01/02   Rich Salz
• Variable argument lists.   Lawrence V. Cipriani
• Variable argument lists.   Richard Harter
• Variable argument lists.   Lawrence V. Cipriani
• Variable argument lists.   ark at alice.UUCP
• Variable argument lists.   Bob Fisher
• Is &a[NTHINGS] legal   Jim Patterson
• Bug in new K&R?   Doug Gwyn
• Datalight Optimizer   REED CHRISTIANSEN
• Help me cast this!   Lars Henrik Mathiesen
• volatile (in comp.lang.c)   John R. Levine
• Help me cast this!: Ultrix 2.x bug   William E. Davidsen Jr
• Variable argument lists.   Scott Daniels
• Variable argument lists.   Peter J Desnoyers
• Args: var number & var types   Justin Chris Vallon
• Bug in new K&R?   Rahul Dhesi
• A different view of volatile   Ray Dunn
• flex   Larry Jones
• Help me cast this!: Ultrix 2.x bug   Tom Karzes
• volatile (in comp.lang.c)   00704a-Liber
• Noalias trivia question   Karl Heuer
• #defines with variable # arguments   Lawrence V. Cipriani
• recursive typedefs   Eric McQueen
• Casting |void *| values (was: Help me cast this!)   Karl Heuer
• Bug in new K&R?   D. Hugh Redelmeier
• Variable argument lists.   Chris Torek
• volatile   Chris Torek
• volatile   Doug Gwyn
• Args: var number & var types   Doug Gwyn
• volatile (in comp.lang.c)   mcdonald at uxe.cso.uiuc.edu
• Flex on MSDOS and C block structure   Charles Marslett
• Variable argument lists.   Andrew Scott
• Args: var number & var types   Joseph Nathan Hall
• negative addresses   Henry Spencer
• Bug in new K&R?   Henry Spencer
• Variable argument lists.   Henry Spencer
• Variable argument lists.   Henry Spencer
• Optimization (really .sig flame)   walter at garth.UUCP
• Optimization (was Re: volatile)   Dave Sill
• new Object Oriented Design book   Dave Yost
• Args: var number & var types   carroll at snail.CS.UIUC.EDU
• Args: var number & var types   Chris Torek
• Args: var number & var types   Karl Heuer
• Variable argument lists.   Karl Heuer
• How would you design a new a.out format?   Bruce Perens
• How would you design a new a.out format?   Bruce Perens
• comments before preprocessor directives   Paul Gluckauf Haahr
• Variable argument lists.   Richard A. O'Keefe
• Variable argument lists.   John F. Haugh II
• Challenge program.   Greg F. Shay
• new Object Oriented Design book   Pete Turner
• Bug in new K&R?   Ed Nather
• Malloc problems   John Kessenich
• Variable argument lists.   Karl Heuer
• Help me cast this!   Karl Heuer
• Help me cast this!: Ultrix 2.x bug   Wayne A. Throop
• Optimization (really .sig flame)   Wayne A. Throop
• ANSI C to pre-ANSI translator   Phil Hughes
• negative addresses   Doug Gwyn
• A different view of volatile   Doug Gwyn
• How would you design a new a.out format?   Doug Gwyn
• Variable argument lists.   Brian T. Schellenberger
• Variable argument lists.   Henry Spencer
• Args: var number & var types   Henry Spencer
• Variable argument lists.   Scott Daniels
• CURSES package for Atari ST   Every system needs one
• New version of getopt()   Lloyd Zusman
• Alignment [was Re: Optimization, volatile]   Every system needs one
• volatile   Every system needs one
• Optimization, volatile (was Re: volatile)   Every system needs one
• gotos   Every system needs one
• optimization (was Re: volatile)   Every system needs one
• Noalias trivia question   Every system needs one
• Variable argument lists.   John F. Haugh II
• volatile (in comp.lang.c)   Dieter Woerz
• Bug in new K&R?   Doug Gwyn
• The 8259 interrupt controller (HELP!)   Bob Argyle
• Flex on MSDOS and C block structure   Henry Spencer
• Variable argument lists.   Doug Gwyn
• Malloc problems   Doug Gwyn
• Interprocess Communication && Multiple threads of execution   USENET News System
• evolution by committee   Ed Nather
• negative addresses   Henry Spencer
• evolution by committee   Doug Gwyn
• volatile (in comp.lang.c)   Peter J Desnoyers
• Help needed with #include problems   john at ntvax.UUCP
• ANSI C to pre-ANSI translator   It takes a clear mind to make it
• comments before preprocessor directives   Henry Spencer
• Variable argument lists.   Henry Spencer
• Variable argument lists.   Jan Gray
• Bug in new K&R?   Barnacle Wes
• A different view of volatile   der Mouse
• Optimization (was Re: volatile)   der Mouse
• But what about kernel printfs?   der Mouse
• State Machines (was Re: gotos)   der Mouse
• negative addresses   == M. Yuhara ==
• Variable argument lists.   John F. Haugh II
• Flex on MSDOS and C block structure   David Collier-Brown
• Malloc problems   Stephen Spencer
• A different view of volatile   David Collier-Brown
• Appreciation for ANSI C committee (was Re: Bug in new K&R?)   T. William Wells
• Variable argument lists.   Robert Firth
• static functions broken in non-Unix compilers?   John F. Haugh II
• Is &a[NTHINGS] legal   Peter da Silva
• Variable argument lists.   Wayne A. Christopher
• evolution by committee   Wayne A. Christopher
• negative addresses   Karl Heuer
• volatile   Karl Heuer
• C++ compiler   Baart Rene
• But what about kernel printfs?   Greg Noel
• printf vs fprintf   Gregory Conway
• Toy compilers (was Re: gotos)   Every system needs one
• Optimization (was Re: volatile)   Every system needs one
• Optimization (was Re: volatile)   Every system needs one
• Optimization, volatile (was Re: volatile)   Every system needs one
• Optimization (was Re: volatile)   Every system needs one
• Malloc problems   Every system needs one
• Optimization (really .sig flame)   Every system needs one
• CURSES package for Atari ST   Doug Gwyn
• Portability and BS   Chris Torek
• volatile   Chris Torek
• Variable argument lists.   Robert Firth
• Variable argument lists.   Frank Adams
• SPARC (was: Re: Alignment [was Re: Optimization, volatile])   Jim Shankland
• State Machines (was Re: gotos)   kenny at uiucdcsm.cs.uiuc.edu
• volatile   Mike Mahar
• negative addresses   Andrew Klossner
• Malloc problems   Henry Spencer
• line buffering   James Jones
• Address arithmetic on the '286 (was: Is &a[NTHINGS] legal)   Chip Salzenberg
• printf vs fprintf   Pete Holsberg
• But what about kernel printfs?   doug-merritt at cup.portal.com
• But what about kernel printfs?   doug-merritt at cup.portal.com
• Structures as status variables.   Cary Bates
• How do I get printf to move to a tab position?   John W. Fawcett
• volatile   Daniel R. Levy
• recursive typedefs   Eric McQueen
• volatile   Chris Torek
• Help needed with #include problems   Frank Swarbrick
• Alignment [was Re: Optimization, volatile]   Richard A. O'Keefe
• Repeated instructions (was gotos)   Dave Caswell
• Variable argument lists.   der Mouse
• Bug in new K&R?   der Mouse
• negative addresses   Wayne A. Christopher
• volatile   der Mouse
• Evaluating ANSI C   dmr at alice.UUCP
• Optimization, volatile (was Re: volatile)   der Mouse
• optimization (was Re: volatile)   der Mouse
• Help needed with #include problems   der Mouse
• negative addresses   der Mouse
• Bug in new K&R?   David Collier-Brown
• Appreciation for ANSI C committee (was Re: Bug in new K&R?)   Michael J. Young
• volatile   Doug Gwyn
• negative addresses   Doug Gwyn
• negative addresses   Doug Gwyn
• line buffering   Doug Gwyn
• arrays...   Peter da Silva
• Anonymous Functions.   Peter da Silva
• volatile (in comp.lang.c)   T. William Wells
• negative addresses   Tim Olson
• static functions broken in non-Unix compilers?   Jeff Beard
• Portability and BS   William E. Davidsen Jr
• recursive typedefs   William E. Davidsen Jr
• volatile   Steven Ryan
• recursive typedefs   Tom Karzes
• Casting function ptrs   Dave Hammond
• Style Rules   Greg Lomow
• negative addresses   Stan Friesen
• But what about kernel printfs?   Eric Black
• Appreciation for ANSI C committee (was Re: Bug in new K&R?)   Karl Heuer
• volatile   Chris Torek
• Portability and alignment constraints   Chris Torek
• Bug in new K&R?   George W. Leach
• Help needed with #include problems   452is-Connet
• Malloc problems   brian at bucc2.UUCP
• Casting function ptrs   Chris Torek
• The 8259 interrupt controller (HELP!)   William E. Davidsen Jr
• But what about kernel printfs?   Colin Kendall
• anonymous functions   Peter da Silva
• anonymous functions   Peter da Silva
• How do I get printf to move to a tab position?   Chris Torek
• Portability and BS   hutchson at convex.UUCP
• SPARC and portability   Henry Spencer
• single character input   Kral
• negative addresses   Henry Spencer
• Malloc problems   Badri Lokanathan
• volatile   T. William Wells
• C COMPILER FOR IBM MAINFRAME   Chuck Hoff
• negative addresses   Philip Kos
• gotos   T. William Wells
• Noalias trivia question   T. William Wells
• C Profiler Wanted   Susan Micciche
• flex   Bill.Stewart.<ho95c>
• negative addresses (real C null pointers)   Radford Neal
• Casting function ptrs   Dave Jones
• C COMPILER FOR IBM MAINFRAME   Craig Ruff
• UUCP over SunLink X.25   Bob Toxen
• trigraphs in X3J11   Dick Dunn
• But what about kernel printfs?   William Sommerfeld
• volatile (in comp.lang.c)   Stephen Crawley
• Variable argument lists.   John F. Haugh II
• Variable argument lists.   Ken Raeburn
• But what about kernel printfs?   Heather Mackinnon
• C Profiler Wanted   Doug Gwyn
• trigraphs in X3J11   Doug Gwyn
• negative addresses   Dieter Woerz
• printf vs fprintf   Jesse Perry
• single character input   Peter J Desnoyers
• static functions broken in non-Unix compilers?   John F. Haugh II
• volatile   ~XT4103000~Marc Mengel~C25~G25~6184~
• Alignment issues and SPARC (commentary)   Gary Wisniewski
• Is &a[NTHINGS] legal   Tom Neff
• Question about regrouping of operands   Ray Butterworth
• volitile   Ray Butterworth
• Casting function ptrs   Walter Murray
• Help needed with #include problems   Lloyd Zusman
• C Profiler Wanted   Rick Adams
• Variable argument lists.   Ray Dunn
• C COMPILER FOR IBM MAINFRAME   schwartz at swatsun.UUCP
• trigraphs in X3J11   Alan Mimms
• trigraphs in X3J11   Chuck Harris
• magic cookies given back by ftell, and used in fseek   David Goodenough
• volatile   smryan at garth.UUCP
• Address arithmetic on the '286 (was: Is &a[NTHINGS] legal)   Dick Dunn
• Variable argument lists.   00704a-Liber
• Help needed with #include problems   vlcek at mit-caf.UUCP
• no noalias not negligible - a difference between C and Fortran - long   dgh at dgh.UUCP
• trigraphs in X3J11   Joe Beckenbach
• no noalias not negligible (long)   Chris Torek
• no noalias not negligible   Chris Torek
• C COMPILER FOR IBM MAINFRAME   Daniel Senie
• line buffering   Roland McGrath
• line buffering   Roland McGrath
• Anonymous Functions.   Roland McGrath
• static functions broken in non-Unix compilers?   Richard Harter
• no noalias not negligible - a difference between C and Fortran - long   Bakul Shah
• C Profiler Wanted   Doug Gwyn
• trigraphs in X3J11   Doug Gwyn
• Help needed with #include problems   Doug Gwyn
• no noalias not negligible - a difference between C and Fortran - long   Doug Gwyn
• no noalias not negligible (long)   Doug Gwyn
• static functions broken in non-Unix compilers?   Doug Gwyn
• CURSES package for Atari ST   mcdonald at uxe.cso.uiuc.edu
• trigraphs in X3J11   mcdonald at uxe.cso.uiuc.edu
• C COMPILER FOR IBM MAINFRAME   Larry Jones
• OKAY, OKAY! ENOUGH already.   Rich Herzog
• Object-oriented techniques in C   Stephen J. Friedl
• no noalias not negligible - a difference between C and Fortran - long   ark at alice.UUCP
• C COMPILER FOR IBM MAINFRAME   Alan Myrvold
• negative addresses   Alan J Rosenthal
• Variable argument lists.   Richard A. O'Keefe
• list-add   C0042%CSUOHIO.BITNET%CUNYVM.CUNY.EDU at cunyvm.cuny.edu
• no noalias not negligible   dmr at alice.UUCP
• no noalias not negligible (long)   Paul_L_Schauble at cup.portal.com
• Style Rules   news
• text adventure   Thomas A. Dressel
• ANSI C Translation Phases   rlb
• trigraphs in X3J11   Ed Nather
• Casting function ptrs   Chris Torek
• trigraphs in X3J11   Jim Shankland
• no noalias not negligible - a difference between C and Fortran - long   Henry Spencer
• trigraphs in X3J11   Henry Spencer
• volatile (in comp.lang.c)   Henry Spencer
• no noalias not negligible (long)   Henry Spencer
• negative addresses   T. William Wells
• C COMPILER FOR IBM MAINFRAME   Richard A. O'Keefe
• Malloc problems   Ken Raeburn
• Integer Sine(x) program.   Greg F. Shay
• #pragma   Chris Torek
• Casting function ptrs   Walter Murray
• negative addresses   n
• Portability and alignment constraints   William E. Davidsen Jr
• trigraphs in X3J11   William E. Davidsen Jr
• no noalias not negligible - a difference between C and Fortran - long   Tim Olson
• Optimization (was Re: volatile)   Dave Sill
• small-c/8086 code generator wanted   Marty
• Using <SHIFT>-PrtSc with MSC graphics   Derek Morgan
• Alignment issues and SPARC (commentary)   Doug Gwyn
• #pragma   Doug Gwyn
• Help needed with #include problems   Mark Hall
• volatile, shared memory, and synchronisation   Chris Torek
• trigraphs in X3J11   Karl Heuer
• C interpreters?   Bob Pendleton
• But what about kernel printfs?   Clayton Cramer
• anonymous functions   Karl Heuer
• printf vs fprintf   Karl Heuer
• volatile, shared memory, and synchronisation   Stuart Friedberg
• no noalias not negligible   Karl Heuer
• no noalias not negligible   Dik T. Winter
• trigraphs in X3J11   Robert Lenoil
• Object-oriented techniques in C   Dave Jones
• Goto considered helpful   James D. Allen
• negative addresses   Dave Jones
• malloc schemes   Chris Torek
• trigraphs in X3J11   Jerry Schwarz
• trigraphs in X3J11   Lars Henrik Mathiesen
• Noalias trivia question   Dave Sill
• Portability and alignment constraints   Guy Harris
• C Profiler Wanted   Dennis L. Mumaugh
• no noalias not negligible - a difference between C and Fortran - long   Walter Bright
• Reserved names in X3J11 (was Re: Appreciation for ANSI C committee)   T. William Wells
• no noalias not negligible   Tom Stockfisch
• Calling C routines from Fortran programs.   Dik T. Winter
• no noalias not negligible   Wayne A. Christopher
• trigraphs in X3J11   Chris Torek
• Casting function ptrs   Chris Torek
• volatile, shared memory, and synchronisation   Robert Firth
• trigraphs in X3J11   Karl Heuer
• a.out magic numbers (was Referencing through a null pointer)   Dennis L. Mumaugh
• problem w/ DEC C 2.3 and INGRES 5.0/05   Carol Chapman
• How do I get printf to move to a tab position?   James E. Prior
• trigraphs in X3J11   Dick Dunn
• trigraphs in X3J11   Richard A. O'Keefe
• trigraphs in X3J11   Dick Dunn
• Noalias trivia question   Karl Heuer
• no noalias not negligible   Richard A. O'Keefe
• Reserved names in X3J11   Karl Heuer
• trigraphs in X3J11   William E. Davidsen Jr
• Style Rules   Ray Smith
• Alignment issues and SPARC (commentary)   Gary Wisniewski
• trigraphs in X3J11   Dick Dunn
• Calling C routines from Fortran programs.   Shankar Unni
• putting stuff in the text segment   Mike McNally
• C interpreters?   Matt Landau
• machine independent atof()   Jeffrey E. F. Friedl
• trigraphs in X3J11   Henry Spencer
• no noalias not negligible - a difference between C and Fortran - long   Niels J|rgen Kruse
• single character input   Kral
• Malloc problems   Henry Spencer
• #pragma   Henry Spencer
• trigraphs in X3J11   Henry Spencer
• trigraphs in X3J11   Henry Spencer
• trigraphs in X3J11   Richard A. O'Keefe
• C interpreters?   Mark Stevans
• An odd compiler error   Mike Peltier
• C interpreters?   Gregory Conway
• null pointers (was: negative addresses)   Mark Brader
• Color in MSC using *printf?   Derek Morgan
• putting stuff in the text segment   Guy Harris
• trigraphs in X3J11   John Limpert
• putting stuff in the text segment   Jeffrey E. F. Friedl
• magic cookies given back by ftell, and used in fseek   Dave Jones
• magic cookies given back by ftell, and used in fseek   Richard A. O'Keefe
• trigraphs in X3J11   Wayne A. Christopher
• getpass causes fprintf(stderr... not to be flushed   Darren Stalder
• Help needed with #include problems   Christoph Kuenkel
• How do I get printf to move to a tab position?   Duane L. Rezac
• putting stuff in the text segment   Dave Burton
• Color in MSC using *printf?   Dave Burton
• single character input   Dave Burton
• putting stuff in the text segment   Mike McNally
• single character input   Chris Torek
• Trigraphs -- some numbers   Rich Salz
• Using <SHIFT>-PrtSc with MSC graphics   Peter J Desnoyers
• C COMPILER FOR IBM MAINFRAME   Jeff Beard
• trigraphs in X3J11   Michael Meissner
• Zortech C++   Ashok P. Nadkarni DTN 226-7448
• Noalias trivia question   Peter J Desnoyers
• trigraphs in X3J11   Alan J Rosenthal
• trigraphs in X3J11   Doug Gwyn
• magic cookies given back by ftell, and used in fseek   William E. Davidsen Jr
• C interpreters?   Bob Pendleton
• Portability and BS   Henry Spencer
• C vs assembler   Henry Spencer
• trigraphs in X3J11   Doug Gwyn
• a.out magic numbers (was Referencing through a null pointer)   Henry Spencer
• Variable argument lists.   Doug Gwyn
• How do I get printf to move to a tab position?   Shankar Unni
• trigraphs in X3J11   Arthur David Olson
• magic cookies given back by ftell, and used in fseek   Doug Gwyn
• the D programnming language   Doug Gwyn
• putting stuff in the text segment   Stephen J. Friedl
• How stable is gcc?   Peter Galvin
• #pragma   Doug Gwyn
• magic cookies given back by ftell, and used in fseek   Karl Heuer
• ?? in existing source code   VLD/VMB
• Zortech C++   Jerry Schwarz
• Reserved names in X3J11 (was Re: Appreciation for ANSI C committee)   Jerry Schwarz
• #pragma   John Myers
• C COMPILER FOR IBM MAINFRAME   Gary Benson
• C COMPILER FOR IBM MAINFRAME   Eric Schnoebelen
• the D programnming language   Bakul Shah
• VAX (VMS) C / strangeness (serious bug?) w/ prototypes and floats   Joseph Nathan Hall
• VAX (VMS) C / strangeness (serious bug?) w/ prototypes and floats   Joseph Nathan Hall
• no noalias not negligible: more red herrings, conclusion unchanged   David Hough
• the D programnming language   Frank Swarbrick
• MSC 5.0 bug?   Cris Simpson
• Noalias trivia question   Prescott K. Turner
• volatile (in comp.lang.c)   Rob Warnock
• no noalias not negligible   Prescott K. Turner
• magic cookies given back by ftell, and used in fseek   Richard A. O'Keefe
• The high bit of a char is not a flag.   Earle R. Horton
• Reserved names in X3J11 -- Hang on folks!   Neil Winton
• Trigraphs -- some numbers   D. Hugh Redelmeier
• the D programnming language   Stephen J. Friedl
• trigraphs in X3J11   Martin Minow THUNDR::MINOW ML3-5/U26 223-9922
• Optimization (was Re: volatile)   Stuart A. Werbner
• magic cookies given back by ftell, and used in fseek   Henry Spencer
• trigraphs in X3J11   Henry Spencer
• static functions broken in non-Unix compilers?   John F. Haugh II
• Real reason for trigraphs (Re: trigraphs in X3J11)   gordan
• dialing for dollars   Grady Ward
• VAX (VMS) C / strangeness (serious bug?) w/ prototypes and floats   Joseph Nathan Hall
• magic cookies given back by ftell, and used in fseek   Chris Torek
• magic cookies given back by ftell, and used in fseek   Chris Torek
• negative addresses   T. William Wells
• Trigraphs: a program   Richard A. O'Keefe
• Trigraphs -- some numbers   Doug Gwyn
• Color in MSC using *printf?   brian at bradley.UUCP
• "%#s"?   Joe Keane
• volatile   T. William Wells
• Constants   T. William Wells
• Zortech C++   Wolf N. Paul
• The 8259 interrupt controller (HELP!)   Michael Baumann
• data in text segment and 4BSD   Chris Torek
• putting stuff in the text segment   Jeffrey E. F. Friedl
• C interpreters?   Ken Raeburn
• trigraphs in X3J11   Lars Henrik Mathiesen
• volatile   Chris Torek
• a.out magic numbers (was Referencing through a null pointer)   John F. Haugh II
• How do I get printf to move to a tab position?   Chris Torek
• no noalias not negligible: more red herrings, conclusion unchanged   Chris Torek
• "%#s"?   Chris Torek
• volatile (in comp.lang.c)   John R. Levine
• trigraphs in X3J11   Ed Nather
• Calling C routines from Fortran programs.   Henry Spencer
• "%#s"?   Henry Spencer
• putting stuff in the text segment   Guy Harris
• #pragma   Henry Spencer
• Malloc problems   T. William Wells
• Appreciation for ANSI C committee (was Re: Bug in new K&R?)   T. William Wells
• trigraphs in X3J11   T. William Wells
• Code using function prototypes   Rick Pelleg
• Motorola DSP56000   John B. Nagle
• trigraphs in X3J11   Brian T. Schellenberger
• trigraphs in X3J11   Aled Morris
• volatile (in comp.lang.c)   Ray Dunn
• the D programnming language   David Collier-Brown
• volatile (in comp.lang.c)   Stephen Crawley
• I/O implementation in C and C++   rlb
• "%#s"?   Ray Butterworth
• Zortech C++   Jerry Schwarz
• Trigraphs and Pragmas   Joe Beckenbach
• "%#s"?   Richard A. O'Keefe

Last message date: Tue May 31 15:38:43 AEST 1988
Archived on: Mon Feb 1 19:33:17 AEST 2016

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