| CARVIEW |
Select Language
HTTP/2 200
server: myracloud
date: Sat, 11 Oct 2025 09:47:17 GMT
content-type: text/html; charset=utf-8
content-length: 2471
vary: accept-encoding
content-encoding: gzip
expires: Sat, 11 Oct 2025 09:47:17 GMT
cache-control: max-age=0
etag: "myra-faab9484"
php.internals: Re: Flexible function naming
Re: Flexible function naming
From: Rasmus Lerdorf Date: Tue, 17 Dec 2013 01:24:06 +0000 Subject: Re: Flexible function naming References: 1 2 3 4 5 6 Groups: php.internals Request: Send a blank email to internals+get-70691@lists.php.net to get a copy of this message
On 12/16/2013 07:30 PM, Rowan Collins wrote: > The core functions which follow neither rule include C-style > abbreviations like "strptime" which couldn't be automatically swapped to > either format, and complete anomalies like "nl2br". If you named those > functions as part of a consistent style, you would probably also follow > stronger naming conventions than Rasmus did when he named > "htmlspecialchars". Well, there were other factors in play there. htmlspecialchars was a very early function. Back when PHP had less than 100 functions and the function hashing mechanism was strlen(). In order to get a nice hash distribution of function names across the various function name lengths names were picked specifically to make them fit into a specific length bucket. This was circa late 1994 when PHP was a tool just for my own personal use and I wasn't too worried about not being able to remember the few function names. -Rasmus
Thread (14 messages)
| « previous | php.internals (#70691) | next » |
|---|