- 29 10月, 2015 1 次提交
-
-
由 Andy Isaacson 提交于
The intent of UNITY_WEAK_PRAGMA is that we have weak symbols for setUp and tearDown in unity.o, so that developers can override these symbols if needed but the link works right if they are not defined. In order to do this using #pragma, the pragma and the definition of the function (not the declaration) need to be present in the same translation unit (source code file). Previously, the UNITY_WEAK_PRAGMA code was just declaring the setUp function, but not defining it, which means that developers had to add an empty setUp function to their tests in order to link.
-
- 03 8月, 2015 1 次提交
-
-
由 Alexander Mueller 提交于
-
- 15 7月, 2015 1 次提交
-
-
由 Nimrod Zimerman 提交于
This eliminates a compiler warning for certain compilers.
-
- 01 7月, 2015 1 次提交
-
-
由 Andrew Burks 提交于
Fixes #3: unity_fixture tests don't build. unity.c and unity_fixture_malloc_overrides.h neglected to include <stddef.h> even though the reference 'size_t' and 'NULL'.
-
- 20 6月, 2015 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
- casting to a (void*) was giving warnings to some compilers about double casting - casting from a u8 to u16/32/64 was giving warnings about changing alignment requirements
-
- 19 6月, 2015 1 次提交
-
-
由 ThingamaByte, LLC 提交于
-
- 23 5月, 2015 1 次提交
-
-
由 Sergey Gusarov 提交于
Double castings look ugly. And if Unity is compiled with -Wcast-qual flag these type castings produce a lot of warnings: unity/src/unity.c:490:80: warning: cast discards ‘__attribute__((const))’ qualifier from pointer target type [-Wcast-qual] UnityPrintNumberByStyle(*(UNITY_PTR_ATTRIBUTE const _US16*)(void*)ptr_exp, style); ^
-
- 23 4月, 2015 1 次提交
-
-
由 Eivind Tagseth 提交于
Compares two strings until maximum n bytes (i.e. strncmp()).
-
- 12 3月, 2015 1 次提交
-
-
由 Greg Williams 提交于
-
- 18 1月, 2015 1 次提交
-
-
由 nimrodz 提交于
Primarily - * Added "static" to static functions. * Added proper signature with "void" to functions without arguments. * Marked unused arguments with "(void)". * Removed entirely unused static functions. * Added "const" to preserve const-correctness. * Added function prototypes for external functions.
-
- 16 12月, 2014 1 次提交
-
-
由 Zane D. Purvis 提交于
- `UNITY_WEAK_ATTRIBUTE`, if defined, is placed before declarations of weakly linked symbols. If not manually defined, it will be automatically set to `__attribute__((weak))` on GCC and Clang, except for Clang for Win32. - `UNITY_WEAK_PRAGMA`, if defined, will cause preprocessor to emit `#pragma weak setUp`, etc. Ignored if `UNITY_WEAK_ATTRIBUTE` is defined. - `UNITY_NO_WEAK` undefines both of the above resulting in no weakly linked symbols. Work around for ThrowTheSwitch/Unity#93
-
- 07 12月, 2014 1 次提交
-
-
由 Zane D. Purvis 提交于
This change makes parsing the results easier for tools like ceedling, which was choking when a test used stdout and there wasn't an EOL after "PASS" (ThrowTheSwitch/Ceedling#41).
-
- 03 12月, 2014 1 次提交
-
-
由 kotofos 提交于
-
- 09 11月, 2014 1 次提交
-
-
由 @gageas 提交于
-
- 02 11月, 2014 2 次提交
-
-
由 Sergey Gusarov 提交于
But they look a bit different.
-
由 Sergey Gusarov 提交于
warning: cast discards ‘__attribute__((const))’ qualifier from pointer target type [-Wcast-qual] FYI, "-Wcast-qual" is not a default option. The main idea: If some function receives "const void*" why should it operate with "void*" (or something) afterwards (after casting)?
-
- 27 10月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
reworked character strings to be an array type so that storage classes are handled better for picky compilers.
-
- 03 9月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 02 9月, 2014 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
-
- 31 7月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
support tests named spec as well. clean up UnityBegin to make us not have to dig inside it to inject the filename. Add UNITY_OUTPUT_START() and UNITY_OUTPUT_COMPLETE() for future use.
-
- 30 7月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
rearranged project to centralize all self-test stuff under test directory. only pull in includes when required.
-
- 23 7月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
- rename the custom FLOAT_TRAIT type because the old name was poor
-
- 22 7月, 2014 4 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
added macros for IS_DETERMINATE and IS_NOT_DETERMINATE
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
- rework to not bother with any of the ever-changing test frameworks in Ruby (sigh) for self-testing - started working on cleaner floating point support. more coming.
-
- 09 7月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 01 7月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
* Add UNITY_BEGIN and UNITY_END macros to simplify usage * Improve RUN_TEST to make line_num optional where possible
-
- 23 5月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 08 3月, 2014 1 次提交
-
-
由 Mark VanderVoord 提交于
Fixed initialization of data structure by just doing it manually instead of statically (goodbye compiler warnings!)
-
- 16 2月, 2014 1 次提交
-
-
由 Jakob Holderbaum 提交于
By printing this newline, the filepath of the failing assertion does not get preceded by the dot which represents a running test. This gives the advantage, that the complete output of unity can be used as it is with a makefile in vim. Every error gets displayed in the quickfix and you can jump appropiately.
-
- 23 9月, 2013 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 22 9月, 2013 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 17 9月, 2013 1 次提交
-
-
由 Antony Male 提交于
Microchip's XC16 and friends, when used with dsPICs, require that all pointers to memory which could possibly be in EDS space by adorned with __eds__, e.g. __eds__ int* p_int Adding the macro UNITY_PTR_ATTRIBUTE allows Unity's pointers to be decorated with whatever ridiculous attributes the compiler requires.
-
- 28 6月, 2013 1 次提交
-
-
由 Antony Male 提交于
This patch fixes testEqualIntArrays in the unity test suite on 16-bit architectures. TEST_ASSERT_EQUAL_INT_ARRAY calls UnityAssertEqualIntArray with 'style' set to UNITY_DISPLAY_STYLE_INT. UNITY_DISPLAY_STYLE_INT is defined as UNITY_DISPLAY_STYLE_AUTO + UNITY_DISPLAY_STYLE_INT{16,32,64} (depending on the int width). However, the switch statement in UnityAssertEqualIntArray has special cases for the width-specific display styles, but these comparisons are carried out without clearing the UNITY_DISPLAY_STYLE_AUTO flag. This means that if 'style' is UNITY_DISPLAY_STYLE_INT, and the int width is, say, 16, bits, the default case will be hit, and elements compared as if they were 32 bits wide. Unsurprisingly this causes a failure in the test named above.
-
- 06 2月, 2013 1 次提交
-
-
由 James Hood 提交于
-
- 05 2月, 2013 1 次提交
-
-
由 Alex Rodriguez 提交于
-
- 27 11月, 2012 1 次提交
-
-
由 Bryan A. Jones 提交于
- Change type of floating-point constants to single/double precision as appropriate.
-