Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document best practices for updating to new PHP versions #147

Open
dktapps opened this issue Nov 19, 2024 · 0 comments
Open

Document best practices for updating to new PHP versions #147

dktapps opened this issue Nov 19, 2024 · 0 comments

Comments

@dktapps
Copy link
Member

dktapps commented Nov 19, 2024

There's a few tricks I picked up over the years to figure out what needed to be changed in new versions:

  • git diff PHP-8.2..PHP-8.3 -- php-src/ext/opcache/zend_persist.c (replace 8.2 and 8.3 with the old & new version respectively) is a great source of info for what needs fixing for class & function copying
  • Test ALL new language features. Pretty much every time a new feature gets added, it breaks in threads because there was some new data associated with it.
  • Build & run tests locally with AddressSanitizer. This often catches errors that Valgrind doesn't see.

to be continued...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant