
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
"Chris Hills" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] sorry, i seldom see standard c programs that do any real work. most are full of platform specific types, inline compiler, link, or source control commands, inline assembler, etc. also, many c compilers have an option to allow k&r syntax. in a perfect world, all c code would conform to the latest ISO. actually, in a perfect world we probably would not be writing programs in c. :) however, you do make a good point that the k&r book is probably not a good transition text from assembler languages to c. the authors of the book disliked assembler and actually developed c so that they wouldn't have to use their assemblers. -bryan > In article <[EMAIL PROTECTED]>, Bryan > Bullard <[EMAIL PROTECTED]> writes > > > >"Chris Hills" <[EMAIL PROTECTED]> wrote in message > >news:[EMAIL PROTECTED] > > > >chris, > > > >i can respectfully acknowledge you're point of view. however, i and many > >others believe the k&r book is still valid for learning simply because all > >the concepts are plainly stated and explained. it is an easily and quickly > >digestible text. > > > >also, i will remind you that off all the c code out there a relatively small > >percentage of it adheres to C90+. > > > Most adheres to C90+ Some now almost C99. Certainly all the compilers > are somewhere between C95 and C99. Many of the things in K&R are not > permitted in many coding standards etc. > > There are also many better books for learning C especially fro some one > coming from an assembly background to embedded c. > > I have seen the effect of a K&R taught programmer coming to grips with > an embedded project... wanted to use sdterr and printf to hard disk for > debugging on an 8-bit smart card.... > > /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ > \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\ > /\/\/ [EMAIL PROTECTED] www.phaedsys.org \/\/ > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
| <-- __Chronological__ --> | <-- __Thread__ --> |