It's also a general programming principle that larger files are harder to maintain and
debug; once it gets to a
certain size, it probably is starting to have too much functionality in one place,
with too much interrelated code,
and would benefit from being broken down into smaller pieces that each do a certain
part. Doesn't necessarily have
to be that small, just as long as it's easier to read and maintain.
- David L.
George Kaytor wrote:
> He is a probably a fuseboxer. Fusebox is a programming methodology that
> breaks things into small parts..... (+ a whole more)
>
> -george
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: CF-Community <[EMAIL PROTECTED]>
> >Subject: Re: CF-Community-List V1 #120
> >Date: Thu, 22 Feb 2001 07:17:33 EST
> >
> >In a message dated 02/21/2001 11:31:04 PM Eastern Standard Time,
> >[EMAIL PROTECTED] writes:
> >
> > > Isn't that a tad on the big side? Not that I've seen your code or
> >anything
> > > but large files in excess of 200 lines usually can be broken down into
> > > smaller steps using cfinclude. Where the cfincludes do one action for
> >the
> > > page (ie like a query).
> >Adam,
> >Why should you make the page less than 200 lines of code?
> >
> >Jo-Anne Head
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
