From: brahms AT mindspring DOT com (Stan Brown) Newsgroups: comp.os.msdos.djgpp,comp.os.msdos.programmer Subject: Re: Detecting Windows and Windows directory from DOS Date: Tue, 21 Mar 2000 22:29:47 -0500 Organization: Oak Road Systems Lines: 21 Message-ID: References: <8am5ub$o0v$1 AT news6 DOT svr DOT pol DOT co DOT uk> <38D108E3 DOT D9821E3B AT americasm01 DOT nt DOT com> <8arkm8$m3h$1 AT newsg2 DOT svr DOT pol DOT co DOT uk> <38D1EFAA DOT 7A48D29D AT is DOT elta DOT co DOT il> <38D6844B DOT 876E5631 AT bigfoot DOT com> <38D7E5F5 DOT ED6FB969 AT bigfoot DOT com> NNTP-Posting-Host: c7.ae.b0.f1 X-Server-Date: 22 Mar 2000 03:29:23 GMT X-Newsreader: MicroPlanet Gravity v2.10 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Said richdawe AT bigfoot DOT com (Richard Dawe) in comp.os.msdos.programmer: >By the way, I think you mean "in user code they _may_ lead to undefined >behavior" rather than "in user code they lead to undefined behavior", >which is a bit harsh. ;) No, I meant what I said. Undefined behavior means you can't count on it to do any particular thing. I would *guess* that __DOSX_H would not be used for their own purposes by most implementations, so probably it's safe. But you can't count on it: it's undefined behavior. It *may* lead to winged monkeys shooting out of your monitor, though in this particular case it's likely that the program would compile and run as desired. That's undefined behavior. -- Stan Brown, Oak Road Systems, Cleveland, Ohio, USA http://www.mindspring.com/~brahms/ My reply address is correct as is. The courtesy of providing a correct reply address is more important to me than time spent deleting spam.