delorie.com/archives/browse.cgi | search |
Date: | Thu, 6 Apr 2000 15:57:51 -0400 |
Message-Id: | <200004061957.PAA14708@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp AT delorie DOT com |
In-reply-to: | <38eda615.11483373@news.mysolution.com> (iam@not.you) |
Subject: | Re: classes |
References: | <eeLF4.13555$K9 DOT 107792 AT typhoon DOT nyroc DOT rr DOT com> <v7umesob3dvcog3a0nhe9e8h4trging7v5 AT 4ax DOT com> <38eda615 DOT 11483373 AT news DOT mysolution DOT com> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> Similar yes, but with 'added' features. AFAICR, structs, in the c++ > standard, do not support private, public, or protected features that > classes do. In other words: Wrong. "struct" and "class" are *identical* except for the default protection. There are no other differences between structs and classes. Even the parser doesn't treat them differently. I often ask about this in interviews to see if the candidate really understands structs and classes in C++. Most don't.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |