June 1988 Archives by author

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

Starting: Wed Jun 1 00:04:34 AEST 1988
Ending: Thu Jun 30 14:49:39 AEST 1988
Messages: 506

• add to list  
• volatile (in comp.lang.c)   00704a-Liber
• Noalias trivia question   00704a-Liber
• trigraphs in X3J11   Martin Minow THUNDR::MINOW ML3-5/U26 223-9922
• #defining NULL as (-1) in stdio   Martin Minow THUNDR::MINOW ML3-5/U26 223-9922
• Using arrow keys with curses.   452is-Connet
• a reasonable approach to inlining   ZIEL FRED ADAM
• Possible bug in the SUN C compiler   William Aitken
• C Compiler bugs (was Re: Speaking of ksh)   Brandon S. Allbery
• Volatile is stupid   Pete Alleman
• Should I convert FORTRAN code to C?   Bob Allison
• Curious Behaviour of "sscanf"   Joel Anderson
• Why does C standard consider each compiler flag a separate implementation?   Dr. T. Andrews
• "Honour Parens" Rule (was: Re: Should I convert FORTRAN code to C?)   Dr. T. Andrews
• C Compiler bugs (was Re: Speaking of ksh)   Avram Aronoff
• turboc/msc spawn*   Avram Aronoff
• Help with strings   Brian R. Bainter
• I need a little advice...   Brian R. Bainter
• yacc with multiple attributes   Joe Baker
• Toy compilers (was Re: gotos)   Walter Bays
• Should I convert FORTRAN code to C?   Walter Bays
• when a core dump occurs ?   Walter Bays
• a reasonable approach to inlining   Robert Breckinridge Beatie
• when a core dump occurs ?   Joe Beckenbach
• turboc/msc spawn*   Patrick Bennett
• Should I convert FORTRAN code to C?   Jerry Berkman
• Should I convert FORTRAN code to C?   Jerry Berkman
• negative addresses   Eric Black
• Partial application in C   Jim Blandy
• Optimal structure field ordering   Jim Blandy
• Optimal structure field ordering   Jim Blandy
• Partial application in C   Art Boyne
• #defining NULL ...   Mark Brader
• when a core dump occurs ?   James Brister
• Partial application in C   Dave Brower
• Trouble with floor ()   The Beach Bum
• Need info on IBM Silverlake compiler   The Beach Bum
• looking for lintlib or function decl building program   Eric K. Bustad
• Trigraphs.   Ray Butterworth
• How not to write a loop, revisited   Rob Carriere
• Should I convert FORTRAN code to C?   Rob Carriere
• Should I convert FORTRAN code to C?   Dave Caswell
• Optimization in a better world   David Chase
• Partial application in C   David Chase
• Is right recursive C grammar necessary?   Rich Chomiczewski
• volatile   Wayne A. Christopher
• why do you need volatile?   Wayne A. Christopher
• Should I convert FORTRAN code to C?   Wayne A. Christopher
• volatile: a summary   Wayne A. Christopher
• Any bounds-checking C compilers?   Wayne A. Christopher
• C Compiler bugs (was Re: Speaking of ksh)   Lawrence V. Cipriani
• More ANSI comment help wanted: #define void int vs. #define void char   Lawrence V. Cipriani
• C Compiler bugs (was Re: Speaking of ksh)   Lawrence V. Cipriani
• C Compiler bugs   Lawrence V. Cipriani
• C Compiler bugs   Lawrence V. Cipriani
• Some trigraph statistics   Lawrence V. Cipriani
• How do you document breakless cases?   Lawrence V. Cipriani
• How do you document breakless cases   Lawrence V. Cipriani
• I/O implementation in C and C++   Mike Coffin
• volatile (in comp.lang.c)   David Collier-Brown
• Should I convert FORTRAN code to C?   Greg Comeau
• I need a little advice...   Gregory Conway
• I need a little help, yet again...   Gregory Conway
• Ceiling of the Logarthim Base Two   Lawrence Crowl
• volatile: a summary   Ross Cunniff
• How not to write a loop, revisited   Scott Daniels
• How not to write a loop, revisited   Scott Daniels
• C Compiler bugs (was Re: Speaking of ksh)   Owen DeLong
• Should I convert FORTRAN code to C?   Owen DeLong
• no noalias not negligible - a difference between C and Fortran - long   Scott Denham
• volatile   Peter J Desnoyers
• volatile (in comp.lang.c)   Peter J Desnoyers
• volatile: a summary   Peter J Desnoyers
• volatile: a summary   Peter J Desnoyers
• Let's define our own NULL II   Bob Devine
• Irish Alert (compiler error)   Bob Donaldson
• Trigraphs: a program   Dick Dunn
• volatile (in comp.lang.c)   Ray Dunn
• Dynamic multidimensional arrays   J. Eaton
• Should I convert FORTRAN code to C?   J. Eaton
• Should I convert FORTRAN code to C?   J. Eaton
• Volatile is stupid   Robert Firth
• Should I convert FORTRAN code to C?   Robert Firth
• Structure pointer question   Robert Firth
• Using arrow keys with curses.   Greg Franks
• Needed: translator from VAX BASIC to C   Mark D. Freeman
• "%#s"?   Stephen J. Friedl
• Variable dimensioning in fortran (now in C)   Stephen J. Friedl
• Puzzle on unsigned promotions   Stephen J. Friedl
• Turbo C Startup for 8088 stand alone system needed....   Henry R Frohne
• Dynamic multidimensional arrays   Heinrich Gantenbein
• Multiple includes of standard headers   Jim Gardner
• How not to write a loop, revisited   Bill Gibbons
• Exponentiation in C (was: How not to write a loop)   Bill Gibbons
• Should I convert FORTRAN code to C?   Jim Giles
• Should I convert FORTRAN code to C?   Jim Giles
• Should I convert FORTRAN code to C?   Jim Giles
• C vs. FORTRAN   Jim Giles
• Should I convert FORTRAN code to C?   Jim Giles
• C vs. FORTRAN   Jim Giles
• Should I convert FORTRAN code to C?   Paul Gomme
• Partial application in C   Paul Gomme
• the D programnming language   David Goodenough
• Should I convert to C?   David Goodenough
• Trigraphs and Pragmas   Doug Gwyn
• trigraphs in X3J11   Doug Gwyn
• ?? in existing source code   Doug Gwyn
• Help wanted on avoiding name space pollution   Doug Gwyn
• More ANSI comment help wanted: #define void int vs. #define void char   Doug Gwyn
• More ANSI comment help wanted: #define void int vs. #define void char   Doug Gwyn
• generic pointers (was: #define void int vs. #define void char)   Doug Gwyn
• C Compiler bugs   Doug Gwyn
• C Compiler bugs   Doug Gwyn
• Initialization in #include files   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• C Compiler bugs   Doug Gwyn
• volatile: a summary   Doug Gwyn
• volatile: a summary   Doug Gwyn
• third public review of ANSI C   Doug Gwyn
• More ANSI comment help wanted: #define void int vs. #define void char   Doug Gwyn
• volatile: a summary   Doug Gwyn
• Initialization in #include files   Doug Gwyn
• Curious about function prototypes...   Doug Gwyn
• Structure pointer question   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• ANSIfication of #define ctl(X) ('X' & 0x1f)   Doug Gwyn
• Why does C standard consider each compiler flag a separate implementation?   Doug Gwyn
• Curious about function prototypes...   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• Dynamic multidimensional arrays   Doug Gwyn
• C Compiler bugs (was Re: Speaking of ksh)   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• Dynamic multidimensional arrays   Doug Gwyn
• replacements for regcmp/regex in PW?   Doug Gwyn
• Dynamic multidimensional arrays   Doug Gwyn
• a reasonable approach to inlining   Doug Gwyn
• Curious about function prototypes...   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• Structure pointer question   Doug Gwyn
• Let's define our own NULL   Doug Gwyn
• #defining NULL as (-1) in stdio   Doug Gwyn
• Let's define our own NULL   Doug Gwyn
• Partial application in C   Doug Gwyn
• = vs. == (was: Let's define our own NULL)   Doug Gwyn
• sizeof aggregate (was: Should I convert FORTRAN code to C?)   Doug Gwyn
• Table lookups   Doug Gwyn
• __STDCPP__ anybody?   Doug Gwyn
• NULL etc.   Doug Gwyn
• Variable dimensioning in fortran (now in C)   Doug Gwyn
• __STDCPP__ anybody?   Doug Gwyn
• lint on Altos 2000 is BROKE BROKE BROKE!   Doug Gwyn
• Optimal structure field ordering   Doug Gwyn
• Pragma and noalias   Doug Gwyn
• __STDCPP__ anybody?   Doug Gwyn
• Volatile is stupid   Doug Gwyn
• Should I convert FORTRAN code to C?   Doug Gwyn
• Structure pointer question   Doug Gwyn
• Is right recursive C grammar necessary?   Mark Hall
• Is right recursive C grammar necessary?   Mark Hall
• Let's define our own NULL   Dave Hammond
• Turbo C, version 2.0 ???   Richard Hargrove
• Irish Alert (compiler error)   Richard Hargrove
• Let's define our own NULL   Richard Hargrove
• null pointers (was: negative addresses)   Guy Harris
• Volatile is stupid   Guy Harris
• Possible bug in the SUN C compiler   Guy Harris
• replacements for regcmp/regex in PW?   Guy Harris
• null pointers (was: negative addresses)   Guy Harris
• Let's define our own NULL II   Guy Harris
• Let's define our own NULL   Guy Harris
• Turbo C, version 2.0 ???   Steve Harrold
• ?? in existing source code   Richard Harter
• Variable dimensioning in fortran   Richard Harter
• Should I convert FORTRAN code to C?   Richard Harter
• Variable dimensioning in fortran   Richard Harter
• Let's define our own NULL II   Richard Harter
• Should I convert FORTRAN code to C?   Richard Harter
• Simulating Structures in Fortran   Richard Harter
• Help with strings   Dick Hauser
• #pragma   Karl Heuer
• VAX (VMS) C / strangeness (serious bug?) w/ prototypes and floats   Karl Heuer
• "%#s"?   Karl Heuer
• Trigraphs and Pragmas   Karl Heuer
• trigraphs in X3J11   Karl Heuer
• Help with strings   Karl Heuer
• volatile (in comp.lang.c)   Karl Heuer
• "%#s"?   Karl Heuer
• trigraphs in X3J11   Karl Heuer
• trigraphs in X3J11   Karl Heuer
• Programming style with arrays, summary   Karl Heuer
• Alloca() and friends   Karl Heuer
• #define void int vs. #define void char   Karl Heuer
• C Compiler bugs (was Re: Speaking of ksh)   Karl Heuer
• trigraphs in X3J11   Karl Heuer
• C Compiler bugs   Karl Heuer
• C Compiler bugs (was Re: Speaking of ksh)   Karl Heuer
• volatile: a summary   Karl Heuer
• Should I convert FORTRAN code to C?   Karl Heuer
• Should I convert FORTRAN code to C?   Karl Heuer
• ANSIfication of #define ctl(X) ('X' & 0x1f)   Karl Heuer
• Structure pointer question   Karl Heuer
• "%#s"?   Karl Heuer
• Dynamic multidimensional arrays   Karl Heuer
• "%#s"?   Karl Heuer
• Structure pointer question   Karl Heuer
• Dynamic multidimensional arrays   Karl Heuer
• Structure pointer question   Karl Heuer
• All those frequently asked questions   Karl Heuer
• Exponentiation in C (was: How not to write a loop)   Karl Heuer
• char *strcat(), *strcpy(), *fgets();   Karl Heuer
• C/IBM   Richard Hoffman
• __STDCPP__ anybody?   Hokey
• __STDCPP__ anybody?   Hokey
• Table lookups   The Mad Merkin Hunter
• ?? in existing source code   John F. Haugh II
• Function prototype generator   John F. Haugh II
• volatile (in comp.lang.c)   Eugene D. Brooks III
• volatile (in comp.lang.c)   Eugene D. Brooks III
• volatile (in comp.lang.c)   Eugene D. Brooks III
• IPC_PRIVATE in shared memory   James Logan III
• Should I convert FORTRAN code to C?   Kjartan Pierre Emilsson Jardedlisfraedi
• Partial application in C   Dave Jones
• Partial application in C   Dave Jones
• Is right recursive C grammar necessary?   Larry Jones
• Curious Behaviour of "sscanf"   Larry Jones
• Database source needed   William E. Davidsen Jr
• Let's define our own NULL   William E. Davidsen Jr
• Let's define our own NULL   William E. Davidsen Jr
• Should I convert FORTRAN code to C?   Gil Kloepfer Jr.
• Let's define our own NULL II   Chuck Karish
• RATFOR (A FORTRAN/C-Language hybrid)   Val Kartchner
• Curious Behaviour of "sscanf"   Joe Keane
• #defining NULL as (-1) in stdio   Joe Keane
• Distributed Declarations   David Keppel
• Partial application in C   David Keppel
• Table lookups   John Kessenich
• Any bounds-checking C compilers?   Mike Khaw
• turboc/msc spawn*   Earl H. Kinmonth
• turboc/msc spawn*   Earl H. Kinmonth
• Trouble with floor ()   Andrew Klossner
• IPC_PRIVATE in shared memory   John Knutson
• COBOL-to-C translator wanted   Bernard Lemercier
• volatile: a summary   Daniel R. Levy
• Why does C standard consider each compiler flag a separate implementation?   Daniel R. Levy
• Optimal structure field ordering   Daniel R. Levy
• NULL etc.   Sean Levy
• Should I convert to C?   Charles Lord
• Curious about function prototypes...   Gunars V. Lucans
• Any bounds-checking C compilers?   Barry Margolin
• strtod setting errno to EDOM?   Roland McGrath
• spawn, MSC   Gene McManus
• when a core dump occurs ?   Karl Meiser
• I/O implementation in C and C++   Michael Meissner
• Initialization in #include files   Leslie Mikesell
• Should I convert FORTRAN code to C?   Eugene N. Miya
• This is not Re: Should I convert FORTRAN code to C?   Eugene N. Miya
• C vs. FORTRAN   Eugene N. Miya
• #defining NULL as (-1) in stdio   Peter X Moore
• when a core dump occurs ?   Fourati Mourad
• putting stuff in the text segment   der Mouse
• "%#s"?   der Mouse
• volatile (applied to automatic variables)   der Mouse
• Using arrow keys with curses.   der Mouse
• xseek(y,z,0) .vs. xseek(y,z,1)   der Mouse
• Should I convert FORTRAN code to C?   der Mouse
• Should I convert FORTRAN code to C?   der Mouse
• Initialization in #include files   der Mouse
• volatile: a summary   der Mouse
• Union type conversions   der Mouse
• a reasonable approach to inlining   der Mouse
• Should I convert FORTRAN code to C?   der Mouse
• Should I convert FORTRAN code to C?   der Mouse
• Optimal structure field ordering   Walter Murray
• Union type conversions   Alan Mycroft
• Curious about function prototypes...   Mark Nagel
• International Obfuscated C Code Contest winners to be announced   Landon Curt Noll
• "%#s"?   Richard A. O'Keefe
• I/O implementation in C and C++   Richard A. O'Keefe
• Trigraphs: a program   Richard A. O'Keefe
• trigraphs in X3J11   Richard A. O'Keefe
• C vs. FORTRAN   Richard A. O'Keefe
• C vs. FORTRAN   Richard A. O'Keefe
• Should I convert FORTRAN code to C?   Richard A. O'Keefe
• Help wanted on avoiding name space pollution   Arthur David Olson
• Help wanted on avoiding name space pollution   Arthur David Olson
• More ANSI comment help wanted: #define void int vs. #define void char   Arthur David Olson
• More ANSI comment help wanted: #define void int vs. #define void char   Arthur David Olson
• More ANSI comment help wanted: #define void int vs. #define void char   Arthur David Olson
• #define void int vs. #define void char   Arthur David Olson
• ANSIfication of #define ctl(X) ('X' & 0x1f)   Arthur David Olson
• __STDCPP__ anybody?   Arthur David Olson
• why do you need volatile?   Tim Olson
• Structure pointer question   Jim Patterson
• Partial application in C   Jim Patterson
• Should I convert FORTRAN code to C?   Mike Percy
• Curious Behaviour of "sscanf"   Powell
• __STDCPP__ anybody?   Ken Raeburn
• "Honour Parens" Rule (was: Re: Should I convert FORTRAN code to C?)   Eric A. Raymond
• Structure pointer question   Eric S. Raymond
• Let's define our own NULL   Len Reed
• Turbo C, version 2.0 ???   Timothy Reed
• replacements for regcmp/regex in PW?   Timothy Reed
• Looking for a Kalman filter written in C   Stan Reeves
• Looking for Turbo Pascal to Turbo C translator   Stan Reeves
• Looking for Fortran to C translator   Stan Reeves
• C vs Pascal   Jim Reid
• Should I convert FORTRAN code to C?   Randy Ricklefs
• Style Rules   Geoff Rimmer
• mailing list   Rob
• Dynamic multidimensional arrays   Jeff Rodriguez
• C/IBM   Christian Rohrmueller
• Should I convert FORTRAN code to C?   Bob Rose
• Should I convert FORTRAN code to C?   Bob Rose
• Variable dimensioning in fortran (now in C)   Bob Rose
• Variable dimensioning in fortran (now in C)   Bob Rose
• lint on Altos 2000 is BROKE BROKE BROKE!   Jim Rosenberg
• lint on Altos 2000 is BROKE BROKE BROKE!   Jim Rosenberg
• Trigraph programs.   Alan J Rosenthal
• Why does C standard consider each compiler flag a separate implementation?   Alan J Rosenthal
• ANSIfication of #define ctl(X) ('X' & 0x1f)   Alan J Rosenthal
• How not to write a loop, revisited   Herman Rubin
• Motorola DSP56000 --> NeXT   Michael Rutenberg
• Optimization in a better world   Steven Ryan
• volatile/CT hypothesis.   Steven Ryan
• volatile: a summary   Steven Ryan
• Should I convert FORTRAN code to C?   Steven Ryan
• Is right recursive C grammar necessary?   Steven Ryan
• Is right recursive C grammar necessary?   Steven Ryan
• Should I convert FORTRAN code to C?   Steven Ryan
• volatile: a summary   Steven Ryan
• Is right recursive C grammar necessary?   Steven Ryan
• On formally undecidable programs (was: Re: volatile: a summary)   Steven Ryan
• volatile: a summary   Steven Ryan
• Volatile is stupid   Steven Ryan
• volatile: a summary   Steven Ryan
• "Honour Parens" Rule (was: Re: Should I convert FORTRAN code to C?)   Steven Ryan
• Safe optimization   Steven Ryan
• Optimal structure field ordering   Steven Ryan
• Partial application in C   Steven Ryan
• Should I convert FORTRAN code to C?   Steven Ryan
• Optimal structure field ordering   Steven Ryan
• when a core dump occurs ?   Steven Ryan
• Partial application in C   Steven Ryan
• Should I convert FORTRAN code to C?   Steven Ryan
• Should I convert FORTRAN code to C?   Steven Ryan
• C vs. FORTRAN   Steven Ryan
• C vs. FORTRAN   Steven Ryan
• ANSIfication of #define ctl(X) ('X' & 0x1f)   Doug Salot
• Irish Alert (compiler error)   Gregory Sandell
• Why does C standard consider each compiler flag a separate implementation?   Rick Schubert
• Alloca() and friends   Scott Schwartz
• C vs. FORTRAN   Jerry Schwarz
• Structure pointer question   Andrew Scott
• The "N" word   Andrew Scott
• Structure pointer question   Andrew Scott
• Should I convert FORTRAN code to C?   Jack Shaio
• Should I convert FORTRAN code to C? (Really, multidim. arrays in C)   Peter Shenkin
• Question on Unary '+' (Was, "Should I convert FORTRAN code to C?")   Peter Shenkin
• Should I convert FORTRAN code to C?   Peter Shenkin
• Looping Conditions   Curt Signorino
• volatile   Dave Sill
• Noalias trivia question   Dave Sill
• Noalias trivia question   Dave Sill
• Malloc problems   Peter da Silva
• "%#s"?   Peter da Silva
• Is &a[NTHINGS] legal   Peter da Silva
• Help needed with #include problems   Peter da Silva
• Needed: translator from VAX BASIC to C   Harry Skelton
• volatile: how will it work here?   Bill Smith
• Trigraphs and Pragmas   Henry Spencer
• xseek(y,z,0) .vs. xseek(y,z,1)   Henry Spencer
• Should I convert FORTRAN code to C?   Henry Spencer
• Union type conversions   Henry Spencer
• Curious about function prototypes...   Henry Spencer
• HELP....structures   Jerry Davis Rsch. Statistician
• C.intensive   Chuck Stein
• Short Course Announcement   Chuck Stein
• Let's define our own NULL   Mark Stevans
• Let's define our own NULL II   Mark Stevans
• Optimal structure field ordering   Mark Stevans
• Optimal structure field ordering   Mark Stevans
• IPC_PRIVATE in shared memory   Richard Stevens
• Should I convert FORTRAN code to C?   Tom Stockfisch
• Looking for Fortran to C translator   Alan Strassberg
• Using arrow keys with curses.   Lawrence F. Strickland
• Structure pointer question   Michael T Sullivan
• Structure pointer question   Michael T Sullivan
• volatile: a summary   Steve Summit
• Curious about function prototypes...   Steve Summit
• Trigraphs.   Steve Summit
• Should I convert FORTRAN code to C?   Frank Swarbrick
• Should I convert FORTRAN code to C?   Frank Swarbrick
• turboc/msc spawn*   Frank Swarbrick
• Let's define our own NULL II   Frank Swarbrick
• Curious about function prototypes...   Wayne A. Throop
• Structure pointer question   Wayne A. Throop
• volatile   Chris Torek
• #define void int vs. #define void char   Chris Torek
• volatile (in comp.lang.c)   Chris Torek
• xseek(y,z,0) .vs. xseek(y,z,1)   Chris Torek
• volatile: a summary   Chris Torek
• volatile: a summary   Chris Torek
• volatile: a summary   Chris Torek
• Curious about function prototypes...   Chris Torek
• volatile: a summary   Chris Torek
• Dynamic multidimensional arrays   Chris Torek
• Dynamic multidimensional arrays   Chris Torek
• a reasonable approach to inlining   Chris Torek
• volatile: a summary   Chris Torek
• Volatile is stupid   Chris Torek
• volatile: a summary   Chris Torek
• Volatile is stupid   Chris Torek
• volatile: a summary   Chris Torek
• Let's define our own NULL   Chris Torek
• Should I convert FORTRAN code to C?   Chris Torek
• For non-USENET readers only   Chris Torek
• when a core dump occurs ?   Chris Torek
• Partial application in C   Chris Torek
• "far" type specifiar   Prescott K. Turner
• NaN   Shankar Unni
• Initialization in #include files   Jim Vlcek
• xseek(y,z,0) .vs. xseek(y,z,1)   Jeff Wabik
• C Compiler bugs (was Re: Speaking of ksh)   Mat Waites
• Should I convert FORTRAN code to C?   Mat Waites
• Variable dimensioning in fortran (now in C)   Steve Wampler
• Query: "Data Dictionary" Facilities?   Dallas Webster
• no noalias not negligible - a difference between C and Fortran - long   T. William Wells
• Goto considered helpful   T. William Wells
• putting stuff in the text segment   T. William Wells
• Noalias trivia question   T. William Wells
• I/O implementation in C and C++   T. William Wells
• "%#s"?   T. William Wells
• volatile (in comp.lang.c)   T. William Wells
• why do you need volatile?   T. William Wells
• volatile: a summary   T. William Wells
• Should I convert FORTRAN code to C?   T. William Wells
• Pragma and noalias   T. William Wells
• Structure pointer question   T. William Wells
• Optimal structure field ordering   Barnacle Wes
• Partial application in C   Barnacle Wes
• Let's define our own NULL   Barnacle Wes
• C vs. FORTRAN   Ross Wetmore
• obfuscated C   David V. Wilbur
• Mouse and Turbo C 1.0   Bill Wilson
• turboc/msc spawn*   Bill Wilson
• Looking for Turbo Pascal to Turbo C translator   Bill Wilson
• Scaring scanf() (Was: Help with strings)   Leo de Wit
• Partial application in C   Leo de Wit
• Should I convert FORTRAN code to C?   Leo de Wit
• Variable dimensioning in fortran   Leo de Wit
• lib   Leo de Wit
• Partial application in C   Leo de Wit
• Variable dimensioning in fortran (now in C)   Leo de Wit
• Should I convert FORTRAN code to C?   Leo de Wit
• Union type conversions   Leo de Wit
• About precision invervals (was: How not to write a loop)   Leo de Wit
• Optimal structure field ordering   Leo de Wit
• Curious Behaviour of "sscanf"   Leo de Wit
• Initialization (was: Variable dimensioning in fortran)   Leo de Wit
• Variable dimensioning in fortran (now in C)   Leo de Wit
• Motorola DSP56000   Brian Woodroffe
• Union type conversions   Farrell Woods
• Trouble with floor ()   Robert Zeff
• Union type conversions   Michael Zehr
• volatile: a summary   Lloyd Zusman
• Should I convert to C?   spenser aden
• C++ conference abstracts due June 14   ark at alice.UUCP
• NaN   ark at alice.UUCP
• volatile (in comp.lang.c)   rpw3 at amdcad.UUCP
• Area Memory Allocation   brian at bradley.UUCP
• strtod setting errno to EDOM?   gwyn at brl-smoke.UUCP
• trigraphs in X3J11   gwyn at brl-smoke.UUCP
• Noalias trivia question   hutchson at convex.UUCP
• Request for membership of INFO-C   C841253%NEUVM1.BITNET at cunyvm.cuny.edu
• Matrix Inversion Routine needed!   SWANGER%AUDUCVAX.BITNET at cunyvm.cuny.edu
• C/IBM   Chuck_M_Grandgent at cup.portal.com
• Curious about function prototypes...   Devin_E_Ben-Hur at cup.portal.com
• volatile (in comp.lang.c)   Paul_L_Schauble at cup.portal.com
• NULL etc.   Paul_L_Schauble at cup.portal.com
• Should I convert FORTRAN code t   rgh at inmet.UUCP
• ?? in existing source code   tanner at ki4pv.UUCP
• ?? in existing source code   tanner at ki4pv.UUCP
• curses   allan krantz
• C/IBM   mchawi
• lib   mchawi
• Should I convert to C?   mchawi
• Help wanted on avoiding name space pollution   chris at mimsy.UUCP
• validation of ANSI-C compilers   jrv%sdimax2 at mitre-bedford.arpa
• How not to write a loop, revisited   jrv%sdimax2 at mitre-bedford.arpa
• "Honour Parens" Rule   anw at nott-cs.UUCP
• Safe optimization   dsill at nswc-oas.arpa
• DSP56000   tomc at oakhill.UUCP
• magic cookies given back by ftell, and used in fseek   Every system needs one
• volatile: a summary   Every system needs one
• Function prototype generator   dalenber at p.cs.uiuc.edu
• Software Transformation Problems   byrum at sleet.cs.odu.edu
• Mouse and Turbo C 1.0   keithc at spked.UUCP
• SVVS (was OSF discussion)   R.H. coast near the top
• Let's define our own NULL   kenny at uiucdcsm.UUCP
• Should I convert FORTRAN code to C?   mcdonald at uxe.cso.uiuc.edu
• Volatile is stupid   mcdonald at uxe.cso.uiuc.edu
• why do you need volatile?   Rick Genter x18
• C Compiler bugs   greg yachuk
• trigraphs in X3J11   robert yaeger
• trigraphs in X3J11   robert yaeger

Last message date: Thu Jun 30 14:49:39 AEST 1988
Archived on: Mon Feb 1 19:33:16 AEST 2016

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