home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!mcsun!Germany.EU.net!news.uni-bielefeld.de!techfak.uni-bielefeld.de!malte
- From: malte@techfak.uni-bielefeld.de (Malte Uhl)
- Subject: Re: ACK ANSI Compiler
- Sender: news@hermes.hrz.uni-bielefeld.de (News Administrator)
- Message-ID: <C0I2CK.75q@hermes.hrz.uni-bielefeld.de>
- Date: Thu, 7 Jan 1993 20:02:43 GMT
- References: <1993Jan6.163649.17110@udel.edu> <103840@netnews.upenn.edu> <C0HpKv.3t7@cs.vu.nl>
- Nntp-Posting-Host: dahlie.techfak.uni-bielefeld.de
- Organization: Universitaet Bielefeld, Technische Fakultaet.
- Lines: 29
-
- In article <C0HpKv.3t7@cs.vu.nl>, ast@cs.vu.nl (Andy Tanenbaum) writes:
- |>
- |> While I really don't want to continue this pointless discussion much longer,
-
- [ .. lots of statements deleted .. ]
-
- |> Andy Tanenbaum (ast@cs.vu.nl)
-
- Ok, we all know the reasons for ACK not being free now. I'd like to raise a
- serious discussion about using gcc only for compiling and developing Minix
- on all of the supported platforms. As Linus Torwalds stated some postings ago,
- $200 for a however-good compiler set is more expensive than a free compiler
- and some memory.
-
- Why do I think so ? gcc runs on a very wide variety of platforms, produces
- reasonably "good" code and implements the (are there more than one ?) ANSI
- standard. Agreed, it is a memory hog, but you'll have a hard time searching
- for a C program that you cannot compile with, say 4 MB RAM. This is what
- an Atari ST is capable of.
- A nice (in my opinion) side effect of using gcc would be the removal of
- 80[012]86 support and its a fine occasion to make integers 32 bits large
- by default, too.
-
- There are a couple of arguments more I could give here now, but this will
- lead us too much into detail.
-
- No flames please, I'm only trying to raise a discussion about this.
-
- Malte
-