[mythtv] [PATCH] fifowriter gcc 3.4

[Kenneth Aafløy]

On Saturday 05 June 2004 04:28, Eric Hattemer wrote:
> Kenneth Aafløy wrote:
> >Sure you'r compiler is not a bit behind? Tried some of the -std=xxx
> > variables as CFLAGS?
>
> I'm not sure what you mean by behind.  Its gcc 3.4.0 release (non-cvs)
> version.  I compiled one version myself, and grabbed the contrib rpm
> from mandrake.  Both give these errors.  From what I can tell, c++
> compatible flags are -std=gnu++98, -std=c++98, and -ansi.  None of the C
> flags seem to apply.  They all fail.

|GCC now requires an ISO C90 (ANSI C89) C compiler to build. K&R C compilers 
|will not work. 

>
> As for fifobuffer:
>
> http://www.gnu.org/software/gcc/gcc-3.4/changes.html
>
> When allocating an array with a new expression, GCC used to allow
> parentheses around the type name. This is actually ill-formed and it is
> now rejected:
>
> 	int* a = new (int)[10];    // error, not accepted anymore
> 	int* a = new int[10];      // OK
>
> As for the RTjpeg:
> The cast-as-lvalue extension has been removed for C++ and deprecated for
> C and Objective-C. In particular, code like this:
>
>         int i;
>         (char) i = 5;
> or this:
>         char *p;
>         ((int *) p)++;
>
> is no longer accepted for C++ and will not be accepted for C and
> Objective-C in a future version.

I guess  that it was the >C90 version requirement that prohibited this 
behavior. Can't really see what's wrong with it for doing low level c++, but 
since that is the behavior decided.....?

Bah, what the heck do I knwo?..

Kenneth J. Aa.