Age | Commit message (Collapse) | Author |
|
|
|
This is a simple implementation of runtime structs, which was taken
from lavignes' librts, and modified to make it alot easier to work with.
Link to librts:
https://github.com/lavignes/librts
|
|
These macros help with finding the minimum, and maximum of two values.
|
|
This greatly simplifies the code for it, and helps make the codebase
more generic.
|
|
`get_keyword_offset_ptr()`
|
|
offset before dereferencing `ret`, and also check if the dereferenced
return pointer is NULL
|
|
|
|
This needs to be done, in case we get a string that's `NULL`.
|
|
This callback is needed because `pr_type` is a `uint8_t`, but the
keyword type is `TYPE_INT` which assumes that the type is an `int`.
|
|
and `create_key_value_str()`
|
|
This can be used to help with `create_key_value_file()`, and
`create_key_value_str()`.
|
|
`create_key_value_file()`
These functions will help in making the creation of key-value files more
generic.
There still needs to be some more work done on it, but that can be done
later.
|
|
|
|
This will be used for creating a getter callback for keywords.
I also renamed `keyword_cb` to `set_keyword_cb`, aswell as renamed
`callback` to `set_callback` in `struct keyword`.
|
|
`create_pull_request_dir()`
This is because we won't be creating patch files for remote branches.
|
|
`create_pull_request_branch()`
We don't need to do this anymore, since `dir_path_name()` now does that.
|
|
|
|
|
|
This takes in the PR, the index of that PR, and the repo the PR is for,
and will create a branch for that PR in the given repo.
Currently it only supports working with remote branches, but eventually
it'll support patch files too.
|
|
This function takes a null-terminated `git_repo` array, and the name of
the repo to get, and will return said repo if found, and NULL if not.
|
|
It was basically not properly skipping over to the next forward slash.
The solution was to have it get the span of the forward slashes, and
checking if we hit the null terminator after trying to find the next
forward slash. If we do hit the null terminator, we add the forward
slash span to the cursor.
|
|
in `parse_dsv_str()`
|
|
|
|
`parse_key_value_file()`
This is a much better way of doing it than what was done previously.
|
|
This also cleans it up a bit.
|
|
This function removes any whitespace found at the end of the supplied
string.
This can be useful when you have a string with whitespace throughout it,
but only want the whitespace at the end removed.
|
|
|
|
in `create_socket()`
|
|
This is designed to make it more readable when printing the logs to
a terminal, or terminal emulator.
|
|
|
|
`log()` macro
|
|
This works exactly like `printlog()`, except it uses variadic arguments.
|
|
`vprintlog()` prints out the provided string to either syslog, stderr,
or stdout depending on the output type.
|
|
This works the same as `vformat_len()`, except that it copies `args`
into a temporary `va_list`.
This can be useful when you're already using a `va_list`, and thus need
to copy the list already.
|
|
`format_len()`
|
|
This works exactly like `format_len()`, except that it uses `va_list`
rather than variadic arguments.
|
|
This get's rid of a long standing TODO.
|
|
|
|
Much like with `create_socket()`, this just makes it easier to get
the sockaddr from a socket descriptor, without having to duplicate
everything over, and over again.
|
|
This function makes makes it easier to create sockets, without having to
duplicate code.
|
|
This function takes a `sockaddr`, along with the length of the
`sockaddr`, and creates a string from that address.
|
|
keyword: Remove trailing whitespace from the right hand side in
`parse_key_value_file()`
I didn't realize this would create a parsing bug.
|
|
`parse_key_value_file()`
|
|
This was a mistake that I didn't even notice until now, lol.
|
|
`parse_config()`
This greatly simplifies the code, and makes it more readable.
|
|
`free_git_branch()`
Forgot to commit this when changing `merge_branch` to a string.
|
|
|
|
|
|
`parse_key_value_file()`
|
|
and make it more generic
This will allow us to parse pretty much anything with a key, value pair
seperated by some delimiter(s).
|