Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14268 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82318 invoked by uid 1010); 4 Jan 2005 03:00:23 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81776 invoked from network); 4 Jan 2005 03:00:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2005 03:00:18 -0000 X-Host-Fingerprint: 195.82.120.217 stack.fission.org.uk Linux 2.4/2.6 Received: from ([195.82.120.217:34783] helo=stack.fission.org.uk) by pb1.pair.com (ecelerity HEAD (r3992M)) with SMTP id BE/CC-27561-0C60AD14 for ; Mon, 03 Jan 2005 22:00:17 -0500 Received: from mesa.fission.org.uk ([82.70.115.105]) by stack.fission.org.uk with esmtp (Exim 3.36 #1 (Debian)) id 1Cleul-0003KK-00 for ; Tue, 04 Jan 2005 02:59:19 +0000 Message-ID: <41DA068A.9080009@fission.org.uk> Date: Tue, 04 Jan 2005 02:59:22 +0000 User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: bit of an odd bug From: gareth@fission.org.uk (Gareth Ardron) Ok, I'm in need of a sanity check here. step one: $input = "foo"; $scanning_class = "clamav"; $result = $scanning_class::scanBuffer($input); now this fails with a "Parse error: parse error, unexpected T_PAAMAYIM_NEKUDOTAYIM" So ok, you can't put variables at the front on a class call like that. Minor bug I'm thinking at this point, but I wonder if I can work round it. So, onto step two: $input = "foo"; $scanning_class = "clamav"; $func = $scanning_class."::scanBuffer"; $result = $func($input); Which fails with a "Fatal error: Call to undefined function clamav::scanBuffer()" Just doing: $result = clamav::scanBuffer($input); of course works absolutly fine. Somebody just tell me that this isn't exactly expected behaviour and it's a minor bug this is all on 5.0.3 btw. Cheers. -- Gareth Ardron