Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!hsdndev!cmcl2!adm!smoke!gwyn From: gwyn@smoke.brl.mil (Doug Gwyn) Newsgroups: comp.lang.c Subject: Re: trouble with macro`s Message-ID: <15523@smoke.brl.mil> Date: 20 Mar 91 21:21:38 GMT References: <15506@smoke.brl.mil> Organization: U.S. Army Ballistic Research Laboratory, APG, MD. Lines: 10 In article rjohnson@shell.com (Roy Johnson) writes: > But even if it "works" today, it may stop working tomorrow, as indeed > it must do once Sun releases a standard conforming C implementation. >Right. *That's* why I told him to document it. Are you suggesting that >he shouldn't write code that works because it isn't standard? I suspect >he has a job to do. That's a short-sighted attitude. We KNOW such code will quit "working" some day. That should be sufficient reason to find a better solution that does not depend on errors in the C implementation.