From: Andrew Pinski <pinskia@gmail.com>
To: "André Coelho" <andrealbergaria@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: syntax errors
Date: Tue, 10 May 2022 15:23:36 -0700 [thread overview]
Message-ID: <CA+=Sn1mF7FvybRGEbPi4eUnbJmAw3h7Aa6ZBncCch_zz2FGqPQ@mail.gmail.com> (raw)
In-Reply-To: <a1103a19-392c-8157-53b5-9a311f7fe6de@gmail.com>
On Tue, May 10, 2022 at 3:19 PM André Coelho via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hey...if the compiler can check syntax errors...why can't it fixed them?
In some cases it does recommend ways of fixing it. But not all syntax
errors are fixable.
Also not all syntax errors might be the wrong behavior vs what the user wanted.
Thanks,
Andrew Pinski
>
>
> thanks
>
>
> andre coelho
>
next prev parent reply other threads:[~2022-05-10 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 22:18 André Coelho
2022-05-10 22:23 ` Andrew Pinski [this message]
2022-05-10 22:32 ` Mohamed Atef
-- strict thread matches above, loose matches on Subject: below --
2019-01-03 17:03 Daniel Marjamäki
2019-01-03 17:39 ` Jonathan Wakely
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='CA+=Sn1mF7FvybRGEbPi4eUnbJmAw3h7Aa6ZBncCch_zz2FGqPQ@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=andrealbergaria@gmail.com \
--cc=gcc@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).