PHP Design tools? IDE?

Christian Fersch <Chronial@web.de> wrote in message news:<ck6n41$goo$04$1@news.t-online.com>...

> The best editor for windows is NuSphere's phpEd. But it costs 500$.

Christian,

PhpED is $299, and the additional license is $50 only. You can get
more information about PhpED features and pricing options on our
website http://www.nusphere.com/products/index.htm

Best regards,
NuSphere Corp.

2metre <2metre@xxxhersham.net> wrote or quoted:
> Tim Tyler wrote:

> > IMO, using an interpreted language should only very rarely stop
> > you using OOP. It should not be *much* slower than the same site
> > without OOP - and any performance problems are best addressed by:
> >
> > * using more efficient algorithms - or by:
> > * buying more expensive hardware;
> >
> > Allowing performance to dictate a procedural programming style is
> > often a case of premature optimisation.

[...]

> As for "buying more expensive hardware..." that has to be *the* most
> extreme case of premature optimisation.

Premature optimisation usually refers to making a mess of your code
for the sake of performance.

Running on a faster machine doesn't seem to qualify there.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

Chris Hope <blackhole@electrictoolbox.com> wrote or quoted:
> Tim Tyler wrote:
> > 2metre <2metre@xxxhersham.net> wrote or quoted:

> > IMO, using an interpreted language should only very rarely stop
> > you using OOP. It should not be *much* slower than the same site
> > without OOP - and any performance problems are best addressed by:
> >
> > * using more efficient algorithms - or by:
> > * buying more expensive hardware;
> >
> > Allowing performance to dictate a procedural programming style is
> > often a case of premature optimisation.
>
> While this is true, you are basing your logic entirely on the premise that
> OOP programming is *always* better/nicer/cooler/whatever than straight
> procedural programming [...]

I read my post again. I can find no sign of such a premise.

I was mostly arguing that choosing a procedural programming style
on performance grounds was usually a bad idea - not that grounds
for writing procedural code do not exist.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.