I feel like the ball boy at Wimbledon here, interfering in a rare old ding-dong of the match of the week
de Guzman v. Slettebų who seem to be about 40 all so far? As someone who grew up happily on pointerless language, I don't automatically think resource when I read pointer or ptr. How about managed_resource<widget> and/or perhaps (and probably not) managed_resources<widgets> if it is a list? A bit long, but MUCH clearer? Paul Paul A Bristow, Prizet Farmhouse, Kendal, Cumbria, LA8 8AB UK +44 1539 561830 Mobile +44 7714 33 02 04 Mobile mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] > > "resource_manager" starts to look attractive, again. ;) > > Perhaps. But there's a *better* and *shorter* alternative that very well fits > the description. We can say: linear_list_of_items_manager<int>, YUCK! > Instead, we say list<int>. The management *is* implicit! > > Also, in general, I would say that any name suffixed by "_manager" are best > used for classes that manage *many* things simultaneously, NOT JUST ONE. > Take a window_manager for example. It is something that manages the operations > of many windows. In the Macintosh, for example, the resource manager manages > "all* the resources in an application. > > -- > Joel de Guzman > joel at boost-consulting.com > http://www.boost-consulting.com > http://spirit.sf.net > > > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
