RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-31 09:48:11 +00:00
Code Issues Activity Actions

Everywhere: Rename ASSERT => VERIFY

Browse source 
(...and ASSERT_NOT_REACHED => VERIFY_NOT_REACHED)

Since all of these checks are done in release builds as well,
let's rename them to VERIFY to prevent confusion, as everyone is
used to assertions being compiled out in release.

We can introduce a new ASSERT macro that is specifically for debug
checks, but I'm doing this wholesale conversion first since we've
accumulated thousands of these already, and it's not immediately
obvious which ones are suitable for ASSERT.
This commit is contained in:
Andreas Kling 2021-02-23 20:42:32 +01:00
parent b33a6a443e
commit 5d180d1f99
725 changed files with 3448 additions and 3448 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Kernel/Time/RTC.cpp
View file

@ -62,7 +62,7 @@ void RealTimeClock::reset_to_default_ticks_per_second()
{
InterruptDisabler disabler;
bool success = try_to_set_frequency(1024);
ASSERT(success);
VERIFY(success);
}
// FIXME: This is a quick & dirty log base 2 with a parameter. Please provide something better in the future.
@ -91,7 +91,7 @@ bool RealTimeClock::try_to_set_frequency(size_t frequency)
}
bool RealTimeClock::is_capable_of_frequency(size_t frequency) const
{
ASSERT(frequency != 0);
VERIFY(frequency != 0);
if (frequency > MAX_FREQUENCY)
return false;
if (32768 % frequency)
@ -102,7 +102,7 @@ bool RealTimeClock::is_capable_of_frequency(size_t frequency) const
}
size_t RealTimeClock::calculate_nearest_possible_frequency(size_t frequency) const
{
ASSERT(frequency != 0);
VERIFY(frequency != 0);
return frequency;
}