hi I am new in these forum and i need some exercices with sollution of Functions in C,I prefer books if its possible
thn you so much
hi I am new in these forum and i need some exercices with sollution of Functions in C,I prefer books if its possible
thn you so much
This is a sticky thread on the main page of the C forum: C Book Recommendations. More books that you could ever need. Also, there are lots of free online resources for this. Google for "function tutorials C" or "function exercises C". That should give you plenty to work on.
With something as complex as C and it's libraries you can "play around with a compiler" for a couple of decades and acquire nothing but bad habits and piles of partially functional code. There are concepts set forth in books and tutorials you will *never* blunder onto by yourself. There are pitfalls explained that you will fall into constantly without even realizing their dangers... There are some things you just have to be *told*.
The C Book - Table of Contents
Functions are the 2nd part of the 1st chapter.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Yes it will... but it won't make a programmer out of you. At best it makes you a hack (as opposed to hacker).
I'm self-educated, started in BASIC back in the z-80 days, moved to Pascal when I started on PCs... now C after Borland killed Pascal. 20 years after beginning programming, I went the "start from scratch" route with C, just like I did with Pascal... grab a good book and start reading...
If you think you can learn C without some sort of guidance, just take a look at your own message history and notice how often you've posted totally bogus ideas --like SEH just being some clever if/else stuff-- and been corrected by others. You may know programming syntax from your playing around but I don't see a lot of evidence you know anything about programming itself.
Knowing all the words to a language is useless unless you also know the grammar.
That's a terrible example - you can't learn that from reading C books anyway, or at least the ones designed for *nix based machines.
You really can't make such a broad claim based off of 93 posts, not to mention that you're implying that almost everything I say is wrong and uninformed (which isn't true). The only 'true' ways to judge this about a person would be to (either) examine what they've written and its source, or watch them for a longer period of time on a forum and see how much they actually know or don't know.
Also, (as you said), programming is useless if all you know is syntax, but I still fail to see your distinction of "programming itself."
Because Posix systems don't use SEH.
Maybe the brush was a bit too wide... but the point remains. Programmers who don't conduct deliberate studies of programming and it's techniques, almost always end up in the "Skript Kiddie" bin because, while they may know all the right syntax they know nothing about programming.You really can't make such a broad claim based off of 93 posts, not to mention that you're implying that almost everything I say is wrong and uninformed (which isn't true). The only 'true' ways to judge this about a person would be to (either) examine what they've written and its source, or watch them for a longer period of time on a forum and see how much they actually know or don't know.
Also, (as you said), programming is useless if all you know is syntax, but I still fail to see your distinction of "programming itself."
Programming is a distinct entity, separate from writing source code. In fact "coding" is actually a very small part of the skillset. The primary skills are analytical --understanding the problem, troubleshooting errors, etc.-- not syntactical. For example: Knowing how to write a multithreaded program is pointless if you don't know *when* to write a multithreaded program. As I've said here, so often it's become a "groaner": No programmer has ever successfully written a solution to a problem he does not understand.
Beyond the basic skills are advanced techniques --like SEH-- that are necessary to write commercial quality code but not part of the "Whatever for Dummies" books. A programmer who's not spending time "keeping up" by reading technical papers and advanced journals isn't going to stay in the market very long. (Why do you think there's this big ongoing grumble here about those awful universities in India still teaching Turbo C for DOS?)
Sure thing, grab a compiler and mess with it... have fun.
But don't fool yourself into thinking that knowing how to write a clever for() loop makes you anything even vaguely resembling a programmer.
For your comment about the forums... I\m pretty sure most here can usually tell, almost right away, if someone has some skills or not.