The following tags are being dropped in PHP7:

• <%
• <%=
• %>
• (<script\s+language\s*=\s*(php|"php"|'php')\s*>)
• </script>

They should be automatically replaced.

Context: https://wiki.php.net/rfc/remove_alternative_php_tags

While doing so is generally a bad idea from a code perspective, it's relatively common to do something like the following:

/**
 * @return Foo|int|bool Some weird conditional return value
 */
function ambiguousReturnValue() { }

Multiple types are not allowed per the RFC, and selecting one would be unacceptable. This needs tests asserting that ambiguous return values in the annotation do not add any annotation.

Code is often littered with $var = isset($some['value']) ? $some['value'] : $some_default;. It may be possible to detect simple cases of this and replace it with the new null coalesce operator: $var = $some['value'] ?? $some_default;

Source: https://wiki.php.net/rfc/isset_ternary

While it's unlikely anyone still using the long-deprecated mysql_ procedural API will be upgrading, supporting the conversion should be reasonably straightforward.

There should be a flag in the executable to append this after the open PHP tag.

The executable's options don't really do anything yet - the file is always dumped to STDOUT, and never written to a file.

This should be fixed, and there should be a --replace option added. Using it should probably check that you're not on master, since replacing code ad-hoc is dangerous and stupid.

I'm trying run php7ize but I have an error

$ php7ize
Composer autoload.php could not be located

How to solve it ?

No updates in seven months and no description of the usage. I assume you are not following this path anymore?

The RFC explicitly disallows return types for the following methods:

• __construct
• Implicit name-based constructors
• __destruct
• __clone

In order to generate syntactically valid code, those functions must not be annotated.