|
|
|
| Syntactic Confectionery Delight | |
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
|
As in a's comment, I also tend to write top down using
wishful
programming. (Where wishful programming is using names
of functions I haven't written yet.) This has the benefit
of not having to think about everything at once, and
if you create stub functions it will actually run and you
can slowly build it up. Ah ha, starting to use some XP
techniques! (Except I learnt to do this before XP was
around...)
When it comes to breaking functions up, if I have a function which is trying to do several different things, it is usually time to break it up. Likewise, a function which is more than a couple of screens long is about due for a break up. Although the screens one is very relative... Especially when I'm writing CGI scripts which are generating forms, they can get rather lengthy. Over the last couple of weeks I've been writing a interface for managing Spong - using Perl OO. In an object, if I realise that I need to use some code again (for example: sucking details out of the database about a host), it get's broken out to a new function in the object. So, there's some of my approaches. Of course, if I sat down and did some decent design before hand I'd only need to use the first one - wishful programming - as the functions would already be broken up logically. Sigh... Updated: Right, that link to Spong now works as it should. My bad. (Thanks a for pointing it out!) In reply to Re: Re (tilly) 1: When do you function?
by puck
|
|