Re: [SC-L] How can we stop the spreading insecure codingexamplesattraining classes, etc.?

www.eschertech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of der Mouse Sent: 31 August 2006 22:45 To: SC-L@securecoding.org Subject: Re: [SC-L] How can we stop the spreading insecure codingexamplesattraining classes, etc.? ever heard of exceptions

Re: [SC-L] How can we stop the spreading insecure codingexamplesattraining classes, etc.?

as an industry we did manage to get rid of computed gotos, spaghetti code, etc., so maybe there's hope. ever heard of exceptions? They're basically goto plus limited state. Spaghetti lives! gem company www.cigital.com podcast www.cigital.com/silverbullet book www.swsec.com

Re: [SC-L] How can we stop the spreading insecure codingexamplesattraining classes, etc.?

I take exception (haha!) at having them dismissed like this. It sounds like you encountered some badly written exception handling code. Error handling can also be really bad, where at every call layer the original error gets filtered or translated to a point where you just know something went

Re: [SC-L] How can we stop the spreading insecure codingexamplesattraining classes, etc.?

ever heard of exceptions? They're basically goto plus limited state. Spaghetti lives! Not at all. Exceptions are not like gotos; in particular, an exception cannot be used to jump *into* a construct. The major problems with gotos are that they can be used to do branches that are downward or