Sebastian Pipping
5dbc857f47
tests: Cover helper unsignedCharToPrintable
2021-05-07 18:25:08 +02:00
Sebastian Pipping
271efb6069
tests: Cover accounting
2021-05-07 18:25:07 +02:00
Sebastian Pipping
8af7d22ff0
lib: Allow test suite to access raw accounting values
2021-05-07 18:25:07 +02:00
Sebastian Pipping
b1d039607d
lib: Protect against billion laughs attacks (approach 3.0.21)
2021-05-07 18:25:07 +02:00
Sebastian Pipping
df42f935bf
Increase precision in existing MIT headers based on Git history
2021-05-02 19:53:29 +02:00
Sebastian Pipping
f29b48cfca
Unexpose function _INTERNAL_trim_to_complete_utf8_characters ( #457 )
2021-04-05 21:44:15 +02:00
David Loffredo
561773607c
handle unused parameters with the usual (void)param; statement rather than gcc-specific attribute
...
Signed-off-by: David Loffredo <loffredo@steptools.com>
2019-08-16 09:52:09 -04:00
clang-format
d248bbd940
Mass-apply clang-format 9 using ./apply-clang-format.sh
2019-08-03 21:31:44 +02:00
Sebastian Pipping
21e11f7782
internal.h: Fix UNUSED_P for GCC 3.3 ( fixes #288 )
2019-07-20 16:42:21 +02:00
Yury Gribov
30f8c30b6a
Hide private symbols.
2018-09-20 17:45:01 +01:00
Sebastian Pipping
8711ee3054
Leave no doubt about align_limit_to_full_utf8_characters being internal
2017-08-23 17:41:17 +02:00
Sebastian Pipping
a704c940a4
Inline copyright headers with C/C++ code where missing ( #116 )
2017-08-12 21:02:41 +02:00
Sebastian Pipping
be917d9f84
Cover UTF-8 limit correction; some tests fail
...
Failing tests are:
[-] UTF-8 case 3: Expected movement by -1 chars, actually moved by 0 chars: "\xdf"
[-] UTF-8 case 4: Expected movement by 0 chars, actually moved by -1 chars: "\xdf\xbf"
[-] UTF-8 case 5: Expected movement by -1 chars, actually moved by 0 chars: "\xef"
[-] UTF-8 case 6: Expected movement by -2 chars, actually moved by -1 chars: "\xef\xbf"
[-] UTF-8 case 7: Expected movement by 0 chars, actually moved by -2 chars: "\xef\xbf\xbf"
[-] UTF-8 case 8: Expected movement by -1 chars, actually moved by 0 chars: "\xf7"
[-] UTF-8 case 9: Expected movement by -2 chars, actually moved by -1 chars: "\xf7\xbf"
[-] UTF-8 case 10: Expected movement by -3 chars, actually moved by -2 chars: "\xf7\xbf\xbf"
[-] UTF-8 case 11: Expected movement by 0 chars, actually moved by -3 chars: "\xf7\xbf\xbf\xbf"
2016-05-20 22:29:47 +02:00
Sebastian Pipping
69746f5ab2
Address all "unused parameter" warnings
2016-05-07 17:24:35 +02:00
Karl Waclawek
fd79deac8b
Fix for bug #1548182 .
2006-11-26 17:35:37 +00:00
Greg Stein
d7a766e9df
Suggested fix from jtalkington@users.sf.net.
...
See bug #765227 .
* lib/internal.h:
(FASTCALL, PTRFASTCALL): only define these macros for the GNU C compiler
on i386 platforms. apprently, they do not work well on PPC ports.
2003-09-28 21:57:22 +00:00
Fred L. Drake, Jr.
f668c507d9
Be more defensive: only enable the *CALL macros when using GCC on
...
Linux, since we know the current definitions work there and have a
positive effect.
This closes SF bug #692878 .
2003-03-14 17:25:12 +00:00
Fred L. Drake, Jr.
cc454566be
Fix FASTCALL for GCC on Solaris (SF bug #692878 ).
...
This file is becoming a liability.
2003-03-12 23:02:11 +00:00
Karl Waclawek
5ca83cc911
Changed calling convention macros to differentiate between
...
different types of function calls - see comments in internal.h.
2002-09-20 03:42:43 +00:00
Fred L. Drake, Jr.
d784ead9cb
A last-minute report suggests a problem with this using at least some
...
versions of egcs, so disable FASTCALL for GCC as well. We are now not using
this for any platform. ;-(
2002-09-06 21:49:57 +00:00
Fred L. Drake, Jr.
9bd525992b
Disable FASTCALL on Windows since it turned out not to be as effective
...
as hoped. Leaving the definition in the file so we'll know what it
was that didn't work, and hopefully find something better in the
future.
2002-09-06 21:29:46 +00:00
Fred L. Drake, Jr.
ca524b2c69
Added new header for common internal definitions. These are all performance-
...
related at the moment.
2002-09-05 01:56:29 +00:00