View previous topic :: View next topic
|
Author |
Message |
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
Robert Sample wrote: |
Dick, you're bringing back bad memories .... BAD memories!
I once worked with programmers from another country. One of them told me, in all seriousness, that if her program compiled without errors then it was tested and ready for production. |
Here in Belgium I worked at a site where they had no problems putting programs with 'E' errors in production, "because this error has been in the program for eons"... |
|
Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009 Posts: 1788 Location: Bloomington, IL
|
|
|
|
prino wrote: |
Robert Sample wrote: |
Dick, you're bringing back bad memories .... BAD memories!
I once worked with programmers from another country. One of them told me, in all seriousness, that if her program compiled without errors then it was tested and ready for production. |
Here in Belgium I worked at a site where they had no problems putting programs with 'E' errors in production, "because this error has been in the program for eons"... |
And if you correct the error without being specifically told to, that's an unauthorized change to the business rules, and we simply can't have that... |
|
Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
I once turned a system over to someone who then proceeded to try to remove every instance of COBOL warnings (RC=4). I think he was OK with the info messages at least.
At another site (a brokerage) I had to repeatedly push to report an obvious COBOL error to the vendor because, since I could not substantiate the ramifications of the error, they would be unlikely to kindly receive the report. From the very nicely indented IF...THEN...ELSE, there was a stray period before the end of ELSE indenting. The compiler very kindly reported this because of the condition checking, the compiler detected dead code. They eventually relented, and the vendor confirmed the error. |
|
Back to top |
|
|
|