mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-255: Add the PHP 5.3 version of the symfony yaml component for better compatibility with the Doctrine autoloader #316
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Jan 14, 2010).
Originally assigned to: @jwage on GitHub.
Jira issue originally created by user marijn:
I propose to integrate the PHP 5.3 version of the
sfYamlcomponent for better compatibility with other autoloaders. I'll try to submit a patch for this next week.See the SVN of Symfony for the related code: http://svn.symfony-project.com/branches/2.0/src/Symfony/Components/YAML/
@doctrinebot commented on GitHub (Jan 18, 2010):
Comment created by shurakai:
The link you've supplied is within the 2.0 branch. This branch is itself under heavy development and I'm not quite sure whether the yaml-parser is already marked as "stable" yet...?
@doctrinebot commented on GitHub (Jan 18, 2010):
Comment created by marijn:
The original sfYaml component for php 5.2 was released in early march I believe. The 2.0 branch is indeed under heavy development but if you check out the timeline for the Yaml component you'll see that aside from a few bugfixes nothing is really hapening in that part of the repo. As far as I know is the 5.3 version only a port that takes advantage of namespaces. To me the advantage seems to be that by using the 5.3 version people that already have the Yaml component wont include another version. Besides, I believe the symfony team won't support the 5.2 versions of the components which is perhaps is the best motivation for using the new 5.3 version.
@doctrinebot commented on GitHub (Mar 18, 2010):
Comment created by romanb:
Jon, I think this is now fixed?
@doctrinebot commented on GitHub (Mar 19, 2010):
Comment created by @jwage:
Yes, it is fixed now. If you use the Yaml component you need to register an autoloader for it now:
@doctrinebot commented on GitHub (Mar 19, 2010):
Issue was closed with resolution "Fixed"