These are chat archives for learnclang/general
That's right, it's on Wednesday.
It was changed shortly after announcing that it was Thursday, sorry about that. If you scroll up, you'll find some more background to it.
I'm still trying to find the best way to keep updates like these from getting lost in the chat, the safest thing to do at the moment is to keep an eye on the repository related to the screencast, we might spend a little more time customising the front-page of the Twitch channel as well.
Here are what I would consider key-points for an announcement:
It's great to see so many new faces here!
As an introduction to what you've gotten yourself into, have a look at this Wiki page, which I will attempt to keep up to date with our latest high-level goals of the group as it evolves.
@lucienfostier and @Jarombrand, welcome in!
Noted about the a git screencast. If you can, add a +1 in the thread here: learnclang/about#1 so we can keep track of how many are interested.
There will be a live chat to the side of the stream that you may ask questions in or converse with other viewers. To ask a question to Sebastian (@byron), try prefixing it with "@byron" so that it becomes a little more clear to Sebastian that it is meant for him.
Also keep in mind that there looks to be a delay between the time of recording and it actually reaching any of us of about 5 seconds or so, which means he won't be able to visually react to questions until double that time (5 seconds to reach him, and another 5 seconds for a response to reach us).
There will also be a Q&A after the 45 minute mark during which Sebastian will try and answer any remaining questions.
See you in 30 minutes!
printf()doesn't add a newline by default, as opposed to Python's
voidis the same as passing nothing.
int main(int argc, char* args): First argument is the amount of arguments that have been passed, the second argument contains the names of arguments as an array.
fprintfprovides an option to print to
stderr, which is the error stream as opposed to
stdoutwhich is regular output. Both of these channels exist in Python as well
constfor reusable constant values
#definereplaces text before compilation, which can produce hard-to-discover bugs. Better to use standard variables.
#include's you do, like
#include <windows.h>which is only available on Windows, for instance.
<>(ie. system headers) are part of the language itself, and should exist on any platform.
First of all, thanks for everyone who attended, hope you found it as informative and mindboggling as I did! :)
For any questions, feel free to speak up here or post a thread in the GitHub issues section here:
There are also some resources available in the Wiki for the organisation, here:
Learn C the Hard Way is also a very interesting read, on the more practical side of things, as opposed to K&R which is more academic and theory.
I tried to compile it with gcc and I got an error saying that
loop initial declarations are only allowed in C99 mode
I've been able to compile though using the following syntax:
gcc rps.c -o rps.exe -std=c99