Want to relearn C, what book?

[bob4432]

Title says it all, learned C probably 15 yrs ago and never got a chance to really use it, so, well, can not program in C. Had an old book but figured there are so many technology differences between then and now, with all the different platforms, etc. I may as relearn with a strong core from this century.

My goals for your suggestions:
- Relearn good core C programming principles. I have a feeling a lot of this will come back to me, but I would like to make sure I will be guided correctly.

- I use multiple platforms, so will be programming for PC and also iOS, Android and other embedded systems where I have designed the hardware and would like to write my own code for it.

Please advise,
Bob

 

[Ken g6]

C is old. For Android you use Java, not C. I'm not sure what apple people use these days.

For embedded you use C, which hasn't changed in many years, C++ which has only changed a little, or maybe Java.

Edit: Point is for C an old book should be fine.

 

[bob4432]

Thanks

 

[CuriousMike]

C++ which has only changed a little,

LOL.

 

[K7SN]

OP the first book is still the best; K&R.

 

[TheRyuu]

Learn C The Hard Way

 

[SOFTengCOMPelec]

This page has a number of free C/C++ books

At least one of the C books via the above link, is a free (PDF), download.

 

[Jaydip]

I will recommend this one, had loads of fun reading it "Expert C Programming: Deep Secrets" http://www.amazon.in/Expert-C-Progr...l&keywords=exper+c+programming+deep+c+secrets and as some one else mentioned K&R C is still golden

 

[Exophase]

C is old. For Android you use Java, not C. I'm not sure what apple people use these days.

For Android I use C (and assembly), although there is some inevitable Java glue code involved to call the NDK libraries.

Java on Android is just not sufficient for the performance requirements of my app.

Even if you don't have similar performance requirements using something like C/C++ means you get easier portability between Android and iOS. So while they're not at all the vendor preferred language for either platform they're a good lowest common denominator.

For embedded you use C, which hasn't changed in many years, C++ which has only changed a little, or maybe Java.

It's worth getting a primer on the C revisions made in 1999 (going to assume these weren't learned 15 years ago) and maybe the ones in 2011. Possibly also some compiler extensions.

I wouldn't bother with a book, a website is fine. Especially since you can get ones with interactive tutorials. Like this: http://www.learn-c.org/

 

[bob4432]

Again, appreciate the comments.

 

[ninaholic37]

Head First C at my library was pretty easy to read, kid friendly with lots of pictures

 

[sckyless]

The C Programming Language 2nd Edition by Brian W. Kernighan & Dennis M. Ritchie

I first started learning programming with this book, then switched to iPhone development. This book added a great journey to my career.

 

[postmortemIA]

Any book is a reference, C is learned through the practice.

Be advised that C-style programming is sword with two edges in object-oriented world. People that know C very well tend to not use or understand advantages of OO languages like C++.

 

[bob4432]

Appreciate the info.

Any book is a reference, C is learned through the practice.

Be advised that C-style programming is sword with two edges in object-oriented world. People that know C very well tend to not use or understand advantages of OO languages like C++.

 

[SteveGrabowski]

The C Programming Language 2nd Edition by Brian W. Kernighan & Dennis M. Ritchie

This. K&R is one of the best written programming books I have ever seen, the style they code in is beautiful, and the book is full of fun exercises. I love the last chapter when you implement your own malloc. I really love APUE2 also, but that's for C programming on UNIX.

 

[bob4432]

One area I do have concerns is is for the smaller embedded items I am wanting to mess around with. Limited amounts of memory, direct hardware interaction, reading/writing to certain memory addresses, etc. I am assuming that I would just deal with the datasheets of the various components on that?

 

[sao123]

Forget C.
Forget C++.
Learn C#.

It does practically everything and is far superior to Java.
Web? Check
Windows\Linux? Check
Mobile? Check
Embedded? Check

 

[postmortemIA]

Nice troll, sao.

For embedded systems, might want to refresh yourself with posix standards use.

 

[SOFTengCOMPelec]

One area I do have concerns is is for the smaller embedded items I am wanting to mess around with. Limited amounts of memory, direct hardware interaction, reading/writing to certain memory addresses, etc. I am assuming that I would just deal with the datasheets of the various components on that?

Best to learn C first, without embedded complexity. (my opinion).

Embedded is best/easiest with a compiler, tailored to the specific microcontroller. Then I/O definitions, peripheral sets, inlining and possibly drivers, will be already done for you. Along with in most/all cases, much internet help as well.

If you are completely free as to what the hardware is. I would suggest something like the raspberry PI (2). As it readily has operating systems (such as Linux), C compilers (GCC) and advice over the internet/books/etc on how to do it.

But yes, you can do it straight from the datasheets. In some cases, you would need inline/intrinsics assembly code (E.g. Disable interrupts), but tailored compilers, would hopefully have most of the stuff built in, in some fashion.

Example (Cpuid) in the PC world, from Intels website. I.e. Some stuff may have to be done via ASM. But ideally it will already be part of your compiler.

void cpuid (cpuid_t *info, unsigned int leaf, unsigned int subleaf)
31
{
32
    asm volatile("cpuid"
33
    : "=a" (info->eax), "=b" (info->ebx), "=c" (info->ecx), "=d" (info->edx)
34
    : "a" (leaf), "c" (subleaf)
35
    );
36
}

 

[sao123]

Nice troll, sao.

For embedded systems, might want to refresh yourself with posix standards use.

Are you saying the .NET Micro Framework Architecture is insufficient for embedded development?

Native code is not the only acceptable approach to embedded projects nowadays.

 

[LevelSea]

Are you saying the .NET Micro Framework Architecture is insufficient for embedded development?

Is it real time? Then it very well may be insufficient.

Native code is not the only acceptable approach to embedded projects nowadays.

It can be, depending on your requirements.

 

[Donanza]

Man, you sure have a very long time since you learned C language.
I would strongly suggest C Primer Plus book.

 

[Crusty]

Are you saying the .NET Micro Framework Architecture is insufficient for embedded development?

Native code is not the only acceptable approach to embedded projects nowadays.

Writing an app for iOS, Android or Windows Phone is not embedded. You're targeting an operating system, not a piece of hardware.

 

[bob4432]

Understand, but I am talking about designing the hardware (schematic->board design->have boards made->assemble board/s->flash code, etc) myself which I have done in the past but always had somebody else for the programming portion

Writing an app for iOS, Android or Windows Phone is not embedded. You're targeting an operating system, not a piece of hardware.

 

[SOFTengCOMPelec]

Understand, but I am talking about designing the hardware (schematic->board design->have boards made->assemble board/s->flash code, etc) myself which I have done in the past but always had somebody else for the programming portion

Someone who has got many, many years of programming in C, embedded microcontroller experience (real time). Can with a degree of difficulty, tend to cope with what you have just described. Even if they have NOT got expensive test gear (such as emulators, logic analysers etc etc). Possibly even without the manufacturers development boards. Which can be amazingly cheap (like $75), in some cases.

But if someone who has never done (embedded real time C) programming on a microcontroller, with a reasonably complicated task to do/perform.

They will probably find the lack of pre-installed operating system (e.g. Linux), lack of diagnostic capabilities (No emulators etc), a really hard, uphill struggle, even to get it to do something quite simple. Let alone much more complicated things.

Peripherals tend to be difficult and fiddly/annoying to control in software, especially if you are completely inexperienced with them. There is a tendency if you get it wrong, at times, for the unit to just simply completely crash. Giving you no clue whatsoever, as to why, and what has gone wrong.

If you have got lots of time on your hands, and DON'T get frustrated easily, and really, really want to get your hands dirty, then do it.

It's much easier doing stuff like that in teams. Because you can split the work, and readily ask for advice from the many experienced engineers, who are working with you.

If you like. Try it for a few weeks and see how you get on. Without trying it, it can be difficult to put it into perspective, how hard and frustrating it can really be.

Analogy:
If there was someone who knew absolutely nothing about Electronics. Should they read a book on electronics for an hour or so. Then Design a 750 MHz 8 layer PCB, with complicated analogue/Digital circuitry, wave guides and create from scratch a large FPGA VHDL setup files ?

If it is a VERY simple, down to Earth task that your unit does, then things are not that bad.

EDIT: At times, I can be overly pessimistic and too negative. If others chime in with more confidence with this, please take that into account.
Since I'm not really sure exactly what you are trying to do here (overall, project wise), it is difficult to be accurate.
At the moment the project(s), could be anything, from a door bell unit, to a new control module for future space flights.