> From: Beman Dawes <[EMAIL PROTECTED]> > At 03:03 PM 1/8/2003, William E. Kempf wrote: > > >The sched_fifo, sched_rr, sched_other, scope_process, and scope_system > >values are implementation defined, and on POSIX correspond to SCHED_FIFO, > > >SCHED_RR, SCHED_OTHER, PTHREAD_SCOPE_PROCESS and PTHREAD_SCOPE_SYSTEM > >respectively. > > A similar situation came up in the Filesystem Library exception classes > where we needed enums for some error codes. > > In the end, we decided that meaningful names were more important than > compatibility with POSIX. > > Most of the ones you list above seem OK as-is. But sched_rr? What does that > mean? How about renaming it "sched_round_robin"? > > If you put "round robin scheduling" into Google, you get links to pages > clearly explaining the concept. > > If you put "sched_rr" into Google, you get links to pages which are much > less enlightening.
I'm not married to any of the names. I can easily rename it to sched_round_robin. I'd even be willing to spell "sched" out in all of these names, if that's what's preferred. William E. Kempf [EMAIL PROTECTED] _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
