delorie.com/archives/browse.cgi | search |
From: | Rolf Campbell <moscoop AT NortelNetworks DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: qsort() bug? Or invalid usage??? |
Date: | Fri, 28 Jan 2000 14:25:00 -0500 |
Organization: | Nortel |
Lines: | 16 |
Message-ID: | <3891ED0C.50ABE2F6@NortelNetworks.com> |
References: | <R0Gh4.2371$Ll5 DOT 3502 AT news2 DOT randori DOT com> <867gpd$k0u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <388758A7 DOT 1B64BDF9 AT cyberoptics DOT com> <388824A4 DOT 7E8CA268 AT is DOT elta DOT co DOT il> |
NNTP-Posting-Host: | wmerh0tk.ca.nortel.com |
Mime-Version: | 1.0 |
X-Mailer: | Mozilla 4.71 [en] (X11; I; HP-UX B.10.20 9000/785) |
X-Accept-Language: | en |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Eli Zaretskii wrote: > > I don't think that a > > good implementation should do this, but I can find nothing in the ANSI standard > > that would prohibit such behavior. > > AFAIK, ANSI C explicitly allows to access an array one element before the > first one, provided that you don't write there. Couldn't that produce a memory protection error on a strict system? -- (\/) Rolf Campbell (\/)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |