You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Greg Stein <gs...@lyra.org> on 1999/09/10 23:51:50 UTC

Re: cvs commit: apache-2.0/src/lib/apr/time/beos access.c

rbb@hyperreal.org wrote:
> 
> rbb         99/09/10 07:00:49
> 
>   Modified:    src/lib/apr Makefile.in
>                src/lib/apr/file_io/beos fileacc.c fileio.h open.c
>                         readwrite.c
>                src/lib/apr/lib apr_getpass.c
>                src/lib/apr/test htdigest.c
>                src/lib/apr/threadproc/beos Makefile.in proc.c threadproc.h
>                src/lib/apr/time/beos access.c
>   Added:       src/lib/apr/threadproc/beos apr_proc_stub.c procsup.c
>   Log:
>   More changes to bring BeOS up to the UNIX APR level.  Also a few changes to
>   some test programs to make them more portable.  Lastly, a work around for a
>   BeOS bug that makes fork potentially dangerous.
>   Submitted by:  David Reid

I think this patch exemplifies some of the worry that myself (and a few
others? Jim?) shared at the start of this project. Namely, that APR is
sliced rigidly along OS lines, rather than "standard + platform-specific
tweaks" lines. As a result, this creates a multiple-path maintenance
nightmare.

What happens if somebody tweaks the interpretation of a parameter in
file_io/unix? They now have to replicate that behavior through a bunch
of other directories, even though each of the functions are actually
implemented identically!

I believe your position at the time was "it is easiest to build this in
separate directories; I'll do it that way for now; later, I'll merge the
common stuff somehow."

Do you have a plan to merge some of this stuff so that it isn't so
strictly separated by platform?

thx,
-g

--
Greg Stein, http://www.lyra.org/

Re: cvs commit: apache-2.0/src/lib/apr/time/beos access.c

Posted by Ryan Bloom <rb...@raleigh.ibm.com>.
I spoke to David Reid, the guy who is doing the BeOS work, and his opinion
was that at this point there aren't enough similarities between unix and
Beos to make this worthwhile.  He is waiting for a couple of fixed from
the BeOS guys before we merge them.  I do not think Windows will ever be
merged into UNIX, because the differences are too great.  Basically, I am
taking this on a case by case basis.  If the maintenance is easier with
them split, then I am keeping them split.  If it is easier with them
merged, then I am merging them.  I would like to see Windows and OS/2
merge, because I believe they are very similar.  I believe that bs2000,
AS/400, and OS/390 will all be using the unix dir, and I think BeOS will
be merged into Unix as soon as the OS becomes a bit more stable.

Hope that answers your question.

Ryan

On Fri, 10 Sep 1999, Greg Stein wrote:

> rbb@hyperreal.org wrote:
> > 
> > rbb         99/09/10 07:00:49
> > 
> >   Modified:    src/lib/apr Makefile.in
> >                src/lib/apr/file_io/beos fileacc.c fileio.h open.c
> >                         readwrite.c
> >                src/lib/apr/lib apr_getpass.c
> >                src/lib/apr/test htdigest.c
> >                src/lib/apr/threadproc/beos Makefile.in proc.c threadproc.h
> >                src/lib/apr/time/beos access.c
> >   Added:       src/lib/apr/threadproc/beos apr_proc_stub.c procsup.c
> >   Log:
> >   More changes to bring BeOS up to the UNIX APR level.  Also a few changes to
> >   some test programs to make them more portable.  Lastly, a work around for a
> >   BeOS bug that makes fork potentially dangerous.
> >   Submitted by:  David Reid
> 
> I think this patch exemplifies some of the worry that myself (and a few
> others? Jim?) shared at the start of this project. Namely, that APR is
> sliced rigidly along OS lines, rather than "standard + platform-specific
> tweaks" lines. As a result, this creates a multiple-path maintenance
> nightmare.
> 
> What happens if somebody tweaks the interpretation of a parameter in
> file_io/unix? They now have to replicate that behavior through a bunch
> of other directories, even though each of the functions are actually
> implemented identically!
> 
> I believe your position at the time was "it is easiest to build this in
> separate directories; I'll do it that way for now; later, I'll merge the
> common stuff somehow."
> 
> Do you have a plan to merge some of this stuff so that it isn't so
> strictly separated by platform?
> 
> thx,
> -g
> 
> --
> Greg Stein, http://www.lyra.org/
> 

_______________________________________________________________________
Ryan Bloom		rbb@raleigh.ibm.com
4205 S Miami Blvd	
RTP, NC 27709		It's a beautiful sight to see good dancers 
			doing simple steps.  It's a painful sight to
			see beginners doing complicated patterns.