Enum name convention consistency
Sam Hu
samhudotsamhu at gmail.com
Tue Aug 18 20:12:19 PDT 2009
>From std.range:
enum StoppingPolicy
{
/// Stop when the shortest range is exhausted
shortest,
/// Stop when the longest range is exhausted
longest,
/// Require that all ranges are equal
requireSameLength,
}
>From std.thread:( phobos webpage)
enum State;
A fiber may occupy one of three states: HOLD, EXEC, and TERM. The HOLD state applies to any fiber that is suspended and ready to be called. The EXEC state will be set for any fiber that is currently executing. And the TERM state is set when a fiber terminates. Once a fiber terminates, it must be reset before it may be called again.
HOLD
EXEC
TERM
>From std.stream:
enum FileMode {
In = 1,
Out = 2,
OutNew = 6, // includes FileMode.Out
Append = 10 // includes FileMode.Out
}
Would not this be better if we keep the name convention consistent.
Regards,
Sam
More information about the Digitalmars-d-learn
mailing list