This is an initial list of issues. We have "seeded" it with topics of current topics in the
evolution working group, reflector threads, and email messages received. We expect that the
list will grow significantly and that the presentation and organization of this list will
evolve to cope.

Some of the library components in this technical report may be considered for standardization
in a future version of C++, but they are not currently part of any C++ standard. Some of the
components in this technical report may never be standardized, and others may be standardized
in a substantially changed form.

We propose a new constant called nullptr of the distinct type decltype(nullptr). nullptr can be
assigned to any pointer type (incl. pointer to member and function pointer types)but not to
integral types. We further propose that the standard library macro NULL be defined to be nullptr.
The result will be more readable code, better error detection, and better overload resolution.

This proposal resents two suggestions:
(1) to allow initializer lists to be used in expressions
(2) to allow initializer lists to be used for containers

We suggest to generalize the notion of constant expressions to include
calls to constant-valued functions.

This submission endeavors to improve enumerations by eliminating certain lingering deficiencies.

This note proposes a notion of user-defined literals based on literal constructors
without requiring new syntax.

This paper discusses the issues presented in adding support for dynamic libraries to standard C++
and it makes specific recommendations for changes to the C++ standard for that support. These
recommendations are at present incomplete, and the parts that are presented will undoubtedly be
changed extensively as a result of future discussions. They are intended to provide a starting
point and a framework for changes needed to support dynamic libraries in standard C++.