ding sooner. I'm a graduate student and
have been ill on-and-off since mid-December. This does not make for
free time for responding to email :)
I realize that this is not a high-priority issue, but I do appreciate
any effort that goes into making -Wconversion more useful.
-- Agthorr
Well, I also compile with -Wmissing-noreturn. If I add the noreturn
attribute to main, gcc complains that the function returns. If I
remove the noreturn, gcc complains that the function does not return.
gcc can't have it both ways. ;)
On Mon, Nov 18, 2002 at 10:55:07PM -, [EMAIL PROTECTED]
Package: gcc-3.0
Version: 1:3.0.4-6
Severity: normal
The following program generates a superfluous warning when compiled
with -std=c99 or -std=gnu99.
#include
int main (void) __attribute__ ((noreturn));
int main (void)
{
Package: gcc-3.0
Version: 1:3.0.4-6
Severity: normal
-Wswitch doesn't actually seem to do anything in gcc-3.0, although it
works in gcc 2.95.4. Here's what the documentation says it *should*
do:
`-Wswitch'
Warn wheneve
---
It'd be nice if these two behaviors were two controlled via two
separate flags. The second behavior would have caught a bug I've been
hunting for hours, while the first behavior is very undesirable to me
(and useless since I also compile with -Wstrict-prototypes).
-- Agthorr
code ugly ;)
-- Agthorr
typedef char foo[16];
void bar (const foo *xyzzy)
{}
int main(void)
{
foo bozz;
bar (&bozz);
ample program which prints "foo" once
with javac, but twice with gcj/libgcj.
I found this while debugging a real program, where it was causing me
quite a bit of confusion.
-- Agthorr
import java.io.*;
class B
This means that the field won't actually get
serialized. Below is a patch to correct the problem. I could write a
small demonstration program to show the difference in behavior from
javac, if desired.
-- Agthorr
--- gcc-20011024/libjava/java/util/Date.java~ Tue Jan 9 01:43:39 2001
+++
8 matches
Mail list logo
