Skip to content
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

cleanup: Align internal logger with external on type of source line. #2820

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

iphydf
Copy link
Member

@iphydf iphydf commented Dec 28, 2024

We use uint32_t everywhere now. It's easier that way, and line numbers are never negative.


This change is Reviewable

@iphydf iphydf added this to the v0.2.21 milestone Dec 28, 2024
@iphydf iphydf changed the title Uint line cleanup: Align internal logger with external on type of source line. Dec 28, 2024
Copy link
Member

@JFreegman JFreegman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 approvals obtained (waiting on @iphydf)


other/DHT_bootstrap.c line 123 at r1 (raw file):

                      const char *func, const char *message, void *userdata)
{
    fprintf(stderr, "[%s] %s:%d(%s) %s\n", strlevel(level), file, line, func, message);

Is is okay to format a uint32_t with %d?

@github-actions github-actions bot added the cleanup Internal code cleanup, possibly affecting semantics, e.g. deleting a deprecated feature. label Jan 12, 2025
Copy link
Member Author

@iphydf iphydf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 approvals obtained (waiting on @JFreegman)


other/DHT_bootstrap.c line 123 at r1 (raw file):

Previously, JFreegman wrote…

Is is okay to format a uint32_t with %d?

Ish, but yes it's cleaner to do %u. Done.

@iphydf iphydf force-pushed the uint-line branch 2 times, most recently from 958d91e to 73be7d4 Compare January 12, 2025 23:26
We use `uint32_t` everywhere now. It's easier that way, and line numbers
are never negative.
@toktok-releaser toktok-releaser merged commit 5bd8a85 into TokTok:master Jan 13, 2025
65 checks passed
@iphydf iphydf deleted the uint-line branch January 13, 2025 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Internal code cleanup, possibly affecting semantics, e.g. deleting a deprecated feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants