Re: "C" Manual
On Saturday 29 December 2001 11:53 am, wsa wrote:
> As others have said stear clear of OS specific topics...
> Even if you want to start using OS specific stuff later on i think it's
> best to start out with real C++.
> In my opinion you should even avoid 'plain' C because you'll end up
> learning things you can ditch in C++ cause there are more effecient and
> new ways of doing things in ++.
> And make very sure whatever book you get really really restricts to C++...
> cause there's a shitload of them that sneak in non C++ stuff like the
> dreaded conio
Exactly. I remember seeing some huge book with an ambitious name like "C++
Bible" or "C++ Black Book" or something. Nothing on the cover said that the
book was platform or compiler-specific. I opened it, and it had all these
ugly Windows system calls (messages) throughout. This stuff wasn't even put
into its own chapter! It was everywhere!
To the OP: If you are intersted in doing applications programming some day, I
suggest you learn the C part of *C++* first. YMMV. Other intersting languages
may include: Perl, Bash, Python, Lisp, Scheme, FORTRAN, Haskell, O'Caml, SML,
Prolog, Java (for some people, but not for me).
Alec
P.S. A real BOFH would say "man cc" :)
> Cheers,
> Willem
>
> >You'll find loads of recommendations and other info on the web and on the
> >C/C++ newsgroups.
> >
> >A word of advice: ignore the whole OS issue when buying general C/C++
> >books or looking at stuff on the web. The best stuff is not system
> >specific as the language is not, and if you restrict yourself to
> >Linux-specific books you are unnecessarily limiting yourself. If you want
> >to use Linux specific extensions/libraries, that is another matter.
> >
> > Sincerely, Faheem Mitha.
Reply to: