Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1171 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7791 invoked from network); 2 May 2003 16:56:46 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 2 May 2003 16:56:46 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h42GujC6024060; Fri, 2 May 2003 18:56:46 +0200 Date: Fri, 2 May 2003 18:56:45 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: Oto Hlincik cc: internals@lists.php.net In-Reply-To: <004701c310c6$f6f53560$ec03020a@mercyhurst.local> Message-ID: References: <004701c310c6$f6f53560$ec03020a@mercyhurst.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Comments within code From: derick@php.net (Derick Rethans) On Fri, 2 May 2003, Oto Hlincik wrote: > Quick Question... > > How does a large amount of Comments within code (especially Class > definitions) affect script performance? Not that much, it's mostly the reading of it that will take the most time. It can't be an excuse to not document your code ;) Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------