On Tue, Feb 05, 2002 at 09:42:12AM -0500, [EMAIL PROTECTED] wrote:
> > [EMAIL PROTECTED] wrote:
> >> Removing backward compatibility for aesthetic reasons is bogus. To be
> >> perfectly honest, I think the whole PHP extension API is truly ugly.
> >> The removal of a few #ifdefs will not a Mona Lisa make.
> >
> > to me "readability" is a maintainance issue, not an aestheic one ...
>
> Perhaps for you it is, but not everyone agrees with you. Open source is
> about freedom, is it not?
>
> >
> > if you don't care about others to understand your code, or even don't
> > want anyone to touch it anyway (as you already have made clear),
>
> I have made no such declaration. I just do not think well placed #ifdefs
> affect readability or maintainability. That is your opinion, not mine. I
> welcome anyone to add features to the msession code as they see fit. All I
> ask is that they do not remove backward compatibility. This is not an
> earth shattering request.
>
> I am really tired of this argument. Why do you care? Why does anyone care?
> The code is fairly readable, it doesn't do anything hard to understand. It
> is a simple thunk/trasport layer for another library all together. If
> anyone has trouble reading or understanding it, I would suggest that they
> need to take a basic C class.
>
> More over, I think msession, while still a bit experimental, is a
> worthwhile addition to PHP. I already have a few people using it and it
> has helped them deploy their web farm. People are using it, and in doing
> so people are using PHP for big things. As I understand it, this is what
> we all want, right?
>
> I think very highly of PHP. It is a great project. I submited my extension
> to add value to the project. I think it can add value and help moderately
> large installations.
>
> All I am asking is that, as one developer, that backward compatibiliy
> remains so I do not have to maintain two branches and duplicate work. My
> time is valuable, why should I waste it? This is not a lot to ask and I
> simply do not understand what the problem is. In any professional
> environment, this would be a no-brainer. You do not remove backward
> compatibility if you do not need to do so.
the problem as i see it is that everything in the php4/ CVS
is worked on by several ppls. we invent a new API and
somebody goes and implements that in some modules (and mybe
not in some other).
the new parameter-parsing API was introduced by andrei some
month ago and we decided to switch to this api. even thogh i
haven't been very active lately i did a big chink of work
porting modules from php3 to php4 and -no- i did not ask the
official maintainer if they want to port it. there was an
itch and i scrachted it. having a new/better API certainly is
an itch and having both the old and the new one in one file
is something we've never done in the past.
i agree with hartmut that we don't care for backward
compatiblity in modules that are in the php4/ cvs. so if you
need to have support for anything but php4-HEAD in your
module it probably doesn't belong to php4-HEAD.
PECL on the other hand is a completely different story, and
if i was you i would "move places".
re,
tc
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
