NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
chromatic (983)
chromatic
(email not shown publicly)
http://wgz.org/chromatic/
(email not shown publicly)
http://wgz.org/chromatic/
Blog Information [technorati.com]
Profile for chr0matic [technorati.com]
Sunday January 27, 2008
12:03 AM
Language/Class Design Question of the Day
How would your code look if your language had a maximum logical SLOC size for classes of 1024? (I like 2^10.)
What other features would your language need to support the types of programs you write if this constraint were in place?
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I know this! (Score:2)
Re: (Score:1)
*wistful sigh*
Re: Language/Class Design Question of the Day (Score:1)
<bitchy>Vaguely decent developers?</bitchy>
If you're not including documentation 1024 lines is a bloody long class in a language like Perl/Ruby/Lisp/Python. Refactor that sucker.
Re: (Score:1)
Oh. For each class?
... right. Carry on.
perl -e 'print "Just another Perl ${\(trickster and hacker)},";'
The Sidhekin proves that Sidhe did it!
No different (Score:2)
It would look pretty much the same, and so the language would need no changes. In fact all the .pm files in my CVS repository which are over 1000 lines (and that includes documentation) are either someone elses code that I bundle with mine for compatibility (cos the new release of DBM::Deep isn't portable enough for my tastes) or are mostly __DATA__ noise. The biggest objecty file that's all my own work is 381 lines including doco and is actually three classes.
But not all my code is OO, so it isn't all