This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Multiple PPP interfaces in single unit


On Wed, 2004-07-28 at 15:45, Nick Garnett wrote:
> Øyvind Harboe <oyvind.harboe@zylin.com> writes:
> 
> > 
> > Seperate C++ namespace for each PPPD?
> > 
> > - Write a pppd2.h file
> > 
> > ---
> > namespace PPPD2;
> > ---
> > 
> > 
> > - Compile PPPD twice, but second time add option:
> > 
> > g++ -include pppd2.h ...
> 
> I have considered several ways around the problem, but not even in my
> most fevered imaginings did I come up with that one :-)
>
> This would end up duplicating the code and the data. Not a good idea.

Currently we have no solution. Thats not good either :-)

If this solution requires no changes to the code, makes updates easy and
incurs no overhead for the common case(single PPPD)...

Slightly increased code size(only PPPD code is duplicated, not the rest
of eCos) and probably not very much more ram usage.

Perhaps you know something I don't, but it seems like a very economical
solution. 

Now, the next question is whether it will work out of the box...


> The least disruptive approach I came up with is to convert all of
> these global variable into arrays, rename them and then define a macro
> with the original name which picks out the correct instance. However,
> there are still issues about where the instance index comes from.
-- 
Øyvind Harboe
http://www.zylin.com



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]