Here are some general rules to follow when writing Ruby and C code for CRuby:
Do not change code unrelated to your pull request (including style fixes)
Indent 4 spaces for C without tabs (tabs are two levels of indentation, equivalent to 8 spaces)
Indent 2 spaces for Ruby without tabs
ANSI C style for function declarations
Follow C99 Standard
PascalStyle for class/module names
UNDERSCORE_SEPARATED_UPPER_CASE for other constants
Abbreviations should be all upper case
Use the following style for commit messages:
Use a succinct subject line
Include reasoning behind the change in the commit message, focusing on why the change is being made
Refer to issue (such as Fixes [Bug #1234] or Implements [Feature #3456]), or discussion on the mailing list (such as [ruby-core:12345])
GitHub actions will run on each pull request.
There is a CI that runs on master. It has broad coverage of different systems and architectures, such as Solaris SPARC and macOS.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4