Book a Demo

Author Topic: PHP reverse code engineering - parse problem  (Read 2439 times)

lubosdz

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
PHP reverse code engineering - parse problem
« on: January 07, 2012, 11:31:02 pm »
Hi,

when trying PHP reverse code engineering (PHP5), following code fails to import:

1. There was an error parsing D:\_projects\myproject\core\common.php on line 683.  Unexpected symbol: xor      

in code fragment:

Code: [Select]
if (K_DEBUG_POLICY xor $bException) error_log(date("Y.m.d. H:i:s") . "> $str\n", 3, $name);

2. There was an error parsing D:\_projects\source\custom\cms\cms.php on line 98.  Unexpected symbol: ,      

(multiline issue)

Code: [Select]

      const

            SEO_KEY_RSS = 'rss',

            // document thumb width in px
            THUMB_WIDTH = 80,

            // document thumb height in px
            THUMB_HEIGHT = 80,
            
            // SEO_KEY for parent document holding all extra info
            EXTRA_POV_PARENT_KEY = 'parent-pov',
            
            // CMS URL Alias for template "Product information"
            URL_INFORMACE_O_PRODUKTU = 'informace-o-produktu-ajax';



3. There was an error parsing D:\_projects\views\uk\profile-summary.php on line 28.  Unexpected symbol: <      

Code: [Select]
echo <<<EOD
      <tr style="background:{$color}">
            <td align="center">{$time}</td>
            <td>{$log[1]}</td>
            <td>{$log[2]}</td>
            <td>{$message}</td>
      </tr>
EOD;
(heredoc syntax, reported also in my previous post)

Using EA 7.5, Win7 x86.
Lubos

« Last Edit: January 07, 2012, 11:32:16 pm by lubosdz »

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: PHP reverse code engineering - parse problem
« Reply #1 on: January 09, 2012, 09:11:12 am »
1. Appears to be a problem with xor. I suggest updating your support and sending a bug report to via email to Sparx Systems.

2. Corrected in the current build.

3. As mentioned in your previous post, corrected in the current build.