WIP: Refactor handling of code blocks with just comments

[czosel]

Fixes #509

[czosel]

I tried fixing #509 and got the feeling that we might make our lives much easier by creating new AST nodes for code blocks that contain just comments, so I gave it a try. It seems to work quite well, but I still have issues with linebreaks/whitespace introduced by printLines.
@evilebottnawi Do you agree that the new AST nodes make it much easier? Do you have an idea how to fix the whitespace issues?

[alexander-akait]

@czosel i can look on this at Monday, little vacation, also we have some regression after last commit (comments), i will create issue. Also i think we should create issue in parser, maybe new option for this or modify standard behavior.

[czosel]

@evilebottnawi no rush, enjoy your vacation 😉

[czosel]

Related to glayzzle/php-parser#169

[alexander-akait]

Bug with extra here

[alexander-akait]

@czosel can you add test

<?php
if (true) {
    ?>inline<?php
    // comment
}

from #517

[alexander-akait]

To be honest, I'm not sure that the idea of creating new ast nodes is good. Can you add link on issue in source code?

[czosel]

@evilebottnawi done! I agree that the "post-production" AST manipulation doesn't seem very clean. The printer code is quite clean though, and it seems to me that any other approach without parser changes is not working/really hard to maintain. We should try to keep "our" AST closely aligned with what the PHP parser will do in the future, then migration will be easy.

[alexander-akait]

@czosel let's add test from #526

[alexander-akait]

Also need fix space and we can merge

[alexander-akait]

@czosel Please read #532 (comment). Let's search solution without new ast nodes (fix it in parser or prepare text for parser).

[czosel]

@evilebottnawi agreed.