Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #150634 > unrolled thread

"How one word broke C"

Started byLynn McGuire <lynnmcguire5@gmail.com>
First post2020-03-17 14:29 -0500
Last post2020-03-24 19:41 -0400
Articles 3 on this page of 43 — 17 participants

Back to article view | Back to comp.lang.c


Contents

  "How one word broke C" Lynn McGuire <lynnmcguire5@gmail.com> - 2020-03-17 14:29 -0500
    Re: "How one word broke C" Real Troll <Real.Troll@Trolls.com> - 2020-03-17 15:40 -0400
      Re: "How one word broke C" John Bode <jfbode1029@gmail.com> - 2020-03-19 11:57 -0700
        Re: "How one word broke C" James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-03-19 18:20 -0400
    Re: "How one word broke C" Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-03-17 13:39 -0700
      Re: "How one word broke C" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-03-17 21:55 +0000
    Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-17 23:02 +0100
      Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-17 21:57 -0400
        Re: "How one word broke C" Dan Purgert <dan@djph.net> - 2020-03-18 11:02 +0000
          Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-18 08:58 -0400
            Re: "How one word broke C" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-03-18 06:04 -0700
              Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-18 09:53 -0400
            Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-18 14:46 +0100
              Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-19 08:55 -0400
        Re: "How one word broke C" Philipp Klaus Krause <pkk@spth.de> - 2020-03-18 18:21 +0100
          Re: "How one word broke C" already5chosen@yahoo.com - 2020-03-18 12:11 -0700
            Re: "How one word broke C" Philipp Klaus Krause <pkk@spth.de> - 2020-03-18 21:06 +0100
              Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-18 22:43 -0400
                Re: "How one word broke C" Tim Rentsch <tr.17687@z991.linuxsc.com> - 2020-03-27 07:18 -0700
          Re: "How one word broke C" Dan Purgert <dan@djph.net> - 2020-03-19 01:40 +0000
        Re: "How one word broke C" Eli the Bearded <*@eli.users.panix.com> - 2020-03-18 19:12 +0000
          Re: "How one word broke C" Philipp Klaus Krause <pkk@spth.de> - 2020-03-18 21:09 +0100
      Re: "How one word broke C" David Brown <david.brown@hesbynett.no> - 2020-03-18 21:35 +0100
        Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-18 23:27 +0100
          Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-19 08:57 -0400
            Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-19 15:00 +0100
          Re: "How one word broke C" David Brown <david.brown@hesbynett.no> - 2020-03-19 15:02 +0100
            Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-19 15:10 +0100
              Re: "How one word broke C" gazelle@shell.xmission.com (Kenny McCormack) - 2020-03-19 14:34 +0000
                Re: "How one word broke C" Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-03-19 07:44 -0700
                  Re: "How one word broke C" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2020-03-19 14:57 +0000
                  Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-19 15:58 +0100
                    Re: "How one word broke C" David Brown <david.brown@hesbynett.no> - 2020-03-19 16:26 +0100
                Re: "How one word broke C" David Brown <david.brown@hesbynett.no> - 2020-03-19 16:08 +0100
                  Troll, gadfly, whatever... (Was: "How one word broke C") gazelle@shell.xmission.com (Kenny McCormack) - 2020-03-21 11:08 +0000
                    Re: Troll, gadfly, whatever... (Was: "How one word broke C") Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-03-21 04:50 -0700
              Re: "How one word broke C" David Brown <david.brown@hesbynett.no> - 2020-03-19 16:04 +0100
                Re: "How one word broke C" felix@palmen-it.de (Felix Palmen) - 2020-03-19 16:16 +0100
                  Re: "How one word broke C" Richard Damon <Richard@Damon-Family.org> - 2020-03-19 23:36 -0400
            Re: "How one word broke C" James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-03-19 18:13 -0400
    Re: "How one word broke C" Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-03-17 19:43 -0600
      Re: "How one word broke C" John Bode <jfbode1029@gmail.com> - 2020-03-24 16:07 -0700
    Re: "How one word broke C" James Kuyper <jameskuyper@alumni.caltech.edu> - 2020-03-24 19:41 -0400

Page 3 of 3 — ← Prev page 1 2 [3]


#150639

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2020-03-17 19:43 -0600
Message-ID<1b36a6bfps.fsf@pfeifferfamily.net>
In reply to#150634
Lynn McGuire <lynnmcguire5@gmail.com> writes:

> "How one word broke C"
>    https://news.quelsolaar.com/2020/03/16/how-one-word-broke-c/

"In C89, undefined behavior is interpreted as, “The C standard doesn’t
have requirements for the behavior, so you must define what the behavior
is in your implementation, and there are a few permissible options”."

The author doesn't seem to understand what "ignoring the situation
completely with unpredictable results" (from his quote from C89) means.

[toc] | [prev] | [next] | [standalone]


#150813

FromJohn Bode <jfbode1029@gmail.com>
Date2020-03-24 16:07 -0700
Message-ID<6b2da778-f82a-413e-97a9-bd913dfa9f44@googlegroups.com>
In reply to#150639
On Tuesday, March 17, 2020 at 8:43:19 PM UTC-5, Joe Pfeiffer wrote:
> Lynn McGuire <lynnmcguire5@gmail.com> writes:
> 
> > "How one word broke C"
> >    https://news.quelsolaar.com/2020/03/16/how-one-word-broke-c/
> 
> "In C89, undefined behavior is interpreted as, “The C standard doesn’t
> have requirements for the behavior, so you must define what the behavior
> is in your implementation, and there are a few permissible options”."
> 
> The author doesn't seem to understand what "ignoring the situation
> completely with unpredictable results" (from his quote from C89) means.

Yeah, I don't think the spirit of the C89 standard was "undefined behavior may only be one 
of the following options", it was "undefined behavior may be any of the following *or 
something else completely*".  It's always been freeform. 

[toc] | [prev] | [next] | [standalone]


#150815

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2020-03-24 19:41 -0400
Message-ID<r5e5s0$6hc$1@dont-email.me>
In reply to#150634
On 3/17/20 3:29 PM, Lynn McGuire wrote:
> "How one word broke C"
>     https://news.quelsolaar.com/2020/03/16/how-one-word-broke-c/

I notice that it nominally has a "Comments" section, but the number of
comments is 0. It's still 0 a week after I attempted to post a comment.
Perhaps he doesn't like criticism?

[toc] | [prev] | [standalone]


Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.lang.c


csiph-web