Re: message_box() category yay or nay?
- Posted by CChris <christian.cuvier at a?r?culture.gouv.fr> May 07, 2008
- 559 views
Shawn Pringle wrote: > > CChris wrote: > > > > I'd suggest spinning a new Interactive I/O category from the current File > > and > > device I/O off. There would go: > > pronpt_number > > mrompt_string > > message_box > > get_key > > wait_key > > ? (since it prints to stdout only) > > and perhaps whatever should be under Mouse support currently, in which case > > the latter category would disappear. > > > > I say "should" because the link from reference index page to Mouse support > > goes > > to the OS category listing. > > > > Also, I'd spin all crash_* entries from Machine level interface, an put that > > under either OS or a new Runtime Control category. > > > > CChris > > Putting these routines in an Interactive category allows us to discover these > functions. I didn't know about those other routines. That's why I never > used them. > > > Shawn Pringle I forgot to mention that fre_console() is misplaced under C Interface. I'd put it in Interactive I/O as well, although OS is a reasonable choice too. CChris