home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky gnu.gcc.help:2271 gnu.misc.discuss:3253
- Path: sparky!uunet!stanford.edu!ames!purdue!yuma!csn!csn.org!james
- From: james@unidata.com (James Powell)
- Newsgroups: gnu.gcc.help,gnu.misc.discuss
- Subject: GCC evangelists, take note!
- Message-ID: <JAMES.92Oct7104927@novadyne.unidata.com>
- Date: 7 Oct 92 17:49:27 GMT
- Sender: news@csn.org (news)
- Distribution: gnu
- Organization: Unidata, Inc.
- Lines: 22
-
-
- Help! I need to convince a rather large and conservative bunch of engineers
- that they should begin using GCC to maintain and extend their software. It runs
- on 36 UNIX platforms. Very few of these vendors include an ANSI 'C' compiler,
- so GCC seems to be the only way to support ANSI code across all these systems
- (the INSTALL notes indicate it will work for 30 of them, the other 6 are
- probables). So, I need reasons... _tons_ of reasons... for example, just how
- great is ANSI 'C', anyway? And how about GCC... will using it make their soft-
- ware run faster? Slower? Will they be able to use their existing tools with it
- (SCCS, lint, yacc, various debuggers, EMACS :-)? And most of all, they want
- assurances that it won't break any of their code. They are correctly terrified
- of buggy compilers... can I reassure them that their system will run at least
- as well as it did, without any tweaking? Will using GCC across all platforms
- simplify porting? Help me bring our code into the 1990's! Thank you thank you
- thank you...
- -James-
-
- --
-
- /-----------------------------------------------------------------------------\
- | James Powell - Programmer/Analyst - Special Projects - jamesp@unidata.com |
- \-----------------------------------------------------------------------------/
-