Re: C needs to evolve

From	Ian Collins <ian-news@hotmail.com>
Newsgroups	comp.lang.c
Subject	Re: C needs to evolve
Date	2017-11-22 11:19 +1300
Message-ID	<f7jn3bFqjosU6@mid.individual.net> (permalink)
References	(7 earlier) <9fb758c6-4531-468c-b3a6-43fa0020978c@googlegroups.com> <b0fc3668-dc3a-4f7d-b66c-4a9f5d47cb31@googlegroups.com> <07971662-4cd2-4f96-a9d5-27af7525d417@googlegroups.com> <2ada3bdd-69e4-4447-9cbd-c2e5da76ca43@googlegroups.com> <7a7db0d7-b646-47f4-8b2c-98dfb845d3e9@googlegroups.com>

Show all headers | View raw

On 11/22/2017 11:10 AM, Rick C. Hodgin wrote:
> On Tuesday, November 21, 2017 at 4:41:57 PM UTC-5, Rick C. Hodgin wrote:
>> ...It should be function-specific and not language specific.
>> There are times when 0 makes sense as an input parameter, and times
>> when it doesn't.  It should be on a function-by-function basis.
> 
> To be clear about this, I think the C Spur-Standard that I'm talking
> about should not be like the existing C Standard, but should simply
> outline functionality, cite examples, and convey the expected output.
> In this way, with the history of C existing, it is self-evident how
> it works to anyone with a little bit of instruction on the basic
> syntax.
> 
> This should exist for flow control:
> 
>      for (init; test; incr) { .. } -- Looping
> 
>      init -- An initialization expression
>      test -- A test expression, if it fails the loop exits
>      incr -- An increment expression
> 
>      Supports break; to manually exit the loop, and continue; to go on
>      to the next iteration.

What you describe is a tutorial, not a standard.

-- 
Ian.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 06:04 -0800
  Re: C needs to evolve "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2017-11-17 22:14 +0800
    Re: C needs to evolve "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2017-11-17 22:15 +0800
    Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 06:18 -0800
      Re: C needs to evolve Mark Storkamp <mstorkamp@yahoo.com> - 2017-11-17 09:12 -0600
    Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 06:21 -0800
  Re: C needs to evolve mark.bluemel@gmail.com - 2017-11-17 07:09 -0800
    Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 07:24 -0800
      Re: C needs to evolve gazelle@shell.xmission.com (Kenny McCormack) - 2017-11-17 15:45 +0000
    Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 07:29 -0800
      Re: C needs to evolve "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2017-11-17 23:33 +0800
      Re: C needs to evolve mark.bluemel@gmail.com - 2017-11-17 07:35 -0800
        Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-17 10:43 -0500
          Re: C needs to evolve supercat@casperkitty.com - 2017-11-21 07:56 -0800
            Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 08:28 -0800
              Re: C needs to evolve supercat@casperkitty.com - 2017-11-21 11:51 -0800
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 12:19 -0800
                Re: C needs to evolve supercat@casperkitty.com - 2017-11-21 13:08 -0800
                Re: C needs to evolve fir <profesor.fir@gmail.com> - 2017-11-21 13:36 -0800
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 13:41 -0800
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 14:10 -0800
                Re: C needs to evolve Ian Collins <ian-news@hotmail.com> - 2017-11-22 11:19 +1300
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 16:07 -0800
                Re: C needs to evolve Ian Collins <ian-news@hotmail.com> - 2017-11-22 13:09 +1300
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-21 17:25 -0800
                Re: C needs to evolve Ian Collins <ian-news@hotmail.com> - 2017-11-22 14:31 +1300
                Re: C needs to evolve supercat@casperkitty.com - 2017-11-21 14:33 -0800
                Re: C needs to evolve "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2017-11-22 05:27 -0800
    Re: C needs to evolve Thiago Adams <thiago.adams@gmail.com> - 2017-11-17 08:32 -0800
      Re: C needs to evolve David Kleinecke <dkleinecke@gmail.com> - 2017-11-17 11:55 -0800
  Re: C needs to evolve zacariaz@gmail.com - 2017-12-01 11:31 -0800
    Re: C needs to evolve Keith Thompson <kst-u@mib.org> - 2017-12-01 11:57 -0800
    Re: C needs to evolve Thiago Adams <thiago.adams@gmail.com> - 2017-12-01 13:26 -0800
      Re: C needs to evolve Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> - 2017-12-01 22:36 +0100
      Re: C needs to evolve supercat@casperkitty.com - 2017-12-01 13:54 -0800
        Re: C needs to evolve Thiago Adams <thiago.adams@gmail.com> - 2017-12-01 14:32 -0800
          Re: C needs to evolve Thiago Adams <thiago.adams@gmail.com> - 2017-12-01 14:39 -0800
      Re: C needs to evolve "Pascal J. Bourguignon" <pjb@informatimago.com> - 2017-12-02 04:13 +0100
  Re: C needs to evolve zacariaz@gmail.com - 2017-12-01 15:50 -0800
  Re: C needs to evolve zacariaz@gmail.com - 2017-12-02 03:44 -0800
  Re: C needs to evolve Chris Ahlstrom <OFeem1987@teleworm.us> - 2017-12-02 07:28 -0500
    Re: C needs to evolve bartc <bc@freeuk.com> - 2017-12-02 12:50 +0000
      Re: C needs to evolve Felipe Ferreira <felipefsdev@gmail.com> - 2017-12-02 06:26 -0800

csiph-web