Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!odi!benson
From: benson@odi.com (Benson I. Margulies)
Newsgroups: comp.lang.c++
Subject: 2.0 vs. 2.1 ifdef?
Message-ID: <1990Nov29.123514.2075@odi.com>
Date: 29 Nov 90 12:35:14 GMT
Organization: Object Design, Inc.
Lines: 21

2.1 makes significant changes in name scoping rules. In particular,

class x {
  enum y {a, b, c} Y;
};

results in x::y as a typename in 2.1 and y as a typename in 2.0.

We need to have some code that is equally compilable by 2.0 and 2.1, 
and I bet we're not alone. 

It would be handy if the community would agree on a #define that
distinguishes 2.1 from 2.0. 

How about

__cplusplus21

indicating a 2.1 compatible compiler?
-- 
Benson I. Margulies