2017-03-03 fm4dd
The gcc compiler can optimize code by taking advantage of CPU specific features. Especially for ARM CPU's, this can have impact on application performance. ARM CPU's, even under the same architecture, could be implemented with different versions of floating point units (FPU). Utilizing full FPU potential improves performance of heavier operating systems such as full Linux distributions.
These flags can both be used to set the CPU type. Setting one or the other is sufficient.
This CSS stylesheet allows you to preview markdown files in VSCode using GitHub's mardown theme. This CSS was taken directly from the official GitHub Markdown repo. I replaced their top-level .markdown-body class with the body tag so it would work in VSCode, and added styling for the html tag to match GitHub's fixed-width container.
Copy the CSS file to your computer
Copy the github-markdown.css file below to your computer. You can put it anywhere you want, but I chose to put it in the same folder as my VSCode settings file.
Edit your VSCode settings
If you want to use this theme for all of your projects, then edit your User Settings file. If you just want to use this them
| #include <stdio.h> | |
| #include <string.h> | |
| /* UTF-8 character might be encoded in up to 4 bytes according to RFC | |
| * 3629 so to truncate it correctly care needs to be taken for such | |
| * characters. ASCII character are in single byte using 7 bits (max is | |
| * 127) so any multi-byte character has first byte higher then | |
| * 127. Because first byte in multi-byte sequence is encoding how many | |
| * bytes this sequence has we can easily check for it looking for the | |
| * first byte in sequence and see how many bytes more to truncate. |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
