Monday, May 28. 200720 possible reasons why PHP function names and parameters are weirdTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Amusing list. I laughed for a few of them, and no doubt there's a bit of truth in each item on that list.
Comment (1)
Good. Very good. Most people will never understand the first one in your list. It is the most common reason PHP is the way that it is.
Comment (1)
Hah! "Pull Strings" Is that your code-speak for payoffs from the manual cartel?
Is it? O Capo di tutti capi? ((Geez, I hope that's glue.....)) Comment (1)
Sorry for my bad english.
I remember a thread in a coder-board, some years ago. The guy said "Now that PHP is well used by the John Does, we have to work for make the language more hard to fully understand, for they need us for that". Comment (1)
lol... but I am more confused now :( I was finding way to go with PHP or ASP.NET
Comment (1)
I was hoping to find some tips on how best to name a function using the least number of characters and avoid conflicting with future reserved words.
The reason I want to do this is so users of my software can enter snippets of PHP into their web pages that call one of my functions that inserts some code into their page. The shorter and easier it is to type the better. burp() seems to be suitable. Andy Comment (1)
well at least the names are easy to goddamn type without ridicujlous prefixes or stupid::colons
Comment (1)
|
Static PagesLinks mentioned in this articleCalendarBlog Administration |
