From: "D. Wokan" <wokan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PHP 5 unstable ?
Date: Sat, 23 Apr 2005 01:59:52 -0700 [thread overview]
Message-ID: <426A0E88.3020202@cox.net> (raw)
In-Reply-To: <20050422134525.25bee3f6@snowdrop>
Ciaran McCreesh wrote:
>On Fri, 22 Apr 2005 14:34:36 +0200 Francesco Riosa
><francesco@pnpitalia.it> wrote:
>| > Quite a lot has changed between PHP 4.3.x and 5.0.x. Apparently,
>| > things like classes are totally different. The classes in PHP 5
>| > more closely resemble Java than the ones in PHP 4.
>|
>| huh ? Horde for example works well with php5, and it's megs of object
>| code.
>|
>| there are problem with apache 2 and the usage of threads. Using it
>| with prefork apache MPM gived me NO problem (at least in the last 18
>| month).
>
>"Works for me" is also not always an indication of whether something is
>stable. "Works for lots of people" is better, but best is "doesn't not
>work for anyone".
>
>
>
Well then as one of hopefully lots of people, let me chime in with a
"PHP5 is working for me as well." How is it developers determine if
something's stable? A lack of bug reports from those of us who added
entries in our /etc/portage/ files? Where do we report a lack of bugs
to get these things pushed into the mainstream on Gentoo?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-23 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 11:57 [gentoo-dev] PHP unstable ? Omer Cohen
2005-04-22 12:12 ` [gentoo-dev] PHP 5 " Omer Cohen
2005-04-22 12:18 ` Stuart Longland
2005-04-22 12:34 ` Francesco Riosa
2005-04-22 12:45 ` Ciaran McCreesh
2005-04-23 8:59 ` D. Wokan [this message]
2005-04-23 9:07 ` Henrik Brix Andersen
2005-04-23 15:27 ` Collins Richey
2005-04-24 4:16 ` D. Wokan
2005-04-22 12:28 ` [gentoo-dev] PHP " Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=426A0E88.3020202@cox.net \
--to=wokan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox