Re: Thoughts on includes

[Jason Pincin <jpincin@ashtech.net>]

If you throw it all in one file it'll prolly be between 1500 and 2000
lines of code.



On Thu, Aug 12, 1999 at 02:40:21PM -0700, Aaron Turner wrote:
> 
> How big is "huge"?
> 
> On Thu, 12 Aug 1999, Jason Pincin wrote:
> 
> > This is something Micah brought up some time ago -
> > 
> > Should we break the functions.php3 apart?  It's going to get HUGE.  I'm
> > not sure we want the entire thing on EVERY page.  There are THREE CORE
> > components in it that just about every page will need - connect(),
> > resultset(), and object().  The rest of the extensions of object() such as
> > article(), kbcontainer(), user(), etc. are going to amount to a good bit
> > of code when thrown into one file.  Should we create a core include and
> > then break the object extensions up into individual files?  One for each
> > extension of object?  99.9% of our pages will only require ONE of those
> > object extensions... so 99.9% of our pages would do 2 includes... plus the
> > render.php3 include which makes 3.  It's either that or do a total of 2
> > for every page load, and have every page pull in a MASSIVE chunk of php
> > code to process.
> > 
> > Thoughts?
> > 
> > Jason
> > 
> 
> --
> Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization  http://linuxkb.org/
> Because world domination requires quality open documentation.