| |||||||||||
Upcoming PHP release will offer Unicode support (Linux.com)Upcoming PHP release will offer Unicode support (Linux.com)Posted Mar 9, 2007 17:34 UTC (Fri) by cdmiller (subscriber, #2813)In reply to: Upcoming PHP release will offer Unicode support (Linux.com) by dvdeug Parent article: Upcoming PHP release will offer Unicode support (Linux.com)
A programming language doesn't prevent a system from being cracked, people prevent a system from being cracked...
(Log in to post comments)
Upcoming PHP release will offer Unicode support (Linux.com) Posted Mar 10, 2007 1:08 UTC (Sat) by bronson (subscriber, #4806) [Link] True. But magic quotes and register globals seem to make it a lot harder for people to prevent the system from getting cracked.
Upcoming PHP release will offer Unicode support (Linux.com) Posted Mar 14, 2007 19:18 UTC (Wed) by dvdeug (subscriber, #10998) [Link] It's amazing how fast people who would fight to the death about the better language will deny any responsibility to a language when problems appear.
The Internet Worm, the first one, depended on a flaw in a program written in C. Only in C (or possibly assembly) would a function like "gets" be used, a function that required you to trust the other side not to overflow the buffer. In many languages, the programmer would have to go out of her way to write such code.
Not only that, I've written in several different languages, and I know I write different code in different languages. I write what comes easy and natural to the language; I create different integer based types in Ada because it's easy and natural to do so, but would never go through the hoops to do so in C++. I use pointers and OO in Java where I would use the stack and structs in C++ or Ada. If a language makes it easy and natural to write safe code, programmers will do so; if a language makes it complex and unnatural to write safe code, programmers will write the unsafe code (e.g. gets) that is simple and natural.
|
|||||||||||