| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
| |
|
|
|
|
|
|
|
|
|
| |
This fixes warnings about passing signed chars to them (apparently they
are implemented as macros that do array lookups without checks in some
platforms, yay)
Specifically:
functions=isalnum|isalpha|isdigit|isspace|isxdigit|tolower|toupper
sed -ir "s/$functions/g_ascii_&/g" **/*.c
|
| |
|
|
|
|
|
| |
(used to encode >16-bit chars). Added code to parse those *and* the ability
to encode >16-bit Unicode in UTF-8. Also sending this upstream. This should
fix #1121.
|
| |
|
|
|
|
| |
Few BitlBee-specific diffs now. Annoyingly need to link to libm now for the
use of the function pow() since the lib now does its own number parsing...
|
| |
|
|
|
|
|
| |
json.c: In function ‘json_parse_ex’:
json.c:260:30: warning: ‘string_length’ may be used uninitialized in this function [-Wmaybe-uninitialized]
json.c:358:16: warning: ‘string’ may be used uninitialized in this function [-Wmaybe-uninitialized]
|
| |
|
|
|
|
|
|
| |
strto(d|l) fix because I can just use GLib instead of reinventing the wheel.
This should fix corruption issues with tweets in Cyrillic. I've double-
checked this code against http://en.wikipedia.org/wiki/UTF-8 now and it looks
correct to me.
|
| |
|
|
|
|
| |
type to long long, the parser was still using strtol to convert numbers,
truncating large numbers to LONG_MAX. Bug found by Artem Savkov, thanks!
|
| |
|
