| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
These names are reserved for the compiler/library implementations.
|
| |
|
|
|
|
|
|
|
| |
- Add warning log level
- Change debug_log_level setting to enumeration string
- Map Irrlicht log events to MT log events
- Encapsulate log_* functions and global variables into a class, Logger
- Unify dstream with standard logging mechanism
- Unify core.debug() with standard core.log() script API
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename everything.
* Strip J prefix.
* Change UpperCamelCase functions to lowerCamelCase.
* Remove global (!) semaphore count mutex on OSX.
* Remove semaphore count getter (unused, unsafe, depended on internal
API functions on Windows, and used a hack on OSX).
* Add `Atomic<type>`.
* Make `Thread` handle thread names.
* Add support for C++11 multi-threading.
* Combine pthread and win32 sources.
* Remove `ThreadStarted` (unused, unneeded).
* Move some includes from the headers to the sources.
* Move all of `Event` into its header (allows inlining with no new includes).
* Make `Event` use `Semaphore` (except on Windows).
* Move some porting functions into `Thread`.
* Integrate logging with `Thread`.
* Add threading test.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, this lua code led to a crash:
local pcg = PcgRandom(42)
local value = pcg:next()
This was because if you called s32 PcgRandom::range(min, max) with the
minimum and maximum possible values for s32 integers (which the lua
binding code did), u32 PcgRandom::range(bound) got called with 0 as the
bound. The bound however is one above the maximum value, so 0 is a "special"
value to pass to this function. This commit fixes the lua crash by
assigning the RNG's full range to the bound 0, which is also fits to the
"maximum is bound - 1" principle, as (u32)-1 is the maximum value in the
u32 range.
|
| |
|
|
|
|
|
|
|
| |
Multiplying by a factor of 1/1000.f (rather than dividing by 1000.f) directly
introduces an error of 1 ULP. With this patch, an exact comparison of a
floating point literal with the deserialized F1000 form representing it is now
guaranteed to be successful.
In addition, the maxmium and minimum safely representible floating point
numbers are now well-defined as constants.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Add serializeHexString()
Clean up util/serialize.cpp
|
| |
|
|
|
| |
Use wide_to_utf8 and utf8_to_wide instead of wide_to_narrow and narrow_to_wide at almost all places.
Only exceptions: test functions for narrow conversion, and chat, which is done in a separate commit.
|
| |
|
|
| |
Also fix UTF-8 inner byte bounds and make unittest for case this fixes.
|
| |
|
|
|
|
| |
Also count multibyte sequences as "one" character.
Adds unittest for the bug reporter's case.
Fixes #2796.
|
| | |
|
| | |
|
| |
|
|
| |
warnings
|
| | |
|
| | |
|
| |
|
|
|
| |
Improve schematic file-saving interface
Add ability to create temporary test files
|
| |
|
|
| |
This simplifies NodeResolver logic and makes some interfaces cleaner.
|
| | |
|
| |
|
|
|
|
| |
- Add ability to explicitly reset NodeResolve state (useful for unittesting)
- Remove non-essential NodeResolve methods modifying state from INodeDefManager
- Add const qualifier to NodeDefManager and ContentFeatures serialize
|
| |
|
|
|
|
| |
Minor misc. NodeResolver cleanups
Prefix faux content type constants for testing with t_ to avoid
confusion or name collisions
|
| | |
|
| | |
|
| |
|
|
|
| |
-> Round negative numbers correctly CMakeLists.txt
-> Link Json with the static run-time library
|
| |
|
|
|
|
| |
Make sure to include random unittests in android builds, too
Use SWAP() macro
Ensure that negative ranges are tested as well in random unittests
|
| | |
|
|
|
Split unit tests into separate files under src/unittest/
Give better unittest diagnostics
Clean up some code
|
