b95bbd93f0
Space should be removed. Before: // Access struct members with . After: // Access struct members with. C should be capitalized. Before: // there is no Boolean type in c. We use ints instead. After: // there is no Boolean type in C. We use ints instead. Before: Header files are an important part of c as they allow for the connection of c After: Header files are an important part of C as they allow for the connection of C Before: Header files are syntactically similar to c source files but reside in ".h" After: Header files are syntactically similar to C source files but reside in ".h" Before: files. They can be included in your c source file by using the precompiler After: files. They can be included in your C source file by using the precompiler Before: as the c file. After: as the C file. Before: /* should instead be put in a c file. */ After: /* should instead be put in a C file. */ Before: /* Beyond the above elements, other definitions should be left to a c source */ After: /* Beyond the above elements, other definitions should be left to a C source */ Before: /* a header file but instead put into separate headers or a c file. */ After: /* a header file but instead put into separate headers or a C file. */
Learn X in Y minutes
Whirlwind tours of (several, hopefully many someday) popular and ought-to-be-more-popular programming languages, presented as valid, commented code and explained as they go.
We need YOU!...
... to write more inline code tutorials. Just grab an existing file from this repo and copy the formatting (don't worry, it's all very simple). Make a new file, send a pull request, and if it passes muster I'll get it up pronto. Remember to fill in the "contributors" fields so you get credited properly!
Contributing
All contributions are welcome, from the tiniest typo to a brand new article. Translations in all languages are welcome (or, for that matter, original articles in any language). Send a pull request or open an issue any time of day or night.
Please prepend the tag [language/lang-code] to your issues and pull
requests. For example, [python/en] for English Python. This will help
everyone pick out things they care about.
We're happy for any contribution in any form, but if you're making more than one major change (i.e. translations for two different languages) it would be super cool of you to make a separate pull request for each one so that someone can review them more effectively and/or individually.
For a detailed style guide, please review the full CONTRIBUTING guidelines.
License
Contributors retain copyright to their work, and can request removal at any time. By uploading a doc here, you agree to publish your work under the default Creative Commons Attribution-ShareAlike 3.0 Unported licensing included on each doc page.
Anything not covered by the above -- basically, this README -- you can use as you wish, I guess.