Article View: comp.std.c++
Article #2459Re: Continue: static func() const; legal?
From: Dick Menninger
Date: Tue, 07 Nov 1995 20:35
Date: Tue, 07 Nov 1995 20:35
31 lines
1651 bytes
1651 bytes
I tried to participate in this general thread earlier but my news server had severe case of out of date newsgroup tables and mailed it (and other replies) to oblivion. So this is slightly out of context. When a normal (i.e., non-static) member function is given a const qualifier, it specifies that the function does not modifies normal members of the object instance. But such a member function can diddle with static members of the class without degrading its const status (at least that is what I remember). So, if you want a means to say NO SIDE-EFFECTS WHATSOEVER, it should be done in a way that can say that for normal member functions, as well. The debate should be about whether that is a good thing to be able to say about functions. If it is, then you want to be able to say it is ALL contexts and that changes how you wind up saying it. Good Day Dick Dick.Menninger@DaytonOH.ATTGIS.COM --- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu. Contact address: std-c++-request@ncar.ucar.edu. The moderation policy is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
Technical Details
Message-ID:
<DHouyI.LH9@falcon.daytonoh.attgis.com>Path:
arc1-ca.pugleaf.net!128.32.155.1!mattReferences:
<47dc02$kbh@bmtlh10.bnr.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!128.32.155.1!matt From: Dick Menninger <Dick.Menninger@DaytonOH.ATTGIS.COM> Newsgroups: comp.std.c++ Subject: Re: Continue: static func() const; legal? Date: 07 Nov 1995 20:35:34 GMT Organization: AT&T Global Information Solutions Approved: matt@physics2.Berkeley.EDU (Matt Austern) Message-ID: <DHouyI.LH9@falcon.daytonoh.attgis.com> References: <47dc02$kbh@bmtlh10.bnr.ca> Reply-To: mennid <Dick.Menninger@DaytonOH.ATTGIS.COM> NNTP-Posting-Host: physics2.berkeley.edu