C++ MT discussion group
Boehm, Hans
hans.boehm at hp.com
Thu Mar 10 21:51:30 GMT 2005
Should we think about an open list, as well
as a more restricted list, with nearly all of the discussion
carried on the former?
That seemed to work reasonably well for JSR133. We do want
input from a large group of people, and don't want to
appear exclusive. On the other hand, we will need to make
decisions in order to arrive at a proposal. I'm concerned
that doing that with a large group, many of whom may
have joined recently, will be difficult.
My impression if Michael Pryhodko, based on a couple
of recent usenet discussions, is that I'd like to see him
involved in discussions, but not necessarily in trying to
reach a consensus.
Hans
> -----Original Message-----
> From: Kevlin Henney [mailto:kevlin at curbralan.com]
> Sent: Thursday, March 10, 2005 12:23 AM
> To: Andrei Alexandrescu
> Cc: jimmaureenrogers at att.net; Doug Lea; Doug Lea; Boehm,
> Hans; Ben Hutchings; Bill Pugh; Douglas C. Schmidt; Maged
> Michael; asharji at plg.uwaterloo.ca; Richard Bilson
> Subject: Re: C++ MT discussion group
>
>
> In message <422FFC79.5050700 at metalanguage.com>, Andrei Alexandrescu
> <andrei at metalanguage.com> writes
> >I've just sent the message below to Michael Pryhodko, who
> asked to join
> >our group. He's participated in a number of discussions on MT on
> >comp.lang.c++.moderated, which I haven't had the time to
> follow. Please
> >let me know what you think about adding him to the list.
>
> I don't have any objections in principle to this. However, it
> might be
> worth actually treating this as a group rather than a cc'd
> list. Ben set
> up such a list, IIRC. Should we all move over to it?
>
> Kevlin
> --
> ____________________________________________________________
>
> Kevlin Henney phone: +44 117 942 2990
> mailto:kevlin at curbralan.com mobile: +44 7801 073 508
> http://www.curbralan.com fax: +44 870 052 2289
> Curbralan: Consultancy + Training + Development + Review
> ____________________________________________________________
>
More information about the cpp-threads
mailing list