Jump to: navigation, search

Difference between revisions of "Type inference for APDT"

(Hello World)
(Hello World)
Line 88: Line 88:
 
$foo = new Foo();
 
$foo = new Foo();
 
$bar = new Bar();
 
$bar = new Bar();
$foo->bar();
+
$foo->fuebar();
$bar->bar();
+
$bar->fuebar();
$unknown->bar();
+
$unknown->fuebar();
 
?>
 
?>
 
</source>
 
</source>
 
And the following joinpoint (all method invocation of the bar() method in an instance of Foo):
 
And the following joinpoint (all method invocation of the bar() method in an instance of Foo):
<source lang="java">call(Foo->bar())</source>
+
<source lang="java">call(Foo->fuebar())</source>
 
Before this summer, when you were writing a such joinpoint, PHPAspect was testing the type of ''$foo'', ''$bar'' and ''$unknown'' to check if the joinpoint has been matched and then execute the associated code-advince.
 
Before this summer, when you were writing a such joinpoint, PHPAspect was testing the type of ''$foo'', ''$bar'' and ''$unknown'' to check if the joinpoint has been matched and then execute the associated code-advince.
 
By using DLTK/PDT type inference engine, APDT knows that ''$foo'' is an instance of Foo therefore the joinpoint has been statically matched. ''$bar'' isn't an instance of Foo, this node in the PHP Program is left unchanged. The type of ''$unknown'' is unknown, APDT adds a runtime assertion: the type of $unknown is tested at runtime to check for code-advice execution.
 
By using DLTK/PDT type inference engine, APDT knows that ''$foo'' is an instance of Foo therefore the joinpoint has been statically matched. ''$bar'' isn't an instance of Foo, this node in the PHP Program is left unchanged. The type of ''$unknown'' is unknown, APDT adds a runtime assertion: the type of $unknown is tested at runtime to check for code-advice execution.
 
The weaved source code is the following:
 
The weaved source code is the following:
 +
<source lang="php">
 +
$foo = new Foo();
 +
$bar = new Bar();
 +
PHPAspect_dispatch(array(2,),new JoinPointImpl(JoinPoint::METHOD_EXECUTION,$foo,new ReflectionMethod($foo,'fuebar'),array(),__FILE__,__LINE__),array(2=>true,));
 +
$bar->fuebar();
 +
PHPAspect_dispatch(array(2,),new JoinPointImpl(JoinPoint::METHOD_EXECUTION,$unknown,new ReflectionMethod($unknown,'fuebar'),array(),__FILE__,__LINE__),
 +
  array(2=>(PHPAspect_match($unknown,'Foo')),));
 +
</source>
 +
Above, the call of ''$foo->fueaber()'' is matched, ''$bar->fuebar()'' is unchanged and ''$unknown->fuebar()'' has the runtime assertion ''PHPAspect_match($unknown,'Foo')''.
  
 
== Features ==
 
== Features ==

Revision as of 10:35, 19 August 2008

Abstract

The Aspect PHP Development Tools (APDT) project provides Eclipse platform based tool support for AOSD with PHPAspect. Our goal is to deliver a user experience that is consistent with the PHP Development Tools (PDT) when working with PHPAspect projects and resources. This plugin provides an integration layer between the PHPAspect weaver, runtime and Eclipse/PDT extension points.

Due to the highly dynamic nature of PHP, most of PHPAspect joinpoints can't be determined statically: PHPAspect weaves hooks in the source code in order to perform type checking at runtime. When a project is woven, a significant amount of hooks can be inserted in the source even though it be can statically analyzed that none of these hooks will trigger a code-advice: this is where type inference comes in.

APDT and PDT have both an integration layer with DLTK which as an experimental type inference framework used to improve code analysis on dynamic languages.

The type inference could be also used to improve APDT UI by providing aspect type information in the editor.

Participants

  • Student: William Candillon
  • Mentor: Michael Spector

Getting the source

The source is available on APDT SVN repository. APDT contains many eclipse plugins and the runtime library for PHP.

Project Description
PHPAspect Runtime support for PHPAspect: joinpoint dispatcher, aspect reflection API.
PHPAspectTest Test for PHPAspect runtime library.
PHPAspectTest Test for PHPAspect runtime library.
org.phpaspect.apdt APDT main plugin.
org.phpaspect.apdt.core Core plugin.
org.phpaspect.apdt.debug.core PHPAspect core launcher.
org.phpaspect.apdt.debug.ui PHPAspect UI launcher.
org.phpaspect.apdt.feature APDT feature.
org.phpaspect.apdt.help APDT help (empty for now).
org.phpaspect.apdt.sdk-feature APDT SDK feature.
org.phpaspect.apdt.ui APDT UI features.
org.phpaspect.apdt.updatesite APDT Update site.
org.phpaspect.apdt.documentation PHPAspect documentation
org.phpaspect.weaver PHPAspect weaver
org.phpaspect.weaver.test PHPAspect weaver test cases

Hello World

Let's consider a simple piece of PHP code:

<?php
class Foo{
  public function fuebar(){
    return true;
  }
}
 
class Bar{
  public function fuebar(){
    return true;
  }
}
 
$foo = new Foo();
$bar = new Bar();
$foo->fuebar();
$bar->fuebar();
$unknown->fuebar();
?>

And the following joinpoint (all method invocation of the bar() method in an instance of Foo):

call(Foo->fuebar())

Before this summer, when you were writing a such joinpoint, PHPAspect was testing the type of $foo, $bar and $unknown to check if the joinpoint has been matched and then execute the associated code-advince. By using DLTK/PDT type inference engine, APDT knows that $foo is an instance of Foo therefore the joinpoint has been statically matched. $bar isn't an instance of Foo, this node in the PHP Program is left unchanged. The type of $unknown is unknown, APDT adds a runtime assertion: the type of $unknown is tested at runtime to check for code-advice execution. The weaved source code is the following:

$foo = new Foo();
$bar = new Bar();
PHPAspect_dispatch(array(2,),new JoinPointImpl(JoinPoint::METHOD_EXECUTION,$foo,new ReflectionMethod($foo,'fuebar'),array(),__FILE__,__LINE__),array(2=>true,));
$bar->fuebar();
PHPAspect_dispatch(array(2,),new JoinPointImpl(JoinPoint::METHOD_EXECUTION,$unknown,new ReflectionMethod($unknown,'fuebar'),array(),__FILE__,__LINE__),
  array(2=>(PHPAspect_match($unknown,'Foo')),));

Above, the call of $foo->fueaber() is matched, $bar->fuebar() is unchanged and $unknown->fuebar() has the runtime assertion PHPAspect_match($unknown,'Foo').

Features

  • Improved code completion in the APDT editor.
  • Quick assist markers in the APDT editor, like AJDT provides (semantic analysis).

Community Proposals

Links

APDT Website

An overview of APDT

PHPAspect Website