Deprecated, reprecated, and prepcreatedcated

Sounds good to me.  Let’s see:

Features that are in the standard, and have never been deprecated, are precated.

Features that have been deprecated, but aren’t any more, are reprecated.

Features that aren’t in the standard, but are (more or less) guaranteed to be in a future standard (the library TR, for example), are preprecated.

I like this group.  Not only can we invent new features for C++, we can invent them for English as well:-).

I’d suggest adding a couple more:

Features that nobody wants in the standard are antiprecated. Example: the comefrom statement.

Features that are of limited usefulness (in spite of a very long implementation time) but did make it in the standard shall be called placated. Example: <censored>.

The upcoming proposal to add multithreading to the standard is prepcreatedcated (the result of two threads writing “precated” concurrently).

Andrei

[Andrei Alexandrescu in comp.lang.c++.moderated]