In first place I have to thank to Alan Sloane and Douglas C. Schmidt for
their help. I want to repost an extract of the information I got from them.

Alan Sloane sent me the following list of the C++ Standard Library Revisions,
updated to February 23, 1994.

-- Cut here -------------------------------------------------------------------

C++ Standard Library Revisions, February 23, 1994.
==================================================

1.1 Bitset
----------
. Description This library provides a template class for defining bit-set's.

  The interface to the library has been undergoing considerable
  change (at every meeting of the committee).
  Giving further details in this document was not considered
                useful.

. Adopted March, 1993

. References ANSI papers 93-0012R2 and 93-0045.

1.2 String and wstring
----------------------
. Description This library provides facilities modeled closely on those of
  the ISO C standard for handling strings and wide-strings,
                i.e. zero-terminated sequences of char or whar_t.

  The interface to the library has been undergoing considerable
  change (at every meeting of the committee).

. Adopted March & July

. References ANSI papers 93-0013R1, 93-0064, 93-0122, 93-0150.

1.3 DynArray
------------
. Description This library provides a class which implements a dynamically
  resizable array type.

  The interface to the library has been undergoing considerable
  change (at every meeting of the committee).
  Giving further details in this document was not considered
                useful.

. Adopted July, 1993

. References ANSI papers 93-0060R, and 93-0122.

1.4 Complex
-----------
. Description This library provides three classes which implement complex
  numbers with float, double, and long double real and imaginary
  parts.

  This library was adopted only at the last committee meeting,
  and had not been previously reviewed. Past experience suggests
  that it will undergo significant revisions before final
  standardization. Consequently giving further details in this
  document was not considered useful.

. Adopted November 1993

. References ANSI paper 93-0165.

1.5 Iostream revisions
----------------------
. Description Currently there are two proposals, by Jerry Schwarz and P.J.
  Plauger, to add wide character support to iostreams. At the
  November 1993 meeting a decision was taken to resolve the
  differences, and incorporate the resolution into the February
  1994 draft of the Working Paper.

  At the current time it is completely unclear what decisions
  the committee may make - considerable controversy and
  dissension exists.

  In addition the standard library iostream classes are required
  to be declared within a Namespace.

. Adopted November, 1993

. References This is scheduled to be included in the February 1994 Draft
  Working Paper, as Chapter 17 (not yet available).

  ANSI paper 93-0136 describes the use of namespaces.


1.6 Other standard library revisions
------------------------------------
. Description Several other minor revisions have been made to the standard
  library. These include adding an exception hierarchy, revised
  semantics of the user-level exception functions (terminate,
  unexpected etc.), and revisions to the free-store functions.

  The exception hierarchy changes the structure of the base
  classes of the standard "out-of-memory" exception, xalloc:

   class xmsg { ... };
   class xruntime : public xmsg { ... };
   class xalloc : public xruntime { ... };

. Adopted November 1992- November 1993, ongoing

. References ANSI papers 93-0164 (Exception hierarchy), February 1994
  revision of the Draft Working Paper, Chapter 17 (not yet
  available).
-- Cut here -------------------------------------------------------------------

I asked him if AT&T's task library is out of the standard, and he answered me:

>The task library has never been proposed (to my recollection in 4 years
>or so of attending) for adoption in the standard. So that's why it's not
>on the list. Complex, by the way, only got proposed and adopted at the last
>meeting, in November.
>
>A C++ interface to threads is I think a different matter than tasks - and
>as you say a useful one. But I doubt that anyone nowadays would want to
>have the cfron task library interface for that purpose !
>
>I don't think the C++ language standard is the place for such a beast, though.
>More appropriate would be for example a C++ language binding for POSIX threads
>- which would be part of the POSIX standard.

I think he is right.

by the other hand, if you want to know about the set of criteria that drives
the library Working Group, the virtual interview to Mike Vilot made by
Doug Schmidt in October '93 C++ Report is a highly recommendable article.

I hope this helps someone. bye.
--
-------------------------------------------------------------------------------
 ||||  ##     ####                    |         Pascual Juan         |    _V_
 ||||  ## _|_ ## ##   Telefonica I+D  | E-mail: pascual@gonzo.tid.es |  _(,|,)`
 @@@@  ##  |  ## ##  (Telefonica R&D) |    Phone: +34-1-314-47-04    | | ___ ')
 @@@@  ##     ####                    |    fax:   +34-1-337-42-22    | |_|`__/
-------------------------------------------------------------------------------