::  >::  I run gcc 2.95.(3) and SAS/C (the latter is usually much more helpful on
::  >::  warnings, and still much more forgiving on "errors")...
::  >Can you add g++ for testing?
::  >Or also some other C++ compiler?
::  >Or use gcc at monday/wednesday and friday and g++ at the rest?
::  
::  I have no incentive to use C++ at all, infact I'm not even interested...
::  
You should not use C++, but the C code should not use special C expressions
allowed in C89 (ANSI C Standard from 1989), but strictly forbidden in ANSI C++.
A lot of them are forbidden in C99 (ANSI C Standard from October 1999).

You can't compiler LAME with a C99 compiler.

Good C Code should be compilable with (nearly) all C(89/95/99) and C++ compilers.


::  I'm not talking about "wild" typecasting, I'm saying that strict, controlled
::  typecasting can be good, instead of leaving it up to the compiler to make the
::  choices (which might not always be the correct one)...
::  
::  >C can't cast from type A to type B. There is only the possibility to
::  >cast every shit to type B. And this is dangerous.
::  >So you write a
::  >  int     ifreq;
::  >  double  dfreq;
::  >  ifreq = (int) ( dfreq );
::  >and now dfreq changes the type to 'struct bla*'. 
::  >C converts this without batting an eyelid.
::  
::  What the hell are you on about?!
::  
::  Oh, w8, you mean if some smartass changes dfreq to a struct without checking
::  the code, or atleast changing the name so these kinds of conflicts can occur?
::  
::  I'd say he'd be downright stupid. ;)
::  
Some of these bugs are parts of international standards.
The most well known is one in the Unix X11 system.
It was found 15 years after it was programmed while porting X11 for Ada.

Noone need to be a smartass to make such errors.
If you write a C program with 1 serious error/1500 LOC, you are a top
programmer.

-- 
Mit freundlichen Gr��en
Frank Klemm
 
eMail | [EMAIL PROTECTED]       home: [EMAIL PROTECTED]
phone | +49 (3641) 64-2721    home: +49 (3641) 390545
sMail | R.-Breitscheid-Str. 43, 07747 Jena, Germany

--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to