Re: [gtk-list] Re: Was : Why is gtk+ written in C? - now : QuickRant



Besides, use gcc with -ansi and -pedantic flags and -Wall to get all
warnings and refuse to compile non-ANSI code.

--Jason

On 19 Oct 1998, Alan Shutko wrote:

> >>>>> "P" == Paul Miller <Paul_Miller@avid.com> writes:
> 
> P> It's impossible to do void pointer arithmetic in C++ (without an
> P> explicit cast), no matter what compiler, because it is illegal.
> 
> It's illegal in C as well.  (ISO 6.3.6)  
> 
> P> The point wasn't merely so much about C++ being better for
> P> type-safety (it is), but that "ANSI C" isn't nearly as "ANSI" as
> P> people think it is, because compilers allow things like that to
> P> slip by.
> 
> ANSI is very ASNI.  There's a nice 200pg standard for it sitting on my
> desk.  Your complaint is that C compilers don't always complain about
> illegal things (because they're allowing extensions).  Is there
> something about C++ that prohibits compilers from extending anything?
> (Unlikely, but even so it wouldn't be followed in practice.)
> Therefore, I don't think there's anything inherently better about
> using a C++ compiler than a C compiler... while you may get better
> warnings now, with some compilers, there's no guarantee.
> 
> -- 
> Alan Shutko <ats@acm.org> - By consent of the corrupted
> SI:%GC-QLX-LUSER-TM governs how long the GC waits before timing out the user.
> 
> -- 
> To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
> 
> 

-------------------------------------------------------------------------------
Jason A. Pfeil, Computer Science Graduate Student      101 Carothers Hall
http://www.cs.fsu.edu/~pfeil			       C3527 University Center
pfeil@cs.fsu.edu				       (850)644-8014



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]