I have just failed miserably at reading this article, which is a book review of sorts. The book being reviewed is an apparently popular reference for the C programming language
( Read more... )
it didnt help i never learned about any compiler beyond a poor version of cc. even the error lines were usually wrong, once i learned to add those flags on to get error lines (which was very late in the process). gcc -o -something. i think the compiler probably makes or breaks you with c. much like my unix environment, which was so totally broken you couldnt use the help pages or print, even if you knew how.
i could never get all the parens to line up. my version of scheme was pretty shitty, too.
I seem to be in the minority here... granted I never had to program anything particularly significant as I didn't continue in CS beyond the first few courses, C didn't particularly frustrate me. I picked it up pretty easily, and what seems to be my strength in programming, regardless of the language, was an ability to flesh out the logic to determine the necessary steps to make a program perform the desired function. Once I had the process down, it was a matter of applying the appropriate code and syntax for the language of choice. Of course do I remember any of it now 10+ years later, heck no!
Comments 4
Reply
Reply
it didnt help i never learned about any compiler beyond a poor version of cc. even the error lines were usually wrong, once i learned to add those flags on to get error lines (which was very late in the process). gcc -o -something. i think the compiler probably makes or breaks you with c. much like my unix environment, which was so totally broken you couldnt use the help pages or print, even if you knew how.
i could never get all the parens to line up. my version of scheme was pretty shitty, too.
Reply
Reply
Leave a comment