This might be better put in a topic separate from C, its own topic, since the network socket interface is accessible in Java, C#, Python, PHP, NodeJS, etc. . Since the socket api is written in C itself, the system calls, and most languages will use these same C system calls, I think it still works to offer the main explanation in C, then either have an example server and client in every language PHP, Ruby, Java, C#, Obj-C, etc
* Create index.md
This file introduces flex-grow: with screen shots and code samples. As with all of my commits, this is a proper contribution effort, neither copy & paste nor a links list.
* Update index.md
Added title: 'Flex Grow' to avoid Travis CL no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: updated individual code items & sentences
Added <code></code> tags to individual code items.
Sorry for so many commits. I just saw the styling guide.
* Create flexbox-display-flex.md (#2)
* Create flexbox-display-flex.md
This file introduces the concept of display:flex and flex-direction:[row | column].
* Rename guide/english/css/flexbox-display-flex.md to guide/english/css/flexbox-display-flex/index.md
Changed the folder structure to comply with index.md.
* Update index.md
Added title: Display Flex to avoid Travice CL no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: update individual code items.
Added <code></code> tags to individual code items.
Sorry for so many commits. I just saw the styling guide.
* Create index.md (#4)
* Create index.md
This file contains details about flex-basis, with screenshots and code samples. As with all of my commits, this is my own work not copy & paste or a lazy linkathon.
* Update index.md
Added the title; Flex Basis, to avoid Travis CI no frontmatter error.
* Update index.md
Added labels to the code blocks.
* fix: added labels for code items
Added <code></code> labels to individual code items.
Sorry for all of the commits. I just saw the styling guide. Doing my own QC.
The linter now checks that fences have languages and that those languages are
supported by PrismJS. The linter has been extended over the guide with its own
set of rules that only validate code fences.
Makes sure the test output console is initialized on backend as well as
classic challenges. Previously it was tied to SidePanel which was not
always present.
Removed some statements talking about the optimization potential of goto (which is mentioned but never specified), and I gave a possible use-case for goto followed by some constructs that can replace it, and ended on why goto is discouraged in C++
Added information about the memory behaviour of labels, the syntax to create a label, and where a label can actually be placed (within the same function).
