Description Frederic Fusier 2009-06-12 07:50:40 EDT

Follow-up of bug 270148...

Using build I20090609-1400 and considering the following snippet:

  class MyCommand extends CommandBase
  {
    protected Command subcommand;

    //...

    public void execute()
    {
      // ...
      Compound subcommands = new CompoundCommand();
      subcommands.appendAndExecute(new AddCommand(...));
      if (condition) subcommands.appendAndExecute(new AddCommand(...));
      subcommand = subcommands.unwrap();
    }

    public void undo()
    {
      // ...
      subcommand.undo();
    }

    public void redo()
    {
      // ...
      subcommand.redo();
    }

    public void dispose()
    {
      // ...
      if (subcommand != null)
     {
        subcommand.dispose();
      }
    }
  }

Before bug 270148 was fixed, parsing the snippet using the
Parser.parseClassBodyDeclarations(...) method returned null. After, e.g. using HEAD, it returns an array with one TypeDeclaration which seems to be the expected result.

However, now considering another snippet:

  class MyCommand extends CompoundCommand
  {
    public void execute()
    {
      // ...
      appendAndExecute(new AddCommand(...));
      if (condition) appendAndExecute(new AddCommand(...));
    }
  }

Parsing it with the same Parser method still returns null. After bug 270148 was fixed, I would expect a non null result for the second snippet either...