Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50783 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93815 invoked from network); 1 Dec 2010 14:18:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Dec 2010 14:18:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.131 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.131 c2bthomr13.btconnect.com Received: from [213.123.20.131] ([213.123.20.131:23022] helo=mail.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CF/60-25725-42956FC4 for ; Wed, 01 Dec 2010 09:18:15 -0500 Received: from host81-138-11-136.in-addr.btopenworld.com (EHLO _10.0.0.4_) ([81.138.11.136]) by c2bthomr13.btconnect.com with ESMTP id AWB53204; Wed, 01 Dec 2010 14:16:03 +0000 (GMT) Message-ID: <4CF658A2.5080409@lsces.co.uk> Date: Wed, 01 Dec 2010 14:16:02 +0000 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.14) Gecko/20101013 SUSE/2.0.9-2.1 SeaMonkey/2.0.9 MIME-Version: 1.0 To: PHP internals References: <003601cb8fd0$f6494e80$e2dbeb80$@com> <4CF3B855.5010406@sugarcrm.com> <003401cb8fee$1be39840$53aac8c0$@com> <2450924ae03481f5b1382a7f00e5743d.squirrel@webmail.basnetworks.net> <4CF50245.5020807@sugarcrm.com> <4CF5118B.2030300@sugarcrm.com> <1faa4c3db62771335db714507ac2adfa.squirrel@webmail.basnetworks.net> <4CF613EB.40200@sugarcrm.com> <23d1e573d22236bad96d57ffff4e3001.squirrel@webmail.basnetworks.net> In-Reply-To: <23d1e573d22236bad96d57ffff4e3001.squirrel@webmail.basnetworks.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4CF658A3.002F, actions=tag X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4CF65921.035C,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Subject: Re: [PHP-DEV] RFC: C-sharp style property get/set syntax for PHP From: lester@lsces.co.uk (Lester Caine) president@basnetworks.net wrote: > Its a defacto standard. Of course there is nothing stopping PHP from > implementing properties that way, but by going against the standard set by > the rest of the industry, it is very confusing for programmers coming from > other languages to learn PHP. A good example is how "==" works > differently in PHP than in other languages. In PHP, "===" works like "==" > does everywhere else. "(string)'0' == (int)0", for example is true in > PHP, but false in most other languages. I have had countless > conversations with PHP developers who claim the language is "broken", > because == does not work like they expect it to, after which I have to > explain === to them. This is because PHP goes against the defacto > standard. Maybe it would have been better if == and === had the opposite > meaning, as to not squash the standard? You have got me there. = is assign == is equal value === is equal type and value At least on all the languages I've been using recently ... where is this a problem? Also isset() makes perfect sense when you have NULL values coming from a database. unset then kicks a NULL back to the database if updating. The varable exists but has a NULL value ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php