Code: Select all
$message = <<<EOT
The form was submitted on $now.
USER'S BROWSER: $browser
USER'S IP ADDRESS: $ip
EOT;
Code: Select all
S BROWSER: $browser
USER
Eric
Bug? Heredoc Syntax Highlighting
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Bug? Heredoc Syntax Highlighting
I just noticed today in WeBuilder 2005 that if I use quotation marks in a PHP heredoc statement, the syntax colouring gets messed up. For example, in the following:
the characters within the single quotation marks get color-coded differently than the rest of the HEREDOC statement.
Does it work the same way in 2006?
Eric
Eric
-
Karlis
- Site Admin
- Posts: 3605
- Joined: Mon Jul 15, 2002 5:24 pm
- Location: Riga, Latvia, Europe
- Contact:
Currently <<< strings are not supported. We are looking toward implementing this, however due to some tech difficulties this is going to take more time.
For techy members I can explain the problem. Syntax highlighter architecture (3rd party product) allows only static begin and end markers, so we can not make it highlight from <<<{variable name} to {variable name}, because both start and end must be predefined constant values.
Unfortunately in practice you may use not only EOT, but also EOF, END, DOG, FOG or wtatever.
So we are thinking how to solve this... providing that we can not change the syntax highlighting architecture.
For techy members I can explain the problem. Syntax highlighter architecture (3rd party product) allows only static begin and end markers, so we can not make it highlight from <<<{variable name} to {variable name}, because both start and end must be predefined constant values.
Unfortunately in practice you may use not only EOT, but also EOF, END, DOG, FOG or wtatever.
So we are thinking how to solve this... providing that we can not change the syntax highlighting architecture.