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


Groups > comp.lang.c > #148158

Re: curiosity about compiler phases

Subject Re: curiosity about compiler phases
Newsgroups comp.lang.c
References (5 earlier) <_u9CF.666$LP4.521@fx40.am4> <sycCF.12697$6v7.9462@fx23.iad> <q0dCF.741$CD3.668@fx39.am4> <877e3q54hc.fsf@bsb.me.uk> <2NtCF.31026$ku.8470@fx04.am4>
From Bart <bc@freeuk.com>
Message-ID <4eRCF.116405$Yv4.34488@fx20.am4> (permalink)
Organization virginmedia.com
Date 2019-11-25 14:06 +0000

Show all headers | View raw


On 24/11/2019 11:25, Bart wrote:
> On 24/11/2019 03:37, Ben Bacarisse wrote:
>> Bart <bc@freeuk.com> writes:
>>
>>> The one I used was gfortran compiled with gcc, running on
>>> rextester.com so probably not Windows. This program didn't compile
>>> (4-space indentation added):
>>>
>>>      !gfortran, gcc version 5.4.0 20160609
>>>
>>>      program hello
>>>          pri&
>>>      nt *, "Hello World!"
>>
>> You need
>>
>>        &nt *, "Hello World!"
> 
> OK, you need two &s, at the end of one line, and at the start of the next.

Actually, the behaviour is not consistent:

You only need one & at the end of the first line, to split between tokens.

You need two to split in the middle of a token.

If you want one or more empty lines between the first and second, each 
of those lines needs && (other white space on the line ignored, but in 
other contexts and before the first/only &, an after the &, is significant).

So the behaviour is rather complex with rules that are likely to be 
different from other languages' line continuation schemes.

Note that while this language doesn't need special statement endings 
such as ";", where a line ends with "," (or other symbols suggesting 
continuation such as "("), the line doesn't automatically continue onto 
the next.

So it NEEDS the line continuation more than many others where such 
common cases don't need any special indications.

AFAICS it is something that can be dropped from C, except from the 
line-based preprocessor where it only appears to be needed inside macro 
definitions.

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


Thread

curiosity about compiler phases Thiago Adams <thiago.adams@gmail.com> - 2019-11-07 05:28 -0800
  Re: curiosity about compiler phases Nick Bowler <nbowler@draconx.ca> - 2019-11-22 19:25 +0000
  Re: curiosity about compiler phases "A. K." <minforth@arcor.de> - 2019-11-22 12:19 -0800
  Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-22 22:22 +0000
    Typo? (Was: curiosity about compiler phases) gazelle@shell.xmission.com (Kenny McCormack) - 2019-11-22 22:34 +0000
      Re: Typo? (Was: curiosity about compiler phases) Bart <bc@freeuk.com> - 2019-11-22 23:49 +0000
        Re: Typo? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2019-11-22 19:26 -0700
    Re: curiosity about compiler phases scott@slp53.sl.home (Scott Lurndal) - 2019-11-22 23:12 +0000
      Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-23 00:06 +0000
        Re: curiosity about compiler phases Richard Damon <Richard@Damon-Family.org> - 2019-11-22 20:34 -0500
        Re: curiosity about compiler phases Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-11-23 01:47 +0000
          Re: curiosity about compiler phases Richard Damon <Richard@Damon-Family.org> - 2019-11-22 21:21 -0500
            Re: curiosity about compiler phases Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-11-24 03:26 +0000
              Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-24 11:29 +0000
                Re: curiosity about compiler phases Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-11-24 16:49 +0000
          Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-23 12:21 +0000
            Re: curiosity about compiler phases Richard Damon <Richard@Damon-Family.org> - 2019-11-23 10:08 -0500
            Re: curiosity about compiler phases scott@slp53.sl.home (Scott Lurndal) - 2019-11-23 15:49 +0000
              Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-23 16:21 +0000
                Re: curiosity about compiler phases Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-11-24 03:37 +0000
                Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-24 11:25 +0000
                Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-25 14:06 +0000
    Re: curiosity about compiler phases Keith Thompson <kst-u@mib.org> - 2019-11-22 21:25 -0800
      Beyond our pay grade (Was: curiosity about compiler phases) gazelle@shell.xmission.com (Kenny McCormack) - 2019-11-23 07:43 +0000
    Re: curiosity about compiler phases Thiago Adams <thiago.adams@gmail.com> - 2019-11-23 06:28 -0800
      Re: curiosity about compiler phases Thiago Adams <thiago.adams@gmail.com> - 2019-11-23 06:39 -0800
      Re: curiosity about compiler phases Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2019-11-23 09:46 -0500
        Re: curiosity about compiler phases Richard Damon <Richard@Damon-Family.org> - 2019-11-23 10:16 -0500
      Re: curiosity about compiler phases Bart <bc@freeuk.com> - 2019-11-23 16:13 +0000
        Re: curiosity about compiler phases Thiago Adams <thiago.adams@gmail.com> - 2019-11-25 03:24 -0800
  Re: curiosity about compiler phases Bonita Montero <Bonita.Montero@gmail.com> - 2019-11-23 08:43 +0100

csiph-web