🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.c++
Article #2478

Re: ??? static locals in inline functions ???

#2478
From: Kaelin Colclasure
Date: Thu, 09 Nov 1995 05:46
48 lines
2967 bytes
In article <9531214.21952@mulga.cs.mu.OZ.AU> fjh@munta.cs.mu.OZ.AU (Fergus Hend
erson) writes:

[Good explanation of distinction between access/linkage/scope
elided...]

    >> The concept of an "extern" member function is meaningless--

    Fergus>    The concept of a member function with "extern" scope
    Fergus> would be meaningless, but the concept of a member function
    Fergus> having external linkage is quite meaningful.  Indeed, all
    Fergus> member functions have external linkage, except for member
    Fergus> functions of local classes defined withing other
    Fergus> functions, which have no linkage.

This is exactly what I was trying to say, albiet using antiquated
terminology. :-)

    >> Your example of const variables defaulting to "file scope" is
    >> something of a surprise to me as well.

    Fergus>    s/file scope/internal linkage/

I was exposed to K&R C at a tender age-- I blame society.

    >> I recognize the obvious benefit from a code generation
    >> perspective, but if this is true do we ever expect anyone to
    >> learn this language (C++) without first assimilating a massive
    >> body of historical and practical knowledge from which to draw
    >> insight as to why these inconsistancies exist?

    Fergus>    I can't speak for anyone else, but I don't.  I expect
    Fergus> most people will learn some small subset of the language,
    Fergus> and then muddle on.

I had intended that last as a purely rhetorical question, but at the
rate things are going I agree.  I suppose we should all take some
comfort from the fact that anyone who manages to understand all this
has excellent job security.
-- 
// Kaelin Colclasure -------------------------------------------------------
// EMail: kaelin@bridge.com           Mail: Bridge Information Systems, Inc.
// Voice: (314)567-8463                     717 Office Parkway
//   Fax: (314)432-5391                     St. Louis, MO 63141
---
[ 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: <KAELIN.95Nov8114230@binki.bridge.com>
Path: arc1-ca.pugleaf.net!in1.uu.net!bounce-back
References: <KAELIN.95Nov4090501@binki.bridge.com> <DHou9J.L8t@falcon.daytonoh.attgis.com> <KAELIN.95Nov7175431@binki.bridge.com> <9531214.21952@mulga.cs.mu.OZ.AU>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!in1.uu.net!bounce-back
Date: 09 Nov 95 05:46:23 GMT
Approved: fjh@cs.mu.oz.au
From: kaelin@bridge.com (Kaelin Colclasure)
Newsgroups: comp.std.c++
Subject: Re: ??? static locals in inline functions ???
X-Original-Date: 08 Nov 1995 17:42:30 GMT
Organization: Bridge Information Systems, Inc.
Message-ID: <KAELIN.95Nov8114230@binki.bridge.com>
References: <KAELIN.95Nov4090501@binki.bridge.com>
 <DHou9J.L8t@falcon.daytonoh.attgis.com>
 <KAELIN.95Nov7175431@binki.bridge.com>
 <9531214.21952@mulga.cs.mu.OZ.AU>
In-Reply-To: fjh@munta.cs.mu.OZ.AU's message of 08 Nov 1995 10:10:27 GMT
X-Auth: PGPMoose V1.1 PGP comp.std.c++
 iQBFAgUBMKGVweEDnX0m9pzZAQEBtgGAiZOaH04zApsK5ejeg459oH/32o1Z2Z47
 YW0QXLcHkONaZOArC7aGA0o8og+PRAEu
 =5m9E