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

ID: 14589
Comment by: team@fazend.com
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
Type: Feature/Change Request
Package: PHP_Beautifier
Operating System: ubuntu
Package Version: 0.1.14
PHP Version: Irrelevant
Roadmap Versions:
New Comment:

You can configure this behavior by means of NewLines filter. Read this
page:
http://beautifyphp.sourceforge.net/docs/PHP_Beautifier/Filter/PHP_Beautifier_Filter_NewLines.html


Previous Comments:
------------------------------------------------------------------------

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

Description:
------------
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
below?!?

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";
}

foo();
?>

------------------------------------------------------------------------

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedJan 13, '10 at 1:11p
activeJan 13, '10 at 1:11p
posts1
users1
websitepear.php.net

1 user in discussion

Team: 1 post

People

Translate

site design / logo © 2022 Grokbase