CompuServe Messages

>A good part of getting used to the C language is learning how to cope with >pointers Very true. And something every C programmer should master. Equally though, I rather tend to not consider it a "good part" but just another part of the deal. Surely, vast quantities of C code can be written w/o any (explicit) pointers at all (this is less a suggestion than letting people stick with the current corners of the language that are known to them, appropriate, etc expecting the rest to subsequently materialize when applicable). IOW, I consider C, or any language, a package to deal with. Yes, though, each does have their set of gotchas and wackos, and in C, many problems do surround pointers. Anyway, on another frame of reference: the thought process, approach, insights, etc, of the problem, and its solutions, is often lost in language, OS, editor, problem and issues. It is this I always try to instill into folks when I teach or write. >It takes a certain type of mind to keep track of how many levels you >need to track to get the to actual stuff you want. 🙂 Yes, this is the killer kind of issue from above. Figure the danged thing out first. Far to many get (artificially) bottlenecked with the notation (this is not to say it isn't a genuine issue, but is something that should be besides the point). >The C language takes a certain mindset, which is hard for some. In general, >what you're writing is a subroutine which is called in by a mess of canned code >attached to your program. If I understand what you mean, this is not anything specific just to C. > Thought: C IS REALLY TWO DISTINCT LANGUAGES. > Language 1: "Traditional C" is something that you'll find described in lots >of books… > Language 2: "Targeted C" goes for the whole rich paraphenalia of the Amiga: That's not two distinct languages. It's the exact same language being used in different contexts. In the latter case we're simply talking about the same C using API's et al for the Amiga. Nothing in C changes. (BTW, "Traditional C" usually connotates "K&R C". It's better to keep it that way to distinguish it from "Standard C", the ISO/ANSI C.)