
|
[openbeosnetteam]
||
[Date Prev]
[07-2003 Date Index]
[Date Next]
||
[Thread Prev]
[07-2003 Thread Index]
[Thread Next]
[openbeosnetteam] Re: PPP: dial-on-demand
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Fri, 04 Jul 2003 17:29:27 +0200 CEST
"Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> > > The 10 MB bloat is only there because we use a static library.
> > > For R2 we could introduce a C++ stack without having the bloat.
> > > Currently, it is just a workaround. It will work, but not as
> > > efficient as it
> > > could do.
> > > After R1 it will work very good. Or do you think differently?
> > Yes, I do - I don't want to have that bloat in R1, even if it's
> > only
> > temporary, at least not for the whole stack.
> Then, the best solution is to implement shared kernel libs for R1. ;)
> If we had shared libs support in the kernel which language would you
> prefer
> for this task?
We don't have shared libs support in the kernel now (and for the
forseeable future); bear with it, it's not that bad.
> > If the ppp stuff is clearly separated from the rest, and the
> > libkernel_ppp.a is reasonably small, I wouldn't mind if you go C++
> > only
> > there - just take care of what you do.
> The templates that I use for the implementation could blow up the
> code to
> 200K, possibly. :(
> Without the templates and void* lists it could be reduced to around
> 80-100K
> (these are only expected values because currently nothing compiles).
Since it's a .a, only the stuff really needed will go into the final
object. Do you think you'll use the full 200 kB for every small module?
And how many modules will there be?
> How can you produce 50K of code in two weeks? I needed more than two
> months
> to get that far! :)
> How many hours do you work on the project per week (this is a
> question to
> all of you)?
The best way to spit out much code in a short time is to have designed
it before you actually do anything coding :-)
I don't know how many hours I spend on the project per week - I would
say anything between 2 and 20 hours could be realistic, sometimes even
more. BTW I will be on vacation shortly :)
> > > FSM_info structure even if you should not do that.
> > #define private public
> > ;-)
> I will put it into cpp.h. :)
Yeah, sounds good ;-))
Adios...
Axel.
|

|