Re: Traditional C rejects ISO C

2004-06-15 Thread Peter \"Firefly\" Lund
On Sat, 12 Jun 2004, Carl B. Constantine wrote: > 2) I get these errors in callbacks.c for routines like: > > void on_button_3_clicked(GtkButton *button, gpointer user_data) > > which I didn't write, but glade generated it for me. One thing you could do -- which is Good Practice in any case -- is

Re: Traditional C rejects ISO C

2004-06-14 Thread Carl B. Constantine
* Manish Singh ([EMAIL PROTECTED]) wrote: > On Sat, Jun 12, 2004 at 08:01:05PM -0700, Carl B. Constantine wrote: > > I thank you for your reply, however it doesn't really answer my > > question. First, I'm only using gcc, so Borland and MS C don't count. > > Second, I'm obviouslly using gcc's -Wtra

Re: Traditional C rejects ISO C

2004-06-13 Thread Valdis . Kletnieks
On Sat, 12 Jun 2004 20:01:05 PDT, "Carl B. Constantine" said: > Second, I'm obviouslly using gcc's -Wtraditional setting for these > errors to come up, so my question was: how do I get rid of these errors > so that everything works correctly while still using -Wtraditional? > Should I even be usin

Re: Traditional C rejects ISO C

2004-06-13 Thread [EMAIL PROTECTED]
On Sat, 12 Jun 2004, Carl B. Constantine wrote: > * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > > What's "traditional C?" Is that K&R C, or the C formerly known as > > c89, ANSI X3.159-1989? Then there is ISO C, ISO/IEC 9899:1990. > > Then there is C99, ISO 9899:1999. > > Good question, I

Re: Traditional C rejects ISO C

2004-06-12 Thread Manish Singh
On Sat, Jun 12, 2004 at 08:01:05PM -0700, Carl B. Constantine wrote: > I thank you for your reply, however it doesn't really answer my > question. First, I'm only using gcc, so Borland and MS C don't count. > Second, I'm obviouslly using gcc's -Wtraditional setting for these > errors to come up, so

Re: Traditional C rejects ISO C

2004-06-12 Thread David Necas (Yeti)
On Sat, Jun 12, 2004 at 08:01:05PM -0700, Carl B. Constantine wrote: > Should I even be using -Wtraditional? I don't think so since Gtk+ itself requires an ISO C compiler -- at least approximately -- to compile. Yeti -- Do not use tab characters. Their effect is not predictable. ___

Re: Traditional C rejects ISO C

2004-06-12 Thread Carl B. Constantine
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > What's "traditional C?" Is that K&R C, or the C formerly known as > c89, ANSI X3.159-1989? Then there is ISO C, ISO/IEC 9899:1990. > Then there is C99, ISO 9899:1999. Good question, I don't know. All I know is what I get in the warning. > For t

Re: Traditional C rejects ISO C

2004-06-12 Thread [EMAIL PROTECTED]
What's "traditional C?" Is that K&R C, or the C formerly known as c89, ANSI X3.159-1989? Then there is ISO C, ISO/IEC 9899:1990. Then there is C99, ISO 9899:1999. For the purposes of your question, I'd imagine you are refering to ISO C as c99 and "traditional C" as c89. As K&R C does not sup

Traditional C rejects ISO C

2004-06-12 Thread Carl B. Constantine
I'm getting alot of these in my code recently. Most likely due to the update to gcc on my systems. I have two problems: 1) I get these errors in gutils.h which I didn't write. (using glib2-2.4.0-1 in Fedora Core 2. I haven't tried with a newer version of glib yet on my Debian box. 2) I get these