nelson@sun.soe.clarkson.edu (Russ Nelson) (12/06/88)
Now that I have Turbo C 2.0 and Turbo Debugger, I find that compiling
for source level debugging conflicts with a standard information
hiding scheme, leaving structures undefined. :-( Fortunately, Turbo C
doesn't complain about zero length structures.
What are the portability considerations of defining zero length structures?
Like this:
struct foo {
#ifdef INTERNAL
int bar, baz;
#endif
};
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])
To surrender is to remain in the hands of barbarians for the rest of my life.
To fight is to leave my bones exposed in the desert waste.henry@utzoo.uucp (Henry Spencer) (12/07/88)
In article <NELSON.88Dec5142448@sun.soe.clarkson.edu> nelson@clutx.clarkson.edu writes: >What are the portability considerations of defining zero length structures? They aren't portable. -- SunOSish, adj: requiring | Henry Spencer at U of Toronto Zoology 32-bit bug numbers. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu