Edit report at http://pear.php.net/bugs/bug.php?id=14589&edit=1

ID: 14589
Updated by: clbustos@surnet.cl
Reported By: francesco dot spegni at gmail dot com
Summary: the beautifier shouldn't delete empty rows i use for
making readable the code
-Status: Open
+Status: Bogus
Type: Feature/Change Request
Package: PHP_Beautifier
Operating System: ubuntu
Package Version: 0.1.14
PHP Version: Irrelevant
Roadmap Versions:
New Comment:

-Status: Open
+Status: Bogus
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the existing bug instead.

Thank you for your interest in PEAR.

Duplicate of 12271

Previous Comments:

[2010-01-13 13:10:08] fazend

You can configure this behavior by means of NewLines filter. Read this


[2008-09-03 06:48:33] francescospegni

i think the beautifier "eats" too many empty rows, even those i use (as
an example) for dividing a function or method definition from the
previous ones. it's like if the beautifier put the code lines too close
each other, and the code becomes less readable.

also, why not allowing (through a command line parameter) to chose
whether the curly parentheses should go on the same line or on the line

also: i think the leading <? such as the closing ?> should be on their
own row, without any other text after and before them.

what do you think about?

Test script:
<? function fie() { echo "fie"; } function foo() { echo "foo"; } foo();

Expected result:
function fie()
echo "fie";

function foo()
echo "foo";

foo(); ?>

Actual result:
<? function fie()
echo "fie";
function foo()
echo "foo";



Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
postedMar 16, '10 at 5:17a
activeMar 16, '10 at 5:17a

1 user in discussion

Clbustos: 1 post



site design / logo © 2022 Grokbase