Re: [Oslib-devel] Outsourcing the extender?

[Luca A. <luc...@em...>]

Hi Peter,

[...]
> Now my reccomendations for OSLib modularization would go into a rather
> different direction:
> - Move all from ll, libcons and libm to one of the three lib levels.
I think this will make things more complex... Someone may want to use ll
without libm or libcons, for example. I know for sure that there are
projects using ll but using a different libcons.

> - Put all xlib functionality in x0.o.
x0.o contains the startup code, whereas xlib contains library code. They
quite different things.

> - Either a) give a i386 subdir to all libs or b) use no i386 subdir at all.
> (a) would mean a widely used mechanism, good for portability.
> (b) would mean: "OSLib can never be ported because the booting mechanisms
> are too different on other architectures. So let's write pure i386 code!"
> Both soultions seem good to me, but not an inconsitent i386 port as it seems
> now to me.
I agree with this idea in principle, but I do not have time for
restructuring the directory structure right now... I leave this as an
"open task" for the future. Maybe someone can contribute some ppc code,
and we will have to rearrange everything for incorporating it ;-) Just
dreaming...

				Luca