|
|
Posted by shimmyshack on 03/25/07 12:50
On 24 Mar, 21:50, Michael Daly <MichaelD...@foo.bar> wrote:
> I'm working on a program that permits a web site admin to enable either
> or both of its two features. Both features have a reasonable amount of
> code.
>
> So - is it likely that someone will complain that having both sets of
> code loaded when only one of the features is enabled will reduce
> performance? Is there a significant advantage to splitting the code so
> that only one feature is loaded to run when only one feature is enabled?
> The php file is about 30KB (both features).
>
not really
> Second - I tend to put a lot of comments in my code. In terms of file
> size, there is often more lines of comments than lines of code (unless
> the code is relatively trivial). Similarly - is someone likely to grump
> that loading all that text at run rime is inefficient?
and no
>
> Mike
but in general for other reasons it is a good idea to modularise your
code, something like jpgraph - a huge set of classes that generates
various types of graphs, simply separates its clsses according to the
type of graph, its a split that makes sense to coders implementing it
at the coal face, and to maintainters. It would be a nice little
project to convert to OO, if not already, and yeah try separating it.
Navigation:
[Reply to this message]
|