Word of warning for anyone about to use new versions of PHP

Quote:

---

Originally Posted by McGruff

I did think that was a good definition; I didn't think you should call people stupid even if you do disagree.

---

I didn't called him stupid, I called his statement stupid, simply because, him too used the word stupid:

Quote:

---

Asking "Is PHP Enterprise ready" is a stupid question

---

And no, his definition is not good, simply because a platform is enterprise-ready only when it provides necessary tools for making "enterprise applications". And just because some "enterprise code" exist, doesn't mean PHP is enterprise ready. This is not the chicken and the egg problem.

Well I've got an XP perspective:

PHP Code:

---

  $this->assertTrue($php_enterprise_application->isWorking()); 


---

If it passes the test, php must be enterprise ready. It may not be perfect, granted, but it just has to be good enough.

Hi...

Quote:

---

Originally Posted by Website Rob

...and good Perl coders know that coding in 'strict' may take more time but you pretty much get bulletproof code; from a no-bugs and best security point-of-view.

---

In practice a good Perl coder will use strict to catch reference errors because the Perl notation for referencing is even more insane than PHP4. Unfortunately it forces you to put "my" before every new occourance of a variable :(. This is utterly unnecessary and a constant irritation. At least Ruby had the good sense to throw it out.

In PHP5 I would just change all of the "var $" strings to "private $" and then strip the now redundant underscores. We are pretty strict about not accessing object memebers from outside (or even subclasses).

yours, Marcus

Quote:

---

Originally Posted by lastcraft

Hi...



In practice a good Perl coder will use strict to catch reference errors because the Perl notation for referencing is even more insane than PHP4. Unfortunately it forces you to put "my" before every new occourance of a variable :(. This is utterly unnecessary and a constant irritation. At least Ruby had the good sense to throw it out.

---

Well, to be fair, instead of using all of strict module, you can use certain parts of it. Like:

Code:

---

use strict 'refs';

---

So at least you do have an option.

That said, I hate perl :p

Quote:

---

Originally Posted by lastcraft

In PHP5 I would just change all of the "var $" strings to "private $" and then strip the now redundant underscores. We are pretty strict about not accessing object memebers from outside (or even subclasses).

---

I like underscores and naming conventions especially when those variables are private (i.e. are not used from outside). What I mean is, who cares if the implementation of a class is ugly if the interface is beautifull :).

Hi...

Quote:

---

Originally Posted by Ryan Wray

Code:

---

use strict 'refs';

---

---

Now you tell me :lol:. Oh well, we are switching our Perl code over to Ruby.

yours, Marcus