|
Pete, Using the *current/*prv signature method will also cause the same problems if new procedures are not added to the end of the export list. That is why this method doesn't buy you anything. I once argued on the side of the *current/*prv method until I saw the light and what was really happening :) Scott Mildenberger --- "Pete Clifford (@riadne software)" <pete@xxxxxxxxxxxxxxxxxxxxx> wrote: > The problem with this surely is that it's like a high-wire act > without the > safety net: everything's fine until until someone puts a foot > wrong... > > This is exactly like LVLCHK(*NO). By forcing the same > signature every time, > you've taken away the safety net. If someone doesn't follow > procedures, and > adds a new export in the middle, then you won't get an > obvious, early > indication of a problem in the form of a signature violation, > you'll get a > potentially much more damaging, subtle and elusive problem > which could > easily be missed in testing and end up in production. > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.