I want to learn how to do something internet related with C.
What do you want to see in Learn C The Hard Way?
101–110 of 127 posts
Re: What do you want to see in Learn C The Hard Way?
#102Re: What do you want to see in Learn C The Hard Way?
#103I really like the __attribute__ mechanism that GCC has, something covering that will be really nice.
Not likely to happen, outside scope.
Re: What do you want to see in Learn C The Hard Way?
#104You probably want to make sure you know C, first.
About 10 years worth, I'm unqualified anyway.
10 years suggests nothing, really. If "int x; What type is &x", "int x[5]; What type is x? What type is &x?" manages to confuse you, I suggest you re-learn C, before authoring this book of yours.
Re: What do you want to see in Learn C The Hard Way?
#105Earlier quoted context omitted.
Unfortunately I think you mean "rough" as in non-responsive... not as in pitiless -- which, assuming a suitable level of expertise, would be great for me.
No I mean pitiless. The C channel I've observed for years is out and out brutal.
Mind if I ask which channel? I suspect my code deserves "brutal", at least on round one :)
Re: What do you want to see in Learn C The Hard Way?
#106I'll go ahead and pledge that if you write it, I will buy a copy. I love LPTHW's emphasis on exercises. It's one thing to read and understand a concept as presented. It's another thing entirely to actually apply it to problem.
Re: What do you want to see in Learn C The Hard Way?
#107Earlier quoted context omitted.
Beg your pardon?
If you don't know what UB or IDB is, you probably don't want to write a book pertaining to C, :)
Context specific.
Could be intel debugger, could be undefined behavior, could be implementation defined behavior. I tested them on a group of about 15 C devs, mixture of embedded, linux, DSP, and other volken.
Got the same guesses I made and a lot of question marks.
It's easy to run your mouth but not actually contribute, you might consider your role in this process before commenting again.
Re: What do you want to see in Learn C The Hard Way?
#108Earlier quoted context omitted.
If you don't know what UB or IDB is, you probably don't want to write a book pertaining to C, :)
Context specific. Could be intel debugger, could be undefined behavior, could be implementation defined behavior. I tested them on a group of about 15 C devs, mixture of embedded, linux, DSP, and other volken. Got the same guesses I made and a lot of question marks. It's easy to run your mouth but not actually contribute, you might consider your role in this process before commenting again.
[deleted]
Re: What do you want to see in Learn C The Hard Way?
#109Make sure you explain pointers well, the additional level of indirection introduced by them is usually hard to grasp for beginners. Show the relation between pointers and arrays. Offer some best practices on using pointers. Explain the most common caveats like buffer overflows, problems with null terminated strings or off by one errors.
Even better, make sure you explain function pointers well.
Some years ago, I ran across and saved off a copy of a some-dozen page reference, in PDF format, titled something along the lines of 'everything you (will) ever need to know about pointers (in C)'. It appeared to be quite well regarded.
But, that laptop was ripped off and the particular file appears not to have made it into backups.
Does this description happen to ring a bell? Any references?
Re: What do you want to see in Learn C The Hard Way?
#110Earlier quoted context omitted.
If you don't know what UB or IDB is, you probably don't want to write a book pertaining to C, :)
Context specific. Could be intel debugger, could be undefined behavior, could be implementation defined behavior. I tested them on a group of about 15 C devs, mixture of embedded, linux, DSP, and other volken. Got the same guesses I made and a lot of question marks. It's easy to run your mouth but not actually contribute, you might consider your role in this process before commenting again.
I don't think C defines an intel debugger.