Requiring that programmers stick to a standard and enforcing that requirement will always limit the sort of problems you encounter. I am all too familiar with projects and companies who don't do that. I think in either case it's a good idea to try to ensure that you design the practices and procedures so as to minimize the both the likelihood and impact of failure to follow the procedures be it through carelessness, malice, or simple human error. The specific case of a variable changing type mid-stream is probably not a a good example of where this can have a big impact, but I think the principle still holds.
I agree, I thought you had been specifically talking about variable type changes.
Yes, but in the case of NASA I'd bet that the standard is well documented and that they have procedures in place to ensure that it is followed.
Agreed. That doesn't mean I'm going to write my code less strictly just because management may fail at verifying that procedures had been followed. That's why all programmers if they don't have a set procedure that needs to be followed, to create one and follow it strictly.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
