home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!att!dptg!ulysses!allegra!princeton!csservices!kastle!blume
- From: blume@kastle.Princeton.EDU (Matthias Blume)
- Subject: Re: Pascal as C prelude?
- Message-ID: <1992Nov21.181810.29808@csservices.Princeton.EDU>
- Sender: news@csservices.Princeton.EDU (USENET News System)
- Reply-To: blume@kastle.Princeton.EDU (Matthias Blume)
- Organization: Dept. of Computer Science, Princeton University
- References: <forb0004.94.722315425@student.tc.umn.edu> <3903@dozo.and.nl>
- Date: Sat, 21 Nov 1992 18:18:10 GMT
- Lines: 44
-
- In article <3903@dozo.and.nl>, jos@and.nl (Jos Horsmeier) writes:
- |>
- |> My advice is: study Pascal first and when you think you've got a firm
- |> notion of pointers, pointer arithmetic, dynamic memory allocation and
- ^^^^^^^^^^^^^^^^^^
- |> all sorts of wonderful stuff, switch to C.
- |>
- Pardon me!? How should you get a firm notion of THAT by learning
- Pascal????
-
- |> #define SILLY_MODE
- |> #ifdef SILLY_MODE
- |>
- |> There's just one drawback, when you do this: you'll end up writing
- |> ugly formatted code like:
- |>
- |> if (condition)
- |> {
- |> statement1;
- |> statement2;
- |> }
- |>
- |> instead of the proper:
- |>
- |> if (condition) {
- |> statement1;
- |> statement2;
- |> }
- |>
- |> #endif
-
- # define SERIOUS_MODE
- # ifdef SERIOUS_MODE
-
- The real problem is not, that those C-programs LOOK LIKE Pascal programs ---
- they ARE Pascal programs with a slightly different syntax. I've seen a lot
- of ``so-called'' C programs showing that their programmers didn't really learn
- C but only how to ``hand-translate'' Pascal code (or whatever) into C.
-
- :-(
-
- # endif
-
- -Matthias
-