From: ms <m.siedlarek@nctz.net>
Cc: mailbox@dmitry-kazakov.de
Subject: Re: Interface to aggregated type
Date: Mon, 6 Aug 2012 13:28:55 -0700 (PDT)
Date: 2012-08-06T13:28:55-07:00 [thread overview]
Message-ID: <e239a0b9-8f5c-41db-b0ea-a312a3fc4fac@googlegroups.com> (raw)
In-Reply-To: <pqmx0s03p9lk$.fbclercmsr1i.dlg@40tude.net>
On Monday, August 6, 2012 9:43:22 PM UTC+2, Dmitry A. Kazakov wrote:
> On Mon, 6 Aug 2012 11:42:03 -0700 (PDT), ms wrote:
>
>
>
> > Clearly `Request` aggregates `Header_Container`, as HTTP requests
>
> > generally contain some set of headers.
>
> >
>
> > My dilemma is - `Headers` package already provides some sort of
>
> > `Header_Container` manipulation interface - procedures for inserting and
>
> > deleting headers and functions to return them, but I want allow these
>
> > operations also on container aggregated inside `Request` type (which is
>
> > probably a private record).
>
>
>
> If Request implements the interface of Header_Container and also aggregates
>
> it, why don't you derive one from another?
>
>
>
> --
>
> Regards,
>
> Dmitry A. Kazakov
>
> http://www.dmitry-kazakov.de
This is one of these "how did I missed that" ideas. Thanks!
next prev parent reply other threads:[~2012-08-06 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 18:42 Interface to aggregated type ms
2012-08-06 19:43 ` Dmitry A. Kazakov
2012-08-06 20:28 ` ms [this message]
2012-08-06 19:56 ` Marius Amado-Alves
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox