Differences

This shows you the differences between two versions of the page.

--- tools:c [2024/06/03 05:40] – Humphrey Boa-Gart
+++ tools:c [2024/08/06 05:48] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-{{wst>iw-update}}
+{{wst>iw-cleanup}}
 ====== C ======
@@ Line 50: / Line 50: @@
 Whatever you do, don't use the beta of Xcode 3.1 right now. It's debugger is seriously borked, and the -g options on GCC don't work worth shit, either. I guess that's what you get for trusting Apple.
+===== Get Started =====
+Now that we all have a compiler I suppose we can get started right? Well first of all I have a few things to say:
+  * You may find similarities between this and other tutorials. Since we're teaching you the same thing (except I'm going very deep) this should be expected.
+  * It won't happen overnight, be patient, if you feel yourself getting frustrated, take a break. Go for a walk, smoke a bowl or whatever you do to relax. This isn't the easiest thing you'll do in your life but I assure you that if you stick with it, you'll be thankful you put the work in.
+  * Use your new found knowledge! There's no point learning a language and not doing anything else. Write (useful) programs, help others and generally help the community.
+  * **Download the Kernighan and Ritchie C book:** [[http://www.51cnnet.com/ebook/660-the-c-programming-language|Link]] -- This will teach you all you need to know to code in C.
+  * You can find more books on C, C++ and C# at [[http://www.51cnnet.com/]]
+===== C# =====
+This is the .NET version of C. It runs in a visual environment similar to Visual Basic.
+===== Ancient Tradition =====
+   #include <stdio.h>
+   int main(int argc, char** argv)
+   {
+       printf("Goodbye, cruel world!");
+       return 0;
+   }
+That's the basic emo version of "Hello World", as shown in K&R's The C Programming Language. If you're really interested in C, that book is a must have. It'll explain a lot that this tutorial will gloss over. Now, let us explain everything in this code selection.
+Line 1: ''#include <stdio.h>'' This is a preprocessor command telling the compiler that we're going to use some standard IO functions. These functions allow us to print things to the command line and read in information from the keyboard.
+Line 2: ''<nowiki>int main(int argc, char** argv)</nowiki>'' This line starts the "main" function, which is the primary entry point into your program. This function is common to all programs, and usually consists of calls to other functions and subroutines that actually do the work of the program. The word "int" here at the beginning refers to the fact that the main function returns an integer, usually 0. Other return values can be useful if your C code is intended to be used as a part of a shell script. The stuff inside the parentheses are the arguments for the main function, which are taken from the command line. The first argument here is an integer (hence the 'int') called "argc", and it tells us how many words were on the command line when the program was called. The second argument is the list of words called argv. argv[0] is the name of the program itself, as all lists in C start with 0 because system engineers and language writers back in the day were lazy. This program doesn't use this information, but others do.
+Line 3: The open curly brace here opens the primary code block for the main function. That's all it does.
+Line 4: ''printf()'' prints shit to the screen through a terminal emulator. The arguments it takes consist of a string in double quotes with special symbols for variables, followed by the list of variables in the order they're used. A full explanation of the function can be found [[http://www.cplusplus.com/reference/clibrary/cstdio/printf.html|here]].
+Line 5: Here, we return the integer that the main function expects, namely 0.
+Line 6: The closed curly brace here closes the primary code block for the main function.
+All lines of actual program code must end in a semicolon. Preprocessor lines don't need it, neither do the opening lines of function definitions nor curly brace lines. This is because the semicolon is about the most useless key on the keyboard when you're programming, so it got used for denoting the end of a command.
+Now, you might want to put some shit below the other, in two different lines. You might be thinking "That shit's easy, dawg, you'll make another printf() command, so we would have something like this:
+   #include <stdio.h>
+   int main(int argc, char** argv)
+   {
+       printf("Goodbye, cruel world!");
+       printf("brb suicide");
+       return 0;
+   }
+Thing is, when you try to compile the program with that, you will end up with shit like this:
+  Goodbye, cruel world!brb suicide
+Which is, well, not exactly what we're looking for.
+But why does this shit happen? It's because that after the end of a command, it positions an "invisible" cursor at the end of the text, and that's why it writes right after finishing the first line. We solve this with a new line, or "\n", that makes the cursor go into the next line. We will have something like this:
+   #include <stdio.h>
+   int main(int argc, char** argv)
+   {
+       printf("Goodbye, cruel world!\n");
+       printf("brb suicide");
+       return 0;
+   }
+And finally we'll end up with this:
+  Goodbye, cruel world!
+  brb suicide
+Victoly.
+If you wanna clear up the screen, simply use the command clrscr()
 {{tag>Tools Programming}}

User Tools

Site Tools

Differences