Skip to content

Conversation

holub
Copy link
Contributor

@holub holub commented Jul 30, 2025

No description provided.

Comment on lines +107 to +108
return;
break;
Copy link
Member

Choose a reason for hiding this comment

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

Isn't return and break at same time going to throw a compiler error?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Neither clang nor gcc failed the compilation. I was thinking having break everywhere is more consistent.

case 0b1110: // CALL
m_ret_pc = m_pc + 1;
m_pc = data & 0xff;
break;
Copy link
Member

Choose a reason for hiding this comment

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

This break; lost a tab child

@@ -173,6 +177,7 @@ class tsconf_state : public spectrum_128_state
void draw_sprites(screen_device &screen, bitmap_rgb32 &bitmap, const rectangle &cliprect);
void tsconf_update_video_mode();
void copy_tiles_to_raw(const u8 *tiles_src, u8 *raw_target);
attotime cooper_until_pos_r(u16 pos);
Copy link
Member

Choose a reason for hiding this comment

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

This became Bob Cooper somehow 🎵

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.

2 participants