John Keiser wrote:
> > From: Christophe Lizzi [mailto:[EMAIL PROTECTED]]
> >
> > > > Hmm... Nearly nothing really portable or generalizable here. Mainly
> > > > addition of some proprietary threading code,
> > >
> > > Was it enough to change files in arch/?
> > >
> >
> > Most of the Chorus specific code takes place in arch/ but some
> > unixims have to be disabled/rewritten elsewhere.
> >
>
> It seems to me that the work you did is useful even just for that reason.
> The more places you find that need to be changed when Japhar is ported, the
> easier it gets to port in the future. At the very least, patches would be
> useful in order to find out what functions had to be modified.
>
> A porting guide might be a good idea, too ...
yes. also, it would be incredibly useful to migrate unixisms and other
platform specific code into the arch directory (as much as makes sense.) that
way only one directory needs to be dealt with to port japhar.
xtoph
