Group :: Desenvolvimento/Outros
RPM: pear-ScriptReorganizer
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 0.4.0-alt1
Data da compilação: 30 junho 2009, 21:40 ( 769.4 weeks ago )
Tamanho:: 252.58 Kb
Home page: http://pear.php.net/package/ScriptReorganizer
Licença: LGPL
Sumário: Library/Tool focusing exclusively on the file size aspect of PHP script optimization
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 30 junho 2009, 21:40 ( 769.4 weeks ago )
Tamanho:: 252.58 Kb
Home page: http://pear.php.net/package/ScriptReorganizer
Licença: LGPL
Sumário: Library/Tool focusing exclusively on the file size aspect of PHP script optimization
Descrição:
ScriptReorganizer has the ability to reorganize source code in different
(incremental) ways:
- File: one-to-one (Script) or many-to-one (Library) optimization.
- Source: EOL (Route), comment (Quiet) and whitespace (Pack) optimization.
Plugin functionality is available by means of the Decorator Pattern.
It is highly recommended to follow the best practice detailed out below,
when using this package:
1. Running of all tests before building releases to deploy.
2. Reorganization of the source code file(s) with ScriptReorganizer.
3. Running of all tests - not only unit tests!
4. Final building of the release to deploy.
If the extreme mode of the pack strategy is used for packaging, a
non-ScriptReorganized source code tree should be shipped together with the
optimized one, to enable third parties to track down undiscoverd bugs.
Same applies for (complex) applications that are pharized, i.e. optimized
and packaged with PHP_Archive, as well as for bcompiled scripts.
ANN: Currently only pure PHP code can be reorganized. Look into the folder
root/PEAR/docs/ScriptReorganizer for more information in depth.
Mantenedor currente: Vitaly Lipatov (incremental) ways:
- File: one-to-one (Script) or many-to-one (Library) optimization.
- Source: EOL (Route), comment (Quiet) and whitespace (Pack) optimization.
Plugin functionality is available by means of the Decorator Pattern.
It is highly recommended to follow the best practice detailed out below,
when using this package:
1. Running of all tests before building releases to deploy.
2. Reorganization of the source code file(s) with ScriptReorganizer.
3. Running of all tests - not only unit tests!
4. Final building of the release to deploy.
If the extreme mode of the pack strategy is used for packaging, a
non-ScriptReorganized source code tree should be shipped together with the
optimized one, to enable third parties to track down undiscoverd bugs.
Same applies for (complex) applications that are pharized, i.e. optimized
and packaged with PHP_Archive, as well as for bcompiled scripts.
ANN: Currently only pure PHP code can be reorganized. Look into the folder
root/PEAR/docs/ScriptReorganizer for more information in depth.
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- pear-ScriptReorganizer