| |||||||||||
Re: Code needs generating a method with more than Posted by admin (Graham Ellis), 25 May 2003 It sound to me as if you've written a very long piece of code in a single method - which is very much against the principles of good code development. Code should be divided down into a number of methods with less code in each, and linked together by calls to one method from another.So - take you huge method and draw a very simple flowchart of what it does - say just 4 or 5 boxes, each of which might have quite a long description in it. That will provide you with how you should split your code down - each of the 4 or 5 boxes will be a method that's much smaller than your current code, and you can then write an extra very short method called in the same way as the one that won't work to replace it. This task may turn out not to be trivial as you'll have to do a certain amount of extra work to ensure that variables are scoped and available properly in the new layout, but it should provide a much more easily tested and maintained result. Posted by admin (Graham Ellis), 30 May 2003 Note for the puzzled reader of this thread ...The original poster has deleted his / her thread, leaving an orphan answer .... Briefly, the question related to error messages generated by Java saying that a method was in excess of 64k in size and couln't work. This page is a thread posted to the opentalk forum
at www.opentalk.org.uk and
archived here for reference. To jump to the archive index please
follow this link.
|
| ||||||||||
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho |