Home Tutorials Forums Articles Blogs Movies Library Employment Press

Go Back   ActionScript.org Forums > General > Best Practices

Reply
 
Thread Tools Rate Thread Display Modes
Old 10-28-2010, 10:18 PM   #11
bowljoman
Senior Member
 
Join Date: Jan 2008
Posts: 831
Default

I hate stack overflow!

I had to fix a project in which every function returned another function .

ActionScript Code:
function doSomething(){ ***     return otherDoSomething(); } function otherDoSomething(){ ***     return implDoSomething(); }

A few here and there is effective, but this SOB had 10 and 20 functions stacked up for no good reason. WHats worse, the SOB also had these stacked up on callReturn from a java server.

There was absolutely no way to tell where the errors occurred due to stack overflow. I spent a week unwinding the crud so that 50 million class methods were not called on every time the user sent something to the server. Idiot. When it got so bad that he could no longer debug, he wrapped the entire app in 'try/catch' with a print stack trace.... F'n trace was two pages long and crashed the browser half the time over a stupid null reference! YAAAAARRRRGHHH.... good money though, and awesome company to work for.
__________________
i = (Andy)this;
bowljoman is offline   Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 05:05 PM.

///
Follow actionscriptorg on Twitter

 


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Ad Management plugin by RedTyger
Copyright 2000-2013 ActionScript.org. All Rights Reserved.
Your use of this site is subject to our Privacy Policy and Terms of Use.