cacalabs/libcaca

Intentional fallthroughs?

r-barnes opened this issue · 0 comments

r-barnes commented

I'm just wondering if these fallthroughs are intentional (can we mark them with __attribute__((fallthrough))) or bugs (can we fix them with break)?

libcaca/caca/caca0.c

Line 168 in f42aa68

case 0x10: feature = 0x12; /* CACA_BACKGROUND_SOLID */

libcaca/caca/caca0.c

Line 175 in f42aa68

case 0x20: feature = 0x22; /* CACA_ANTIALIASING_PREFILTER */

libcaca/caca/caca0.c

Line 182 in f42aa68

case 0x30: feature = 0x33; /* CACA_DITHERING_ORDERED4 */