Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #19492
| References | <569a94a3-cd84-449b-b0c1-80348014aac6@i10g2000pbl.googlegroups.com> <mailman.5070.1327492214.27778.python-list@python.org> <7c9ae6dd-c175-4376-be70-633785ed9386@iu7g2000pbc.googlegroups.com> <mailman.5080.1327510460.27778.python-list@python.org> <roy-98357C.09110826012012@news.panix.com> |
|---|---|
| Date | 2012-01-27 01:41 +1100 |
| Subject | Re: Distributing methods of a class across multiple files |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5129.1327588911.27778.python-list@python.org> (permalink) |
On Fri, Jan 27, 2012 at 1:11 AM, Roy Smith <roy@panix.com> wrote: > So, I'd say the driving principle should be that a function should do > one thing. Every function should have an elevator talk. You should be > able to get on an elevator with a function and when you ask it, "So, > what do you do?", it should be able to explain itself before you get to, > "Sorry, that's my floor". If it takes longer than that to explain, then > it's probably several functions fighting to get out. Agreed, that's definitely a good rule of thumb. But there's still some value in keeping the code length down too. In a program I maintain at work (in C++, but the same holds true), some functions have a perfect elevator talk, yet are quite a few screenfuls of code - this is not really advisable. For instance, one function is "handle responses to previously-sent requests". It incorporates all the code for handling requests of type X, of type Y, and of type Z. If I were writing this from scratch in Python, I would probably have X, Y, and Z all separated out, and the checkresponses function would simply be a dispatcher. ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Distributing methods of a class across multiple files lh <lhughes42@gmail.com> - 2012-01-24 19:54 -0800
Re: Distributing methods of a class across multiple files Roy Smith <roy@panix.com> - 2012-01-24 23:05 -0500
Re: Distributing methods of a class across multiple files Cameron Simpson <cs@zip.com.au> - 2012-01-25 17:15 +1100
Re: Distributing methods of a class across multiple files "Frank Millman" <frank@chagford.com> - 2012-01-25 10:26 +0200
Re: Distributing methods of a class across multiple files Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-01-25 11:10 +0000
Re: Distributing methods of a class across multiple files Jean-Michel Pichavant <jeanmichel@sequans.com> - 2012-01-25 12:49 +0100
Re: Distributing methods of a class across multiple files lh <lhughes42@gmail.com> - 2012-01-25 07:19 -0800
Re: Distributing methods of a class across multiple files Neil Cerutti <neilc@norwich.edu> - 2012-01-25 15:42 +0000
Re: Distributing methods of a class across multiple files Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-01-25 11:53 -0500
Re: Distributing methods of a class across multiple files Roy Smith <roy@panix.com> - 2012-01-26 09:11 -0500
Re: Distributing methods of a class across multiple files Chris Angelico <rosuav@gmail.com> - 2012-01-27 01:41 +1100
Re: Distributing methods of a class across multiple files Chris Angelico <rosuav@gmail.com> - 2012-01-26 20:25 +1100
csiph-web