[lkml]   [2004]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] enums to clear suspend-state confusion

> Can you provide an example where the enum patch
> causes gcc to generate a warning for incorrect code?
> When I drop the wrong enum into a function,
> gcc seems to eat it just as happily as when
> we used u32's. Maybe I'm missing something.

It will not provide a warning, not for now. Idea was that eventually
sparse could warn or so.

Even with that, it makes it pretty clear for user what is going on,
and hopefully people will actually think before assigning variables
from different enum types.
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:05    [W:0.043 / U:0.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site