Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: double free Date: Tue, 05 Jul 2016 17:25:33 -0700 Organization: None to speak of Lines: 26 Message-ID: References: <577ba42f.13700328@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="9669"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+H18yUdUK18n0usba7koTW" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:gsSYPdQ5dALrOGw3NeruxuKm8JE= sha1:SdzCEfzXXWfh25uWnzb12IE4h8c= Xref: csiph.com comp.lang.c:90062 G G writes: [...] > Keith is correct, and I should apologize to the group. The author did say > "runtime exception". I ran the code and it produce a runtime error on my > machine. I should not have said he said "runtime error". The lack of quotation marks made it clear enough that you weren't claiming to quote the book exactly, but rather summarizing it, and your summary was reasonably good. For most purposes, "runtime error" is nearly the same thing as "runtime exception". > I do apologize everyone. I don't want to give the authors a bad rep due > to my mistakes in representing there teachings, or thoughts. Actually you made the author look slightly better (but it's really not a big deal). "Runtime error" might reasonably describe undefined behavior (which is what the standard actually says); "runtime exception" implies some observable error (which is not guaranteed). [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"