-
Updated
Oct 4, 2019
system-programming
Here are 317 public repositories matching this topic...
Is your feature request related to a problem? Please describe.
We don’t have anything in our code of conduct about how contributions are licensed and how we handle bad contributions or contributors. We should be explicit about that.
Describe the solution you'd like
A policy like Wikipedia’s about code.
Describe alternatives you've considered
N/A
Additional context
N/A
-
Updated
May 8, 2020 - Haskell
-
Updated
Feb 7, 2019 - C
-
Updated
Jan 11, 2017 - Shell
Update documentation
To include all language features and more examples
Concepts to cover in the Book:
- everything from spec.md
- package manager
- build system
-
Updated
Apr 18, 2018 - C++
-
Updated
May 20, 2020 - M4
As of alpha 2.685
there's a new action trigger_named_async_without_response
which can be used in favor of trigger_named
. Wrapper does not operate on trigger response anyway, so using the new method which works better for broader spectrum sounds like a good idea. More on that here: https://community.folivora.ai/t/floating-html-settings-menu/5788/44?u=worie
-
Updated
Jan 5, 2019 - C
-
Updated
Dec 4, 2018 - C
-
Updated
Apr 15, 2020 - HTML
-
Updated
Nov 28, 2016
-
Updated
Dec 4, 2019 - C++
-
Updated
Nov 12, 2018 - C
-
Updated
Jun 3, 2018
-
Updated
Apr 25, 2020 - Pascal
-
Updated
Oct 20, 2019 - C
-
Updated
May 18, 2020 - Pascal
-
Updated
May 9, 2020
Integrate clang-sanitizer in a special build and add it to Travis.
Even though we currently have valgrind run in Travis it would be nice to also have clang's sanitizers. Add the following sanitizers:
- address
- memory
- [undefined behaviour](http://clang.llvm.org/docs/UndefinedBehaviorSa
-
Updated
Aug 31, 2018 - C
Notes
(Auto)Generate documentation for functions.
(just another tag is needed)
Possibly: replace the praeprocessor macros in syscall_stubs with
something own. Atm, the praeprocessor macros' arguments aren't
informative ( They have to be named a1,a2, and so on. )
and I've to adapt the tags anyway, in order to generate the autoheaders in include/gen
-
Updated
Apr 22, 2020 - C++
Improve this page
Add a description, image, and links to the system-programming topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the system-programming topic, visit your repo's landing page and select "manage topics."
PR #342 revamps the checking of bounds declarations. It contains some examples of checking. @lenary noted that none of the examples have unsequenced assignments, where the order in which assignments happen is not specified. This means that pending sets are always empty in the examples. We should add an example where there are some unsequenced assignments.