-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
func_80183070 to SleepForever #1686
base: main
Are you sure you want to change the base?
Conversation
Looks like main needs to be merged in and conflicts resolved. |
@@ -1,6 +1,6 @@ | |||
#include "libc64/sleep.h" | |||
|
|||
void func_80183070(void) { | |||
void Sleep_Forever(void) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So taking another look at OoT, they have an additional log message that uses the word freeze which I'm wondering if should actually use in the function name (func_800D31A0
is the function in OoT).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For reference, OoT (zeldaret/oot#2315) looks to rename the file to sys_freeze
(no word on the function yet, though I think just Freeze
or Freeze_Forever
works) which I agree with.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree with OoT's decision to call it sys_freeze
. The word freeze in the context most appropriate is a system hang, or an unintended fault of software/hardware causing unresponsiveness, and not a deliberate action. Additionally, calling Sleep_Forever
does not necessarily result in an unresponsive system.
The "freeze!" comment in OoT more seems like a joke than a hint at the actual source name.
No description provided.