It seems like the core team is using the filter extension that is part
of PHP 5.2 and higher(http://www.php.net/manual/en/
filter.installation.php). You can see it in one of the posts Fabian
Lange posted on the blog (http://www.symfony-project.org/blog/
2008/07/01/symfony-1-2-roadmap). Also there are some changesets that
refer to this topic. you can easily find them via trac (http://
trac.symfony-project.org/search?q=PHP+5.2&noquickjump=1&changeset=on).
So i come to the conclusion that the changes the core team have made
are so big that you will cause serious problems if you use symfony 1.2
with a php version prior to 5.2.

- Dennis

On 11 Nov., 00:32, "David Brewer" <[EMAIL PROTECTED]> wrote:
> I think the reason for the dependency is the desire to fully support
> Doctrine in the 1.2 release.  I can personally vouch that, as Bernhard
> wrote, prior to 5.2.4 (or possibly 5.2.3) Doctrine was pretty much
> unusable due to PHP constantly segfaulting.  This was not an issue
> that could easily be worked around.
>
> It may be that other parts of symfony 1.2 or Propel 1.3 run into
> similar issues with PHP < 5.2.3, but I can't vouch for that.
>
> David
>
> On Mon, Nov 10, 2008 at 12:09 PM, Tom Boutell <[EMAIL PROTECTED]> wrote:
>
> > These do sound like nonoptimal features of PHP 5.1, but not
> > dealbreaker bugs/absent features that make the Symfony core turn up
> > its nose and refuse to play. (: I am also sympathetic to the
> > observation that we can't all wait on Red Hat, but again... it doesn't
> > really answer my question. Does Symfony 1.2 really depend on PHP 5.2?
> > If so, in what way?
>
> > Thanks!
>
> > -Tom
>
> > On Mon, Nov 10, 2008 at 2:18 PM, Bernhard Schussek <[EMAIL PROTECTED]> 
> > wrote:
>
> >> I think a real problem with PHP 5.1 is its garbage collector and its
> >> memory allocation. I experienced a couple of bad memory errors and
> >> segmentation faults when working with PHP prior to 5.2.4, mainly in
> >> connection with Doctrine though. These errors were fixed and I highly
> >> recommend everyone to use PHP >= 5.2.4.
>
> >> Bernhard
>
> >> On Mon, Nov 10, 2008 at 3:29 PM, Tom Boutell <[EMAIL PROTECTED]> wrote:
>
> >>> See:
>
> >>>http://www.symfony-project.org/installation
>
> >>> Symfony 1.0: supported until January 2010.
> >>> Symfony 1.1: supported juntil January 2009.
> >>> Symfony 1.2: requires PHP 5.2.
>
> >>>http://www.centos.org/modules/newbb/viewtopic.php?topic_id=16915
>
> >>> Red Hat Linux 5 and CentOS 5: PHP 5.1.x. PHP 5.2.x is available only
> >>> from the "testing" repository in CentOS. It is not available in RHEL,
> >>> I believe.
>
> >>>http://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux
>
> >>> Red Hat Linux 6: expected first quarter 2010 at the earliest.
>
> >>> Looks like it could be difficult to use a supported, newer-than-1.0
> >>> version of Symfony on one of the most widely used server distributions
> >>> until at least first quarter 2010.
>
> >>> One can of course use a "testing" distribution or take on the project
> >>> of building PHP 5.2.x from source promptly each time a new subversion
> >>> comes out (to maintain the sort of security one has with 'yum
> >>> update'), but it's tough to sell an IT department on either of those
> >>> things.
>
> >>> How serious is Symfony 1.2's dependency on PHP 5.2? Which PHP 5.2
> >>> features are considered indispensable for Symfony 1.2?
>
> >>> I thought it might be a requirement of Propel 1.3 but was surprised to
> >>> find no reference to a requirement for anything other than PHP 5 on
> >>> the Propel site.
>
> >>> --
> >>> Tom Boutell
>
> >>>www.punkave.com
> >>>www.boutell.com
>
> > --
> > Tom Boutell
>
> >www.punkave.com
> >www.boutell.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to