From: Nate Eldredge Newsgroups: comp.os.msdos.djgpp,comp.os.msdos.programmer Subject: Re: Detecting Windows and Windows directory from DOS Date: 21 Mar 2000 14:22:41 -0800 Organization: InterWorld Communications Lines: 22 Message-ID: <83puso55fy.fsf@mercury.st.hmc.edu> 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: mercury.st.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: nntp1.interworld.net 953677478 34076 134.173.45.219 (21 Mar 2000 22:24:38 GMT) X-Complaints-To: usenet AT nntp1 DOT interworld DOT net NNTP-Posting-Date: 21 Mar 2000 22:24:38 GMT User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Richard Dawe writes: > 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. ;) Hmm, interesting question of semantics. I think this means the behavior is unspecified by the standard, which is certainly true. So according to the standard, in real life anything may happen. It _may_ compile just fine (and in most cases probably will), or give a warning, or fail at runtime, or whatever. In fact, what actually happens is certainly defined, since the computer is still a finite-state machine ;-) So: The standard behavior is undefined, but it only _may_ actually break. -- Nate Eldredge neldredge AT hmc DOT edu