public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@debian.org>
To: ncw@axis.demon.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Asm style
Date: Thu, 22 Nov 2001 15:29:07 +0100	[thread overview]
Message-ID: <3BFD0BB3.2000000@debian.org> (raw)
In-Reply-To: <fa.derh1nv.1h0ai0b@ifi.uio.no> <fa.njuqm5v.100c5ak@ifi.uio.no>

ncw@axis.demon.co.uk wrote:
> Giacomo Catenazzi wrote:
>> 
>> not ANSI C. The trailing \ is understood only in marco definitions
>> (and outside strings)
>> 
> gcc begs to differ
> 
> /* z.c */
> #include <stdio.h>
> 
> int main(void)
> {
>     printf("This is a string\n\
> with continuation characters\n");
>     return 0;
> }
> 
> $ gcc -Wall -pedantic -ansi z.c -o z
> [silence]
> 
> Remove the \ and you get
> 
> z.c:5: warning: string constant runs past end of line
> z.c: In function `main':
> z.c:5: warning: ANSI C forbids newline in string constant
> 

gcc should warn in both case (when calling it with -pedantic -ansi).
But forget my comment:
Talking about ANSI C for asm construct doen't make much sense.

If gcc people will maintain (in long future) the syntax of
trailing \ + NL, I agree to use it into kernel.

	giacomo



       reply	other threads:[~2001-11-22  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.derh1nv.1h0ai0b@ifi.uio.no>
     [not found] ` <fa.njuqm5v.100c5ak@ifi.uio.no>
2001-11-22 14:29   ` Giacomo Catenazzi [this message]
2001-11-22 11:31     ` Asm style Jakub Jelinek
     [not found] <fa.d6k3juv.16q3on@ifi.uio.no>
     [not found] ` <fa.cbkkrrv.m72ejr@ifi.uio.no>
2001-11-22 12:43   ` Giacomo Catenazzi
2001-11-22  9:27     ` ncw
2001-11-21 23:07 vda
2001-11-21 21:21 ` Ben Collins
     [not found] <01112123070300.05447@manta.suse.lists.linux.kernel>
2001-11-21 21:23 ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BFD0BB3.2000000@debian.org \
    --to=cate@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw@axis.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox