What's a good way to get c information? [closed] - c

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
What I mean by this question is unlike other programming languages where I could simply just google the phrase "implementing comparable interfaces java" or "graphics drawing python", whenever I google a C problem, it seems that the majority of the results are about C# or C++
I've tried saying ANSI C or C99 instead but that's not too successful. I lent my friend in college my K&R C bible, is there any websites that are good definitive c sources?

http://www.cprogramming.com/
Also that K & R C book is available as a pdf :)

What seems to work well for me is to put what I am looking for and follow it with " in c programming"
so if I wanted info on using structs in c i would put "structs in c programming"

Once you get a good grasp as how OO works, you can transfer algorithms and patterns to C easily.
Also, currently the best C referente IMHO is StackOverflow.com.

I have a good C reference book called C Programming FAQ. I found a similar website that helps tackle most of the common problems.

Related

What exactly is the SEXP data type in R's C API and why is it used? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am aware of the wikipedia page on SEXP, and I know that it stands for symbolic expression. I know (vaguely) SEXP is notation to refer to tree data structures in Lisp, but I want to know what motivated the developers to call the data type of R objects in C SEXP. Why SEXP?
I am also confused because if R was made in C and Fortran, why would notation from Lisp be used? Or is SEXP a more general term? Maybe I'm missing something here.
R is, internally, kind of like Scheme with an S-compatible syntax. A lot of R's internals derive from Scheme concepts, like cons cells and lexical environments.
Back in the late 90s, I worked on a new (at the time) serialisation format for R; see my honours project paper, which explains a lot of this. (The email address on that paper isn't valid any more, so don't use that.)

Is it possible to google for C without getiing C++ in the results? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I know this isn't really a programming question but I wondered if anyone knew if there was a way of constructing a google query that returned results about the C language without results for C++.
Use your normal search value and add -c++ and -cpp(including the minus symbol)
Try something like: c programming -"c++"
Appears to work on quick inspection.
Advanced Google search
The advanced options for Google allow you to ban words, so you can just ban "C++" and whatever else you don't want.
Yes, you can!
c -++
for example : searching for new york without hotels
new york -hotel

Taking notes when programming? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I just got my first programming book, and I just started programming.
I have a little question. Should I take notes while reading the book, or should I just memorize, and refer back if I forget something?
Thanks
Never read from just 1 book, read multiple books on the subject to get a better picture.
for C read The C Programming Language, How To Program - C, C: A complete reference and then C a reference manual(by Harbison and Steele) touching on at least C99
Take notes, keep a book handy at all times - think before you ink though.
Always sit by a computer + text editor + compiler (yes, do not use an IDE - learn with manual compilation)
Learn good debugging techniques, gdb is fine to start off with(although has a significant learning curve)
Be attentive to what is being said in the books and - also do not forget to experiment all the time. Programming is best learnt by doing it/practicing it.
The best thing to do is to understand what is being said to you by the book, I've tried memorizing before.. it doesn't work I would suggest a bit of both, but mostly understanding it that way you would know what you are coding also practice your level of confidence of coding will increase and you'll continue to want to code more.

Key differences between Ruby and C [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What are the key differences between Ruby and C?
They are almost totally different.
Ruby
Strong, dynamic typing
Purely object oriented
Automatic garbage collection and no pointers
Interpreted (or JIT compilation with JRuby/IronRuby)
Reflective
Supports functional programming (closures, coroutines, etc.)
No preprocessor or macros
C
Weak, static typing
Procedural (not object oriented)
Not garbage collected and has pointers
Compiled
No reflection
Does not support functional programming
Has a preprocessor and supports macros
To Ruby From C and C++
Why do you ask? Do you have a specific project or goals in mind?
In addition to what others have already mentioned; I'd also say that some key differences to keep in mind is that the C family is much more portable....or rather, much easier to distribute the finished software. C programs will also be much faster than Ruby...whether that is important or not depends on what you are building (well, that's ALWAYS important, but it isn't a make or break proposition for a lot of programs).
Ruby is just simply a beautiful language to work with (do not underestimate the importance of a language that works with you); developing programs is much quicker in Ruby than C ( C is a compiled language, so that is to be expected )...Ruby is also a pretty simple language to learn; most people consider C to be fairly tough for newbies to pick up.
-- edit --
wow, just saw this was a 3 year old thread....my bad

Where can I learn more about pointers? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I do not understand pointers. Where can I learn more about them?
The best way to understand pointers is to write assembly, I found.
try http://home.netcom.com/~tjensen/ptr/pointers.htm
Richard Buckland's lecture about pointers is highly recommendable.
I personally like the quite straightforward cplusplus.com tutorial on pointers.
My C language bible is "C-The complete Reference" by Schildt. Chapter 5 is all about pointers.
If you just think of the pointer as being the address of something - like the address in a letter telling you how to find the house - then you will be most of the way there.
Deitel & Deitel C how to program
C++ version of the book preview on Google Books
Pointers on C (Paperback)
by Kenneth Reek (Author)
http://www.amazon.com/Pointers-C-Kenneth-Reek/dp/0673999866
Lot's of great references suggested. I'd just like to add one thing:
Play with them!
Once you understand them on the theoretical level from the books, articles, lectures, videos above then you should set yourself to some task that that will allow you to make mistakes, find those mistakes and fix mistakes.
Think about implementing something like a linked list (double or singly linked), binary tree, or similar data structure. Then write some code to insert and remove values from your structure. In completing the task you'll definitely feel more comfortable with them, and get some experience debugging pointer problems.

Resources