From: Phil Edwards <phil@jaj.com>
To: Nicole Nails <nnails@palm.net>
Cc: libstdc++@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: help!!
Date: Mon, 17 Jun 2002 13:05:00 -0000 [thread overview]
Message-ID: <20020617160452.A23507@disaster.basement.lan> (raw)
In-Reply-To: <20020617195757.13842.qmail@uwdvg001.cms.usa.net>; from nnails@palm.net on Mon, Jun 17, 2002 at 07:57:57PM -0000
Please don't send HTML email; more information is at gcc.gnu.org/lists.html
On Mon, Jun 17, 2002 at 07:57:57PM -0000, Nicole Nails wrote:
> I need though a list of all
> possible errors the GNU compiler will detect when a student is attempting to
> compile and/or run a program.
In theory, anywhere the language rules say that a compiler must detect an
error, we do so.
For an exact list, look through the GCC source code for calls to the
functions named "warning" and "error".
Be aware that there are many mistakes in C and C++ that compilers cannot
detect, or are not required to detect. Beginning students should probably
use flags like
-Wall -W -pedantic
while learning the language.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next parent reply other threads:[~2002-06-17 20:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020617195757.13842.qmail@uwdvg001.cms.usa.net>
2002-06-17 13:05 ` Phil Edwards [this message]
2018-06-01 15:58 Help!! Tomas Ukkonen
-- strict thread matches above, loose matches on Subject: below --
2006-12-26 13:38 help!! manish manish
2006-12-27 17:01 ` help!! Ian Lance Taylor
2006-01-28 5:42 Help? Garvin Pang
2006-01-28 7:41 ` Help? Brian Dessent
2005-06-02 15:54 help_ imacat
2003-07-12 10:05 help? Shen Hui
2003-03-03 17:37 help!!! Jim Frost
2003-03-07 5:46 ` help!!! LLeweLLyn Reese
[not found] <20021204042724.64819.qmail@web15002.mail.bjs.yahoo.com>
2002-12-04 0:16 ` help! Ben Elliston
2002-11-19 10:16 help!!! mingo lu
2002-04-04 23:41 Help! 朱 少波
2001-01-02 18:27 Help? Kwanghoon Choi
2001-01-02 19:37 ` Help? Alexandre Oliva
2000-05-15 9:15 HELP!!! Michael Michael
2000-05-16 23:27 ` HELP!!! Martin v. Loewis
2000-03-08 14:14 HELP !!! FabrÃcio Souza
2000-03-09 17:00 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` FabrÃcio Souza
2000-02-24 0:56 Help! 陳鵬升
2000-04-01 0:00 ` Help! 陳鵬升
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=20020617160452.A23507@disaster.basement.lan \
--to=phil@jaj.com \
--cc=gcc-help@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=nnails@palm.net \
/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).