Eclipse Corner Articles - The Diigo Meta page

• 19 Apr 16
  

  reyhanjb
  • • IPackageFragmentRoot: can be a source or a class folder of a  project, a  .zip or a  .jar file.  IPackageFragmentRoot can hold source or binary  files.
• 29 Oct 14
  

  gyoomin

  eclipse ast

• 03 Sep 14
  

  diigo34443
  • ICompilationUnit is a pointer to a Java file
• 04 Feb 14
  

  qqibrow
  • As mentioned, the Abstract Syntax Tree is the way that Eclipse looks at your source  code
• 13 Jun 12
  

  max j

  Eclipse AST Abastract Syntax Tree

• 16 Apr 12
  

  azarai

  eclipse java ast

• 13 Jan 12
  

  ychhet
  • The Abstract Syntax Tree is the base framework for many powerful tools of the  Eclipse IDE, including refactoring, Quick Fix and Quick Assist
  • The Abstract Syntax  Tree maps plain Java source code in a tree form. This tree is more convenient and  reliable to analyse and modify programmatically than text-based source. This  article shows how you can use the Abstract Syntax Tree for your own  applications.

  • Are you wondering how Eclipse is doing all the magic like jumping conveniently to a  declaration, when you press  "F3" on a reference to a field or method? Or how "Replace in file"  solidly detects the declaration and all the references to the local variable and  modifies them synchronously?
  • Well, these—and a big portion of the other source code modification and generation  tools—are based upon the Abstract Syntax Tree (AST). The AST is comparable to the DOM  tree model of an XML file. Just like with DOM, the AST allows you to modify the tree model and  reflects these modifications in the Java source code.
  • This article refers to an example application which covers most of the  interesting AST-related topics. Let us have a look at the application that was built to  illustrate this article:

  • According to Java Practices [4], you  should not declare local variables before using them. The goal of our application  will be to detect contradicting variable declarations and to move them to their  correct place. There are three cases our application has to deal with: 

    1. Removal of unnecessary declaration. If a  variable is declared and initialized, only to be overridden by another  assignment later on, the first declaration of the variable is an  unnecessary declaration.

    2. Move of declaration. If a variable is declared,  and not immediately referenced within the following statement, this variable  declaration has to be moved. The correct place for the declaration is the line  before it is first referenced.

    3. Move of declaration of a variable that is referred to from within  different blocks. This is a subcase of case 2. Imagine that a variable is used  in both a try- and a catch clause. Here the declaration cannot be moved right  before the first reference in the try-clause, since then it would not be  declared in the catch-clause. Our application has to deal with that and has to  move the declaration to the best possible place, which would be here one line  above the try-clause.
  • In Appendix A, Code Fragments for Example Application Cases code snippets  to each of these cases are provided.

    You can import the example application into your workspace [1] or install the plug-in using the Eclipse Update  Manager [2].
  • Java source: To start off, you provide  some source code to parse. This source code can be supplied as a  Java file in your project or directly as a  char[] that contains Java source
  • Parse: The source code described at  1 is parsed. All  you need for this step is provided by the class  org.eclipse.jdt.core.dom.ASTParser. See the section called “Parsing source code”.
  • The Abstract Syntax Tree is the result of step  2. It is a tree model that entirely  represents the source you provided in step 1. If requested, the parser also computes  and includes additional symbol resolved information called "bindings".

  8 more annotations...

• 05 Jan 12
  

  chrisjbird

  eclipse Java

• 15 Apr 11
  

  Rodrigo Costa

  ording to Java Practices [4], you should not declare local variables before using them. The goal of our application will be to detect contradicting variable declarations and to move them to their correct place. There are three cases our application has to

  eclipse ast refactor

• 09 Mar 11
  

  arnout evers

  AST java

• 21 Dec 10
  

  eugenio abello

  everis eclipse ast java codegenerator

• 22 Apr 10
  

  Alexandra N

  eclipse java plugin article tutorial howto extract strings code manipulation

• 16 Mar 10
  

  Sven Duzont

  "The Abstract Syntax Tree is the base framework for many powerful tools of the Eclipse IDE, including refactoring, Quick Fix and Quick Assist. The Abstract Syntax Tree maps plain Java source code in a tree form. This tree is more convenient and reliable to analyse and modify programmatically than text-based source. This article shows how you can use the Abstract Syntax Tree for your own applications."

  eclipse ast article java programming tutorial

• 05 Jun 09
  

  benpjohnson

  eclipse ast programming parser

• 05 Aug 08
  

  Simon Reavely

  java ast parser eclipse tutorial howto

• 02 Aug 08
  

  Ching Yi Chan

  eclipse ast jdt

• 21 Mar 08
  

  Alexandre Vanbelle

  eclipse ast

• 23 Sep 07
  

  Kim Bo Kastekniv

  The Abstract Syntax Tree is the base framework for many powerful tools of the Eclipse IDE, including refactoring, Quick Fix and Quick Assist.

  eclipse articles

• 21 Jul 07
  

  cwalltx

  ast eclipse

• 25 Jun 07
  

  Pavel Samokha

  eclipse ast

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.