Ticket #266 (new enhancement)

Opened 1 year ago

Last modified 1 year ago

EAccelerator is more strict than PHP itself

Reported by: marcog Assigned to: somebody
Priority: minor Milestone:
Component: eAccelerator Version:
Keywords: Cc:

Description

Our php normally accepts 

$obj = new WorkingClass();

class WorkingClass{
  function WorkingClass(){
    // ...
  }
  // ...
}

which is a bit strange, but the code works with those parts.

I didn't find any warning about it, so I thought it might be a yet unknown difference.

I have no clue if it would be a great deal to change that.

Change History

08/14/07 16:42:26 changed by hans

Ehm, this ticket doesn't make any sense to me, sorry.

Do you mean your constructor doesn't get cached or something? That sounds highly unlikely to me.

Please enlighten us!

09/08/07 22:47:33 changed by marcog

ok, in php I can do 

<?
$x = new SomeThing();

class SomeThing(){
//bla
}
?>

with EAccelerator it only works that way: 

<?
class SomeThing(){
//bla
}

$x = new SomeThing();
?>

The first way around I get an error like unknown function call. At least when the example is deep inside of a bunch of include-files. Hope that helps!