linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric <eric@cisu.net>
To: jtwilliams@vt.edu
Cc: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re:  Pointers to classes
Date: Sun, 20 Jun 2004 08:30:08 -0500	[thread overview]
Message-ID: <200406200830.08098.eric@cisu.net> (raw)
In-Reply-To: <1087708691.11832.32.camel@localhost>

On Sunday 20 June 2004 12:18 am, John T. Williams wrote:
> Sorry wrong terminology. its not prototyping, but I can't remember what
> you call it when you give a partial class, i.e.
> class SomeClass;
>
> rather then full class
>
> class SomeClass {
> private:
> ...
> public:
> ...
> };
>
> ?Maybe forward declaration ?

 The abstract class worked like a charm! I think I had some weird include 
problems where they werent going in the order I needed them to and I couldn't 
trace it down. Firthermore I didnt want to redefine the class inside 
connection.h...that would just be silly. But an abstract class worked 
beautifully.

> > you might also want to add the lines
> >
> > #ifndef CONNECT_H
> > #define CONNECT_H
> >
> > to the very top of connect.h
> >
> > and
> >
> > #endif
> >
> > to the very bottom of connect.h

Thats a great tip. Ill implement that from now on.

  parent reply	other threads:[~2004-06-20 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20  4:46 Pointers to classes Eric
2004-06-20  5:06 ` John T. Williams
2004-06-20  5:18   ` John T. Williams
2004-06-20 12:49     ` LDB
2004-06-20 13:30     ` Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21 14:55 Huber, George K RDECOM CERDEC STCD SRI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406200830.08098.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=jtwilliams@vt.edu \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).