Article View: comp.sys.amiga.tech
Article #13219Blinking static members
From: Ranjan Bagchi
Date: Fri, 29 Dec 1989 00:36
Date: Fri, 29 Dec 1989 00:36
19 lines
1246 bytes
1246 bytes
A C++ project that I'm working on involves a class with a static member. Perfectly acceptable C++ code...two different .cp files #include the .h which defines this class. Everything compiles fine. What bothers me is when I blink everything together into executable code, blink complains about multiply defined code. I have isolated it to the presence of the static class members. When I transfered the code to *NIX and g++'ed everything together, there was not a burble. What I'm asking is if there's any way to tell blink to "chill", and that the static members are supposed to be there. The object files do link, incidently...eveyrthing runs as expected. Warnings of any kind bug me, though. -rj bagchi@sparky.eecs.umich.edu
Technical Details
Message-ID:
<1165@zip.eecs.umich.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!shadooby!umich!dip.eecs.umich.edu!bagchiShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!shadooby!umich!dip.eecs.umich.edu!bagchi From: bagchi@dip.eecs.umich.edu (Ranjan Bagchi) Newsgroups: comp.sys.amiga.tech Subject: Blinking static members Keywords: C++ Message-ID: <1165@zip.eecs.umich.edu> Date: 29 Dec 89 00:36:16 GMT Sender: news@zippy.eecs.umich.edu Reply-To: bagchi@dip.eecs.umich.edu (Ranjan Bagchi) Organization: University of Michigan EECS Dept., Ann Arbor, MI Lines: 19