Programming

Hello guys!

It's been some time and I have been busy. I got my qualification as an IT-Professional now (Systems Administrator).

I learned VB.NET at school but I don't want to continue using that language, I want to learn C because I'm working with Linux/UNIX most of the time, also I do electronics and will get a Arduino soon.

I learned VB.NET (basics) the "school" way. Like how to programm a class or how the syntax of a while-loop is. I heard Richard Stallman say that you should obtain some open-source software and "expand it" by adding code or changing the software to fit your needs. I mean, after 1 year VB.NET I must say I can't use the language properly, that gets me thinking.

I already got a book about C (Galileo Computing, german site) which reads pretty well, I've been working with that.
I think that if you work hard enough, you can always reach a goal. I just want to go in the right direction from the start because I don't want to waste any time.

So here are my questions:

1. What's the best way to get started? Should I look for a projekt to programm (maybe from Rosetta Code) and start at that or should I go through C step-by-step like:
1. Data-Types
2. printf
3. scanf
4. while
5. for
...

2. How did you get started?
3. Are there any sites/books/youtube videos that you can recommend me?

greetings,

nick.

Hi Nick,
I first taught myself to program with Java, then I taught myself C++. I learned both languages almost solely from a textbook. The internet usually helps where the book leaves off.

I would definitely read through the book you have first. Practice writing out some programs, either from the book or you can try to make simple program. I would also advise getting a notebook to keep some organized notes, you can make reference to later. As you get more proficient with the language, you will have to refer to it much less.

Reading the book while keeping notes and writing simple programs is definitely a start. Personally, I am not familiar with any good websites, but I know there there. I used the internet if a problem came up in my program that the book couldn't help me with. I would just Google my problem. There would usually be a forum or website with the solution.

thank you very much!

maybe while I'm continuing my work with my textbook some other people have some thoughts?

I'm not sure where the best place to begin is, but you need to keep one thing in mind in C. It's very different from other languages in that it's kind of a construction kit. Nearly all the features in C are there because the CPU directly supports them. All the oddness of the language, its unusual features and odd limits, its strange compilation errors stem from this -- that it is molded around the shape of the CPU itself. Anything that's not CPU-supported is done through external functions, one way or another.

Local variables really are local variables -- stored on the stack. They are directly available to the CPU if you set up space for them.

Global variables are likewise stored in the data segment, another CPU thing.

Functions are actual CPU functions, i.e. blocks of data you direct the CPU to via the CALL instruction or newer equivalents. They have addresses that you can get at, just like anything else in C.

Pointers are how the CPU deals with all memory, and are exposed directly to you, unlike most languages, which have fancy references that handle themselves, or no references at all. Variables are also handled directly with no middleman. You do A++; and the CPU will do something like INC [address of A]

So when you write a C program, you are telling it "Okay, create THESE functions, which I will call X Y and Z... with THESE local variables, which I will call Q Y and R... with these global things in the data segment, which I will call G H and M... Convert these statements into assembly language and find spots in memory for them. Convert all names into these addresses. Then staple everything together into something the CPU can load and execute directly."

I am a self taught amateur at coding in a few languages.
I learn very quickly when I jump in right at the deep end and splash about a lot until my head pops up above the water.
I thoroughly enjoy _hitting_ the HW, (banging the metal), and will deliberately attempt such tasks with all kinds of languages. Strangely enough I avoid ANSI C for such tasks as I prefer to find _back_doors_ using scripting languages.
ANSI C is _relatively_ easy understand but if Arduino is what you are interested in then I have done loads to access it in different languages AND platforms; including the Classic AMIGA A1200(HD) and under emulation using WinUAE...
However I have this little gem...

Code:

"SAMS Teach Yourself C For Linux Programming In 21 Days"
ISBN 0-672-31597-1

this is the bible.

Don't bother with cheap imitations

Another good reference is:

gnu libc manual

The C Programming language might be the bible, but it really is tough. Steve Summit has a good intro online: C Programming Notes One level above there is more, one of it are notes to "The C Programming language" (as far it's me they don't make it any better). good means easy. If that is too easy look at "C - A modern approach" by K.N King. I don't learn by projects, but by the books. Most tell me that is not a good approach, but i ain't got much talent (iow: i am slow).

---------- Post updated at 02:48 PM ---------- Previous update was at 02:45 PM ----------

youtube has a couple of videos about C. Some you might like. I missed that you already got a book (from Galileo Computing). If it was me i would use that for now +online ressources. As far it is me slightly too slow: https://www.youtube.com/watch?v=RpRRUQFbePU but entertaining. Then there is newboston: http://thenewboston.org/list.php?cat=14, which i don't know. Then there are youtube videos by people from India, but i can't find them right now. I liked them a lot (search for long ones).

---------- Post updated at 03:00 PM ---------- Previous update was at 02:48 PM ----------

"I mean, after 1 year VB.NET I must say I can't use the language properly, that gets me thinking." If you want to quickly do stuff yourself, then shell scripting is a better approach (Again: i am very slow, but i think that quite some people, hobbyists, would agree)