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

Resolve GBC vs. CGB mismash #491

Merged
merged 3 commits into from
Jan 30, 2025
Merged

Resolve GBC vs. CGB mismash #491

merged 3 commits into from
Jan 30, 2025

Conversation

SatoMew
Copy link
Contributor

@SatoMew SatoMew commented Jan 30, 2025

Both are used so I went with CGB over GBC. The latter only remains for the .gbc file extension.

@dannye dannye requested a review from Rangi42 January 30, 2025 18:34
@Vortyne
Copy link
Contributor

Vortyne commented Jan 30, 2025

Since GBC is used by people in the average discussion of GBC, could we use that? I feel it is easier to read/understand. I know in hardware terms such as the labels on the back of the gameboy it will say CGB-001 and such, but people generally call it a GBC when abbreviated. Shouldn't we stick to what is the most commonly used abbreviated name for the system?

ram/wram.asm Show resolved Hide resolved
Copy link
Member

@Rangi42 Rangi42 left a comment

Choose a reason for hiding this comment

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

Thanks for this! It gets closer to pokecrystal, which already uses hCGB and hSGB names.

@Rangi42 Rangi42 merged commit 79518a6 into pret:master Jan 30, 2025
1 check passed
github-actions bot pushed a commit that referenced this pull request Jan 30, 2025
@SatoMew SatoMew deleted the cgbc branch January 30, 2025 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants