Issues with PHP highlighter

Sure, that's easy... you can modify the string state to have these pattern groups:

Hi,

>Sure, that's easy... you can modify the string state to have these pattern groups:

That's exactly what I tried, but it didn't work. I guess my Regular Expression was not as good as your, although I tested it in RegexBuddy where it worked fine. Oh well, thank you :)

Now, on to the next problem. Have a look at the following piece of HTML, with PHP blended in to it:

<input type="text" name="test" value="<?= $testVar; ?>" />

This is perfectly valid, yet the PHP is not colored, probably because it's within an HTML tag. Once again, the solution might be simple, or it might not even be possible (which would be a shame though). I'm just not sure how to solve it best, so I hope you can help me once again :)

You'd probably just have to make a PHP child state and allow it to be called from the StartTagAttributeStringValueState in the HTML definition.

Hi,

I'm sorry, but I'm still no expert on this. Could you possibly provide a bit more details on how to do it? :)

Take a look at the HTML definition at like the ASPDirectiveCodeState block. Copy it and change that to the proper delimiters for PHP. Then have it call your PHP language file instead. Then reference the new state you made as a ChildState in the StartTagAttributeStringValueState. There are examples of it all throughout the HTML definition so that should get you going.

Thank you so much! I had of course already defined a PHPDirectiveCodeState, so I simply added it to the ChildStates of StartTagAttributeValueState and StartTagAttributeState. Now it works brilliantly! :)

Sorry for all the questions, but I'm still learning how to properly use the languages of SyntaxEditor. It can be a bit tricky, even with the good documentation included :)

I'm having another minor issue here. I have already defined the PHPDirectiveCodeState as a ChildState to the StartTagAttributeStringValueState, which means that something like this works fine: However, have a look at this one: Because the PHP block is not the first part of the value, it's ignored. I don't really get why though, but I'm sure there is some logical explanation, but is there a way to fix it as well? :)

The lexical parser is greedy so once it starts matching a pattern it will not stop until the end. Therefore it is probably matching string attribute contents and is not looking to end on a < character. The HTML def probably has a regex that says match one or more tokens that aren't a quote character. Add a < character to the set as well. That will cause it to break there.

Thank you, that seems to work :)