linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rafael Costa dos Santos <rafael@thinkfreak.com.br>
To: Voicu Liviu <pacman@mscc.huji.ac.il>,
	Sandro Dangui <sdangui@nortelnetworks.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: C++ class inheritance
Date: Fri, 3 Oct 2003 12:57:13 +0000	[thread overview]
Message-ID: <200310031257.14155.rafael@thinkfreak.com.br> (raw)
In-Reply-To: <3F7BD40E.3050100@mscc.huji.ac.il>

Ok, but as I am C ANSI programmer it is a bit dificult to underestand.

Are you saying that "RasPDU" is a general class that depends on the template 
(in this case "H225_RegistrationRequest") that is informed ?

Is it similar to create a specific class like:

class RasPDU : public H225_RegistrationRequest
{
} ;

and inherit from it ?

class RegistrationRequestPDU : public RasPDU
{
} ;

On Thursday 02 October 2003 07:30, Voicu Liviu wrote:
> Rafael Costa dos Santos wrote:
> >Can anyone explain me what does < > means ?
> >Example:
> >
> >class RegistrationRequestPDU : public RasPDU<H225_RegistrationRequest>
> >{
> >} ;
> >
> >Is "RegistrationRequestPDU" inheriting from RasPDU,
> > H225_RegistrationRequest or both ?
>
> RegistrationRequestPDU  inherits from RasPDU using template
> H225_RegistrationRequest ?

-- 
Rafael Costa dos Santos
rafael@thinkfreak.com.br

  reply	other threads:[~2003-10-03 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02  4:00 C++ class inheritance Rafael Costa dos Santos
2003-10-02  7:30 ` Voicu Liviu
2003-10-03 12:57   ` Rafael Costa dos Santos [this message]
2003-10-03 16:19     ` Darío Mariani
  -- strict thread matches above, loose matches on Subject: below --
2003-10-02 12:27 Sandro Dangui
2003-10-03 21:18 IVAN DE JESUS DERAS TABORA

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=200310031257.14155.rafael@thinkfreak.com.br \
    --to=rafael@thinkfreak.com.br \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=pacman@mscc.huji.ac.il \
    --cc=sdangui@nortelnetworks.com \
    /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).