Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44963
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain keryx.se designates 208.69.121.33 as permitted sender)
Message-ID: <4A5CF17B.1040102@keryx.se>
Date: Tue, 14 Jul 2009 22:58:35 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090713 Lightning/1.0pre Shredder/3.0b3pre
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ctype functions going, going, gone?
From: webmaster@keryx.se (Keryx Web)

Hi all!

I am preparing a Server Side Scripting (using PHP) course for the Web 
Standards Project Interact[1]. As I am going through security 
considerations I note that the ctype functions are being used in the 
manual[2] and have not been deprecated in 5.3. I have, however, been 
told that they are not, nor ever will be, Unicode compatible.[3]

If that indeed is the case:

A. Should they not be deprecated formally, including giving an 
appropriate error when used? (Yes, that will give some people, like me, 
lots of errors. But I rather take them now than have my code blow up on 
me in the future.)

B. Should not the the manual be telling people about these functions 
being non-future proof?


-- 
Keryx Web (Lars Gunther)
http://keryx.se/
http://twitter.com/itpastorn/
http://itpastorn.blogspot.com/

1. http://interact.webstandards.org/
2. http://www.php.net/manual/en/security.filesystem.php
3. http://marc.info/?l=phpdoc&m=119678432606169

P.S. If you are interested in helping us at WaSP make an awesome 
curriculum for our PHP course, contact me off list.