home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!Sirius.dfn.de!Urmel.Informatik.RWTH-Aachen.DE!dfv.rwth-aachen.de!sungate.fido.de!p1.hippo.fido.de!spam.fido.de!Gilles_Kohl
- Date: Sat, 29 Aug 92 08:16:00 +0200
- From: Gilles_Kohl@spam.fido.de (Gilles Kohl)
- Subject: Most difficult part of learning C?
- Message-ID: <7907e1ff@p3.f6.n249.z2.fidonet.org>
- References: <ffb5aed0@romeo.cs.duke.edu>
- Newsgroups: comp.lang.c
- X-Comment-To: (Tom Truscott)
- Organization: To take arms against a C of troubles ...
- Lines: 25
-
- > Some difficulties can be circumvented by avoiding them entirely.
- > In my opinion the following can be omitted:
- > boolean operators
- > goto
- > enumerated types
- > bit fields
- > typedefs
- > unions
- > pointer arithmetic
- > Is the purpose of the course to explore every last corner of the C
- > language, or is it to teach some topic for which C happens to be
- > appropriate?
- Tom,
-
- The beauty of C consists in its smallness, IMHO. You can't leave much out
- without serious limitations. The topic of the course should be plain C, not one
- subset or the other. Teach them all, _and_ tell them about the potential
- problems. In real life, they will have to maintain programs containing elements
- that you consider superfluous, they should at least be able to identify and
- understand them.
-
- Regards,
- Gilles.
-
- ---
-