On 08/08/07, Keith Bierman <[EMAIL PROTECTED]> wrote: > The lesson I learned from that experience is that developers don't > really want their faces rubbed into their mistakes. They want their > existing code to "just work" ... they may (and often do) appreciate > tools that let them clean up their act in their own time ... but not > ones which force their blunders to be obvious ... especially if the > only discovery is at runtime (even at compile time, the most frequent > requested compiler/lint options tend to be ways to suppress warnings > and even errors!).
While I understand your viewpoint, I think there has to be a better compromise than letting developers "get away with murder" or simply perpetuating those mistakes. There needs to be some incentive or way to encourage developers to do "the right thing." For example, maybe /bin/sh could somehow detect that the script being loaded contains bash syntax and automatically invoke bash to do the work while displaying a warning about the script being wrong. Heinous, I know, but I can't help but think that users need to know that a program is misbehaving and developers need to know that they need to do "the right thing." -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
