I've been learning from this site, and it seems good, and the general consensus online is that it's one of the better online tutorials/books for learning C++.
* Fish Shell tutorial
* Typo
* Typo and shortened a bit
* Update fish.markdown
Co-authored-by: Andre Polykanine <ap@oire.me>
* Update fish.markdown
Co-authored-by: Andre Polykanine <ap@oire.me>
* Update fish.markdown
Co-authored-by: Andre Polykanine <ap@oire.me>
* Update fish.markdown
Co-authored-by: Andre Polykanine <ap@oire.me>
* Update fish.markdown
Of course, it's fish, not bash...
* Update fish.markdown
No translators for an english article...
Co-authored-by: Andre Polykanine <ap@oire.me>
* Adds extra clarity to enum value assignment.
The previous statement shows only 1 way to declare enums, and it happens
that they specify a starting value. I clarify that a starting value is
not necessary and that all enum value could contain user specified
values.
* Added clarity to `includes` section.
specified that angle brackets are for system libraries and not just
standard libs. I also added an example of relative paths in the local
include statements.
* Added more clarity for function prototyping and main return vals.
I cleaned up some formatting; then added some clarity to how function
prototyping works, as well as recommend techniques.
* Fixed the mention of character sizes. they are not always 1 byte
* Added clarity about floating point arithmetic.
The previous comments on floating points made it feel like there was
something broken with doing comparison and arithmetics with floating
point types. I added clarity about how floats are stored in memory and
why they seem to behave strangly when used in arithmetic expressions.
* reworded boolean stuff for better clarity on _Bool type in C99
* Adds not about binary assignment
* Added clarity for value roll over
* Added section on multiple return values.
C doesnt allow returning of multiple values, so i added a section on
returning multiple values through pointers.
* added section break for printing special characters
* fix typo
Co-authored-by: Andre Polykanine <ap@oire.me>
* fix typos
Co-authored-by: Andre Polykanine <ap@oire.me>
* fix markdown syntax
Co-authored-by: Andre Polykanine <ap@oire.me>
* fix markdown syntax
Co-authored-by: Andre Polykanine <ap@oire.me>
* fix markdown syntax
Co-authored-by: Andre Polykanine <ap@oire.me>
* reword with better english
Co-authored-by: Andre Polykanine <ap@oire.me>
* reword with better english
Co-authored-by: Andre Polykanine <ap@oire.me>
Co-authored-by: Andre Polykanine <ap@oire.me>
The json code block renders fine in Github Flavored Markdown on Github, but not on the learnxinyminutes.com/docs/toml page. Because there isn't any syntax highlighting for this section anyway, I switched it to vanilla code block.
* [mongodb/en] Write introduction and getting started
* [mongodb/en] Write code sample for CRUD operations
* [mongodb/en] Write code sample for operators and database operations
* [mongodb/en] Write further reading
* [mongodb/en] Minor fixes for Markdown
* [mongodb/en] Made each line 80 characters long
The pygments highlighter does not recognize `==begin` and `==end`
without a newline before `==end`. For this reason it will never end the
comment. This resulted in 95% of the Raku document being highlighted as
a comment.
We replace most `=begin` and `=end` with standard quotes `#`. In some
places I retain `=begin` and `=end` when they are indented (this works
fine in pygments).
