in reply to Re^2: Perl in the Enterprise
in thread Perl in the Enterprise
Normal coders rely on structured programming, separation of concerns, and language guarantees to produce trusted code. Perl doesn't offer very much in the ways of guarantees about anything; everything is left to the programmer's discression. That principle can't scale: independent of the language you implement it in.
There's no typechecking, no array bounds checking, substr() emits the same warning for fatal as non-fatal errors, but otherwise silently fails on bad input. In a critical system, you don't want one programmer to assume that a dial goes to ten, while another programmer assumes it goes to 11. You want a language that can detects code that tries to set an array bounds outside it's declared size to be detected beforre the code finishing compiling. Perl just doesn't do that. It's not designed for that.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Perl in the Enterprise
by chromatic (Archbishop) on May 18, 2006 at 18:31 UTC | |
|