June 1988 Archives by date

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

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

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

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 ] [ author ]