When you program in a very OOP style this can be problematic. If the code is obvious, then I would think it would be far more procedural which is not where one wants to go. Just a thought, John
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Haygood Sent: Monday, February 19, 2007 1:06 PM To: [email protected] Subject: RE: [AFFUG Discuss] How do you document your Flex Code Self-documenting code. Make the code obvious to what it does. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Precia Sent: Monday, February 19, 2007 1:07 PM To: [email protected] Subject: [AFFUG Discuss] How do you document your Flex Code How do you document your Flex code? In CF some use FuseDocs or other solutions. What's yours? Precia ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by FusionLink <http://www.fusionlink.com> ------------------------------------------------------------- ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by FusionLink <http://www.fusionlink.com> ------------------------------------------------------------- ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
