A C++ Whishlist

From: Hattuari (susudata_at_setidava.kushan.aa)
Date: 03/09/04 

Date: Tue, 09 Mar 2004 16:15:15 -0500

Somewhere there was a question about what we would like to see in the next
version of C++. I can't find it, and it was basically a fork from the
previous thread, so I'll start anew.

I believe some things could go a long way to improve the language's
usability that do not involve modifying the language itself. I would like
to see an open standard library for supporting code completion, syntax
highlighting, code formatting, and edit-time error checking.

A really standard string class. I still count as a newbie to C++, so
perhaps I just need to adjust. I know Java strings aggravated me at first
because I felt like I had to write an entire program to do things I could
do in C in a couple lines. Now I have come to really like Java Strings.
Mostly because in Java, a String is a String is a String. Not so in C++.

Deprecate, or seriously restrict struct so that it can only have public
members. It just adds complexity without functionality to have struct
defined as a class in which members are default public.

I believe header files are nothing but a nuisance. It is not clear to me
they add anything to the capability of the language, but they clearly add
confusion. If nothing else, provide a standard library component that will
facilitate the automatic synchronization of header files.

I suspect namespaces and what is now done with header files could be merged
in such a way to encourage better use of namespaces, and provide basically
the same support as header files currently provide.

Make exception handling manditory as it is in Java. If you throw it, you
*must* catch it, or declare it to be thrown in the function declaration.

Should I even suggest thinking about introspection and reflection? 

-- 
.

Relevant Pages

  • Re: Fetch function names & prototypes?
    ... > although in C++ the prototypes are found in the header files included ... > string into the object file symbol table, ... trick would not allow a perfect/accurate type checking. ... arguments have complex data types, ...
    (comp.compilers)
  • Re: Using multiple programming languages - C++ & C#
    ... In your project add the C# dll under the "references" option. ... using namespace CustomMadeDll; ... Converting System::String to normal string: ... Do not search for header files or lib files to include, ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Std Map .. Help
    ... This is a valid header file, but it doesn't declare the std::string class ... Use <string> instead ... You need to use the correct header files (no C++ header files have .h in ...
    (comp.lang.cpp)
  • Re: Nasty code...but please critique it anyway :-)
    ... > I, too, would like feedback on my code. ... > 1) my use header files ... string lcase{ ... a separate part handles the direct interaction with ...
    (comp.lang.cpp)
  • Re: Nasty code...but please critique it anyway :-)
    ... > I, too, would like feedback on my code. ... > 1) my use header files ... string lcase{ ... a separate part handles the direct interaction with ...
    (alt.comp.lang.learn.c-cpp)