RE: [PEAR-DEV] Pear Installer to remove comments

From: Date: Mon, 08 Sep 2003 18:18:33 +0000
Subject: RE: [PEAR-DEV] Pear Installer to remove comments
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-21199@lists.php.net to get a copy of this message
> From: Lukas Smith [mailto:smith@backendmedia.com] > Sent: Monday, September 08, 2003 8:08 PM > > > From: Stan Lemon [mailto:insyder@myrealbox.com] > > Sent: Monday, September 08, 2003 8:07 PM > > > I agree with Arnaud on this one. I'm not convinced that the times are > > significant enough. PEAR has a hard enough time getting docs made and > > getting *good* inline doc block comments, the idea of removing > comments > > seems like a step in the wrong direction, regardless of the purpose. > > > > - Stan > > > > Arnaud Limbourg wrote: > > >>Is it possible to have per installer to strip comments on install of > > >>package (with some optional switch of cource) > > >> > > >>it sounds like a relativle easy way of redusing some cpu cycles, a > log > > >>of pear package have 30% > of comments in them. Would'n it make them > > >>faster to remove the comments. On a production system source is > rarly > > >>read. It should be trivial to be done with the tokenizer extension. > > >> > > >>Just a random thought I had over the week end. > > > > > > > > > Ilia had done some benchmarking on this, you would need a very large > > file with a very large amount of comments to begin to notice anything. > > > > > > Plus i often browse the installed code to see what it does, without > > comments it would be much harder ;) > > Finally the approriate solution to this "problem" is to use a bytecode > cache. It was brought to my attention that not everybody knows what a bytecode cache. The quick summary is that it caches the compiled variant of a php script instead of requiring a compile every time the script is accessed. You can use the PECL extension APC for this. Regards, Lukas

« previous php.pear.dev (#21199) next »