Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucbvax!decwrl!elroy.jpl.nasa.gov!ames!amdahl!dgcad!gary
From: gary@dgcad.SV.DG.COM (Gary Bridgewater)
Newsgroups: comp.lang.c++
Subject: stat
Message-ID: <1475@proa.SV.DG.COM>
Date: 24 Mar 90 10:00:27 GMT
Reply-To: gary@proa.SV.DG.COM (Gary Bridgewater)
Organization: Data General SDD, Sunnyvale, CA
Lines: 13

cfront 2.0 continued to grandfather the stat() / struct stat{}
problem.
What do people think about this?

Should we be biting the bullet and changing the name of the structure?
If so, wouldn't it be nice to agree on what we change it to and then
start lobbying to get it changed in the base c header files?

Or - should cfront (et. al.) just always be smart enough to differentiate
a function from a structure?
-- 
Gary Bridgewater, Data General Corporation, Sunnyvale California
gary@sv.dg.com or {amdahl,aeras,amdcad}!dgcad!gary
The impossible we understand right away - the obvious takes a little longer.