Re: basic issue with ScriptReorganizer and pharize

Dear All! On Wed, 01 Jun 2005 01:58:33 +0200, Stefano F. Rausch <pear@sf.rausch-e.net> wrote:

On Tue, 31 May 2005 19:29:26 +0200, Davey Shafik <davey@php.net> wrote:

One more thing to point out: <?php echo <<<EOL TXT; EOL; ?> is simply not valid. - Davey

Correct you are Davey and thanks for having spotted the Heredoc issue. I have already a working solution for it (still pondering, if it is the best fix) and I will release ScriptReorganizer 0.2.1 later today. A respective notification will follow in due time.

I have finally packaged the release 0.2.1, which fixes the Heredoc bug highlighted by Davey - thanks for your valuable input. You can download the new release either at http://pear.sf.rausch-e.net/pepr/ScriptReorganizer/ScriptReorganizer-0.2.1.tgz or at http://download.berlios.de/screo/ScriptReorganizer-0.2.1.tgz. Enjoy! Please test this release and report any outstanding issue - if there are any ;)

Greg Beaver (http://pear.php.net/user/cellog) has voted +1 on the proposal for Tools andUtilities::ScriptReorganizer. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=247 Vote information: http://pear.php.net/pepr/pepr-vote-show.php?id=247&handle=cellog Comment: This looks very interesting. I would recommend adding an explicit mention in the documentation of the potential debugging issues.

I have already followed your advice in the 0.2.0 release by having added a notice in the API documentation for ScriptReorganizer_Strategy_Pack - see the message below too ;)

On Tue, 24 May 2005 00:25:20 +0200, Stefano F. Rausch <stefano@rausch-e.net> wrote: Dear All, Unfortunately PEPr didn't process my change log as well as the call for votes in one go! The following log message is missing: <quote> Updated the sections "Example" and "Known Issues" (Greg Beaver pointed out the issue of bugtracking with packed source code) as well as the link to the PEAR Package File new release0.2.0 Second release can still be downloaded at http://pear.sf.rausch-e.net/pepr/ScriptReorganizer/ScriptReorganizer-0.1.1.tgz </quote> Thanks for taking notice of this fact.

For complex applications that are pharred, it should be recommended to have a "debug" version of the phar that the user can download and use to locate bugs. The debug version would contain non-ScriptReorganized versions of the package.

Right you are Greg. In the new release your recommendations have been incorporated in the API documentation for ScriptReorganizer_Type_Decorator_Pharize as follows: Suggested practice to follow, if the advanced pack mode of the Pack strategy is used for the optimization of the PHP_Archive to create: 1. Creation of a debug version: reorganization of the source applying the default pack mode. 2. Running of all tests. 3. Creation of a deployment version: reorganization of the source applying the advanced pack mode. 4. Shipping of both versions, to enable third parties to track down undiscovered bugs.

This is a "someone should really do that" kind of package, thanks for writing it.

The pleasure is mine and thanks for your support! -- Stefano