You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
A thread has come up on the forum that points out that <?php ... ?> doesn't get matched as PHP code when on the same line. I did a little bit of poking around and found that the embedded whitespace pattern has a negative lookahead (?![^?]*\\?>) that, when removed, allows single-line PHP comments to display. The thing is, I can't figure out what that negative lookahead was put there to check against. My fork of this package seems to work just fine.
Does anybody know what the negative lookahead was meant to guard against?
The text was updated successfully, but these errors were encountered:
A thread has come up on the forum that points out that
<?php ... ?>
doesn't get matched as PHP code when on the same line. I did a little bit of poking around and found that the embedded whitespace pattern has a negative lookahead(?![^?]*\\?>)
that, when removed, allows single-line PHP comments to display. The thing is, I can't figure out what that negative lookahead was put there to check against. My fork of this package seems to work just fine.Does anybody know what the negative lookahead was meant to guard against?
The text was updated successfully, but these errors were encountered: