[cfe-commits] Patch to make clang compile and work on Windows using MSVC8
Hartmut Kaiser
hartmut.kaiser at gmail.com
Tue Sep 4 18:29:41 PDT 2007
Chris,
> >>>> It looks like it might just be trailing whitespace removed.
> >>>> Is this intentional or just something extraneous in the patch?
> >>>
> >>> This was intentionally. AFAIK a backslash/newline should be
> >> recognized
> >>> as a line continuation only if there is no whitespace in between
> >>> those.
> >>
> >> This is a well known (and long-debated) GCC extension that we're
> >> intentionally compatible with.
> >
> > Understand. Can you (optionally) switch that off, just to be 100%
> > Standards comformant?
>
> I believe we already emit "backslash and newline separated by space"
> as a warning. I would be fine with changing it to an
> extension warning (visible with -pedantic). Is this what you mean?
I'm not sure I understand the conventions applied for Clang, so please
excuse my ignorance.
IMHO a tool like Clang should be absolutely Standards conformant by default.
If there are extensions supported these should be enabled explicitely if
needed. In this context I'ld report an _error_ on "backslash and newline
separated by space" and allow to bring that down to an (pedantic) warning
using a special --allow_gcc_extensions switch only. But YMMV...
Regards Hartmut
More information about the cfe-commits
mailing list