Read "Refactoring: Improving the Design of Existing Code" by Martin Fowler.
On 11/28/06, Helmut Granda <[EMAIL PROTECTED]> wrote:
I have a game class that is about 215 lines of code. Is not really big but i would like to divide this class in smaller packages so I can re-use bits of pieces of code for new versions of the game. The question is what are the best practices to break this code into smaller bits and pieces? As always we dont like to help without seeing what the person is doing already. So here it is my idea MainClass -com --utils ---func1 ---func2 ---func3 But some of the functions talk directly to the main class so what is the best approach to use those extra functions? Should I pass all the strings or arrays that in need and let the functions spit back the information I need? Help welcome... maybe a book or 2 :) -- ...helmut _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
-- T. Michael Keesey Director of Technology Exopolis, Inc. 2894 Rowena Avenue Ste. B Los Angeles, California 90039 -- The Dinosauricon: http://dino.lm.com Parry & Carney: http://parryandcarney.com ISPN Forum: http://www.phylonames.org/forum/ _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
